Connect with us

FACEBOOK

Docusaurus: A Contributor’s Story with Samuel Adjei

Published

on

The “Contributor’s Story” series is intended to provide a face and voice to our major open source contributors and community members, an overview of the projects they are working on, and the successes and challenges contributors face when developing.

For this blog post, we spoke with Samuel Adjei, a Docusaurus contributor working on blog and documentation plugins through the Major League Hacking (MLH) Fellowship.

“For me, I have always wanted to become a part of something bigger than myself. [In] the Tech space, it has mostly been about contributing to open source and helping others get into coding by making it easier.”

Tell us a little bit about yourself and your current experience in the MLH Fellowship.

My name is Samuel Adjei, I’m a second year Computer Science student from the University of Ghana. I’m currently working on Facebook’s Docusaurus in the MLH Fellowship open source track. Docusaurus is basically an open source project for building, managing and deploying technical documentation very easily.

Before getting started in open source, my background was primarily in web development. I started my career with the fundamentals of the web – HTML, CSS and JavaScript. After becoming familiar with those languages, I expanded to vanilla PHP, did some cool stuff with the Laravel framework, and later got hooked to jQuery. From these beginnings, I worked my way up to some modern front-end web frameworks like VueJS, and now in my free-time I focus on building for mobile. Lately I have been working with Flutter outside of my open source contributions.

Advertisement
free widgets for website

Prior to joining the MLH Fellowship, I was looking for some open source-related programs for students. I heard about the Fellowship program and I decided to look more into it. I read a lot of articles and threads to get a sense of how the program really worked, especially for the open source track. It was exactly what I was looking for. I went through the application and interview process, got accepted, and started developing on Docusaurus.

See also  Good news for advertisers: Facebook is developing a new tool for brands to tackle harmful content

Where did you first learn about open source? How did you get started using/contributing?

I heard about open source fairly early when I started learning how to code. I didn’t really have a lot of experience with it when I first got involved with the Fellowship. That said, a lot of knowledge required when using and contributing to open source projects became intuitive when I learned how to use GitHub. It made sense to me: let’s write software in a way everyone gets to be a part of. With the resources from the Fellowship and witnessing how people use tools like GitHub, I spent a lot of my first week taking the time learning about the open source ecosystem as a whole.

After I got a hang of how it worked, I made a few contributions here and there and wrote some packages myself on GitHub.

Describe the project you are currently working on.

Advertisement
free widgets for website

I am currently working on Docusaurus in the Fellowship. On the technical side, what’s most impressive to me is that they take a modular approach. Almost every feature like the blog and docs functionality is basically a package. It is well thought-out, and abstracts most of the technicalities allowing you to configure and write docs and blogs very easily without even touching code. The best part is you can write your own plugins to augment and build on top of what’s already available.

How did you initially go about tackling the issue?

Contributing to huge repositories might look intimidating. A lot of what you initially learn and contribute to has to do with the project’s structure. For Docusaurus, as I previously mentioned, a lot of the features are built as plugins. This makes it relatively easier to use and contribute to Docusaurus in my opinion.

See also  The New York Times Abandoning Its Very Popular Facebook Cooking Group

To start working on an issue, I would first read thoroughly about the issue’s description and all the previous discussions about it. For me, this ensures that I actually understand what the issue is about. The next part is knowing where to look. In Docusaurus, the most approachable solution would be to look into the plugin the issue is from. You might have to trace from the entry point of the project to get there, but once you do and understand how everything fits together, it is relatively easy to know how to solve the issue.

What roadblocks or problems have you faced thus far in your contribution?

Advertisement
free widgets for website

Generally, the most obvious problems come up due to a lack of context. Sometimes digging through the project’s code can be difficult. Things might not be conventional to you just yet. It might not be intuitive to know where exactly to look. A file might just be too large and may import a lot of unknown dependencies. Not knowing how all these fit together might drive you insane. Learning to trace through the project yourself helps you in the long run. You can understand how the framework works from the ground up. That said, whenever you get stuck, you should not be shy to ask for help from maintainers.

What is the current status of development?

I think overall my Docusaurus team and I have come a long way in both contributing and developing, with help from very skilled maintainers of the project. I would say most of the issues assigned to us have been resolved with support from the maintainers when necessary. We just have a few issues to round up and call it a cohort! The nice part about open source and this Fellowship is these projects are visible and community-driven, so we can continue to contribute even after the Fellowship.

See also  A French coronavirus conspiracy video stayed on YouTube and Facebook for months

What have you learned about the project, development, or open source thus far?

I would say contributing to Docusaurus has given me a solid foundation to contribute to other large repositories in the future. I got to witness how technical discussions work in bigger open source projects, and was able to join in the conversation. In working with Docusaurus and the maintainers, I learned some really neat testing tricks and a whole lot of strategies I couldn’t get from a lot of tutorials. Really, just being given the opportunity to work on such a huge repository made me grow as a developer.

Advertisement
free widgets for website

What advice would you give future contributors to the open source project?

I would say debug and trace the repo right from the beginning. It would help you ramp up faster on the codebase and you would get the most out of contributing to open source and the Fellowship that way. Don’t get stuck trying to figure things out yourself, ask the maintainers and community for help and I’m sure you will do great.

We’d like to thank Samuel for their continuous contributions to the Facebook Open Source ecosystem. You can follow Samuel’s work through GitHub, and LinkedIn.

If you’d like to learn more about Facebook Open Source, follow us on Twitter, Facebook, and YouTube for relevant updates, and check out the Docusaurus website, Twitter and GitHub for how to get started.

Facebook Developers

Advertisement
free widgets for website
Continue Reading
Advertisement free widgets for website

FACEBOOK

Meet the Developers – Linux Kernel Team (David Vernet)

Published

on

By

meet-the-developers-–-linux-kernel-team-(david-vernet)

Credit: Larry Ewing (lewing@isc.tamu.edu) and The GIMP for the original design of Tux the penguin.

Intro

For today’s interview, we have David Vernet, a core systems engineer on the Kernel team at Meta. He works on the BPF (Berkeley Packet Filter) and the Linux kernel scheduler. This series highlights Meta Software Engineers who contribute to the Linux kernel. The Meta Linux Kernel team works with the broader Linux community to add new features to the kernel and makes sure that the kernel works well in Meta production data centers. Engineers on the team work with peers in the industry to make the kernel better for Meta’s workloads and to make Linux better for everyone.

Tell us about yourself.

I’m a systems engineer who’s spent a good chunk of his career in the kernel space, and some time in the user-space as well working on a microkernel. Right now, I’m focusing most of my time on BPF and the Linux kernel scheduler.

I started my career as a web developer after getting a degree in math. After going to grad school, I realized that I was happiest when hacking on low-level systems and figuring out how computers work.

As a kernel developer at Meta, what does your typical day look like?

I’m not a maintainer of any subsystems in the kernel, so my typical day is filled with almost exclusively coding and engineering. That being said, participating in the upstream Linux kernel community is one of the coolest parts of being on the kernel team, so I still spend some time reading over upstream discussions. A typical day goes something like this:

Advertisement
free widgets for website
  1. Read over some of the discussions taking place on various upstream lists, such as BPF and mm. I usually spend about 30-60 minutes or so per day on this, though it depends on the day.

  2. Hack on the project that I’m working on. Lately, that’s adding a user-space ringbuffer map type to BPF.

  3. Work on drafting an article for lwn.net.

What have you been excited about or incredibly proud of lately?

I recently submitted a patch-set to enable a new map type in BPF. This allows user-space to publish messages to BPF programs in the kernel over the ringbuffer. This map type is exciting because it sets the stage to enable frameworks for user-space to drive logic in BPF programs in a performant way.

Is there something especially exciting about being a kernel developer at a company like Meta?

The Meta kernel team has a strong upstream-first culture. Bug fixes that we find in our Meta kernel, and features that we’d like to add, are almost always first submitted to the upstream kernel, and then they are backported to our internal kernel.

Do you have a favorite part of the kernel dev life cycle?

I enjoy architecting and designing APIs. Kernel code can never crash and needs to be able to run forever. I find it gratifying to architect systems in the kernel that make it easy to reason about correctness and robustness and provide intuitive APIs that make it easy for other parts of the kernel to use your code.

I also enjoy iterating with the upstream community. It’s great that your patches have a whole community of people looking at them to help you find bugs in your code and suggest improvements that you may never have considered on your own. A lot of people find this process to be cumbersome, but I find that it’s a small price to pay for what you get out of it.

Tell us a bit about the topic you presented at the Linux Plumbers Conference this year.

We presented the live patch feature in the Linux kernel, describing how we have utilized it at Meta and how our hyper-scale has shown some unique challenges with the feature.

Advertisement
free widgets for website

What are some of the misconceptions about kernel or open source software development that you have encountered in your career?

The biggest misconception is that it’s an exclusive, invite-only club to contribute to the Linux kernel. You certainly must understand operating systems to be an effective contributor and be ready to receive constructive criticism when there is scope for improvement in your code. Still, the community always welcomes people who come in with an open mind and want to contribute.

What resources are helpful in getting started in kernel development?

There is a lot of information out there that people have written on how to get integrated into the Linux kernel community. I wrote a blog post on how to get plugged into Linux kernel upstream mailing list discussions, and another on how to submit your first patch. There is also a video on writing and submitting your first Linux kernel patch from Greg Kroah-Hartman.

In terms of resources to learn about the kernel itself, there are many resources and books, such as:

Where can people find you and follow your work?

I have a blog where I talk about my experiences as a systems engineer: https://www.bytelab.codes/. I publish articles that range from topics that are totally newcomer friendly to more advanced topics that discuss kernel code in more detail. Feel free to check it out and let me know if there’s anything you’d like me to discuss.

To learn more about Meta Open Source, visit our open source site, subscribe to our YouTube channel, or follow us on Twitter, Facebook and LinkedIn.

First seen at developers.facebook.com

Advertisement
free widgets for website
See also  The New York Times Abandoning Its Very Popular Facebook Cooking Group
Continue Reading

FACEBOOK

Get started with WhatsApp Business Platform in Minutes with Postman

Published

on

By

get-started-with-whatsapp-business-platform-in-minutes-with-postman

Our collaboration brings tools you already use to WhatsApp Business Platforms APIs

Postman is a best-in-class API platform used by 20M developers worldwide. Using Postman simplifies each step of the API lifecycle and streamlines collaboration.

Postman’s strong platform and broad adoption in the developer community made deciding to work with Postman to deliver a robust developer experience an easy decision for our WhatsApp Business Platform product team.

What Postman means for your WhatsApp projects

The benefits of this collaboration for developers are clear – you can easily leverage Postman’s platform with your Meta projects to onboard, collaborate, and contribute towards documentation and best practices as you build out your integrations.

Fast Onboarding

The WhatsApp team is able to offer, via Postman, an API collection that pre-fills environment variables and walks you through your initial test requests – helping developers dive right in to using the Cloud API. Our product managers show you how easy it is to get started with Postman in this session from Conversations:

Foster Collaboration

The public Postman workspace fosters collaboration – allowing environments, collections, and documentation augmentation to happen in one place.

Advertisement
free widgets for website

Enhance Documentation

Postman’s API documentation tools augment our own documentation and allows developers to contribute directly to the community’s shared knowledge, building a strong reference library for all developers and encouraging new, innovative use cases.

The Results

Working with Postman from the beginning helps create a developer-friendly experience for the WhatsApp Business Platform – allowing you to get started quickly, build community, and share knowledge.

Want to know more about our partnership with Postman? Check out their case study, follow along with the video above, or dive right into the Postman Workspace for the WhatsApp Business Platform.

See also  The New York Times Abandoning Its Very Popular Facebook Cooking Group

1. https://www.postman.com/state-of-api/

First seen at developers.facebook.com

Advertisement
free widgets for website
Continue Reading

FACEBOOK

Summer of open source: building more efficient AI with PyTorch

Published

on

By

summer-of-open-source:-building-more-efficient-ai-with-pytorch

Note: Special thanks to Less Wright, Partner Engineer, Meta AI, for review of and additional insights into the post.

This post on creating efficient artificial intelligence (AI) is the second in the “Summer of open source” series. This series aims to provide a handful of useful resources and learning content in areas where open source projects are creating impact across Meta and beyond. Follow along as we explore other areas where Meta Open Source is moving the industry forward by sharing innovative, scalable tools.

PyTorch: from foundational technology to foundation

Since its initial release in 2016, PyTorch has been widely used in the deep learning community, and its roots in research are now consistently expanding for use in production scenarios. In an exciting time for machine learning (ML) and artificial intelligence (AI), where novel methods and use cases for AI models continue to expand, PyTorch has reached the next chapter in its history as it moves to the newly established, independent PyTorch Foundation under the Linux Foundation umbrella. The foundation is made up of a diverse governing board including representatives from AMD, Amazon Web Services, Google Cloud, Microsoft Azure and Nvidia, and the board is intended to expand over time. The mission includes driving adoption of AI tooling through vendor-neutral projects and making open source tools, libraries and other components accessible to everyone. The move to the foundation will also enable PyTorch and its open source community to continue to accelerate the path from prototyping to production for AI and ML.

Streamlining AI processes with Meta open source

PyTorch is a great example of the power of open source. As one of the early open source deep learning frameworks, PyTorch has allowed people from across disciplines to experiment with deep learning and apply their work in wide-ranging fields. PyTorch supports everything from experiments in search applications to autonomous vehicle development to ground-penetrating radar, and these are only a few of its more recent applications. Pairing a versatile library of AI tools with the open source community unlocks the ability to quickly iterate on and adapt technology at scale for many different uses.

See also  This Robot Trader Turned Bullish on Amazon, Facebook, and Nvidia. What It Sold. | Barron's

As AI is being implemented more broadly, models are trending up in size to tackle more complex problems, but this also means that the resources needed to train these models have increased substantially. Fortunately, many folks in the developer community have recognized the need for models to use fewer resources—both from a practical and environmental standpoint. This post will explore why quantization and other types of model compression can be a catalyst for efficient AI.

Advertisement
free widgets for website

Establishing a baseline for using PyTorch

Most of this post explores some intermediate and advanced features of PyTorch. If you are a beginner that is looking to get started, or an expert that is currently using another library, it’s easiest to get started with some basics. Check out the beginner’s guide to PyTorch, which includes an introduction to a complete ML workflow using the Fashion MNIST dataset.

Here are some other resources that you might check out if you’re new to PyTorch:

  • PyTorch Community Stories: Learn how PyTorch is making an impact across different industries like agriculture, education, travel and others
  • PyTorch Beginner Series: Explore a video playlist of fundamental techniques including getting started with tensors, building models, training and inference in PyTorch.

Quantization: Applying time-tested techniques to AI

There are many pathways to making AI more efficient. Codesigning hardware and software to optimize for AI can be highly effective, but bespoke hardware-software solutions take considerable time and resources to develop. Creating faster and smaller architectures is another path to efficiency, but many of these architectures suffer from accuracy loss when compared to larger models, at least for the time being. A simpler approach is to find ways of reducing the resources that are needed to train and serve existing models. In PyTorch, one way to do that is through model compression using quantization.

Quantization is a mathematical technique that has been used to create lossy digital music files and convert analog signals to digital ones. By executing mathematical calculations with reduced precision, quantization allows for significantly higher performance on many hardware platforms. So why use quantization to make AI more efficient? Results show that in certain cases, using this relatively simple technique can result in dramatic speedups (2-4 times) for model inference.

See also  A French coronavirus conspiracy video stayed on YouTube and Facebook for months

The parameters that make up a deep learning model are typically decimal numbers in floating point (FP) precision; each parameter requires either 16 bits or 32 bits of memory. When using quantization, numbers are often converted to INT4 or INT8, which occupy only 4 or 8 bits. This reduces how much memory models require. Additionally, chip manufacturers include special arithmetic that makes operations using integers faster than using decimals.

There are 3 methods of quantization that can be used for training models: dynamic, static and quantize-aware training (QAT). A brief overview of the benefits and weaknesses is described in the table below. To learn how to implement each of these in your AI workflows, read the Practical Quantization in PyTorch blog post.

Advertisement
free widgets for website

Quantization Method

Benefits

Weaknesses

Dynamic

  • Easy to use with only one API call
  • More robust to distribution drift resulting in slightly higher accuracy
  • Works well for long short-term memory (LSTM) and Transformer models

Additional overhead in every forward pass

Static (also known as PTQ)

Advertisement
free widgets for website
  • Faster inference than dynamic quantization by eliminating overhead

May need regular recalibration for distribution drift

Quantize-Aware Training (QAT)

  • Higher accuracy than static quantization
  • Faster inference than dynamic

High computational cost

Additional features for speeding up your AI workflow

Quantization isn’t the only way to make PyTorch-powered AI more efficient. Features are updated regularly, and below are a few other ways that PyTorch can improve AI workflows:

  • Inference mode: This mode can be used for writing PyTorch code if you’re only using the code for running inference. Inference mode changes some of the assumptions when working with tensors to speed up inference. By telling PyTorch that you won’t use tensors for certain applications later (in this case, autograd), it adjusts to make code run faster in these specific scenarios.

  • Low precision: Quantization works only at inference time, that is, after you have trained your model. For the training process itself, PyTorch uses AMP, or automatic mixed precision training, to find the best format based on which tensors are used (FP16, FP32 or BF16). Low-precision deep learning in PyTorch has several advantages. It can help lower the size of a model, reduce the memory that is required to train models and decrease the power that is needed to run models. To learn more, check out this tutorial for using AMP with CUDA-capable GPUs.

  • Channels last: When it comes to vision models, NHWC, otherwise known as channels-last, is a faster tensor memory format in PyTorch. Having data stored in the channels-last format accelerates operations in PyTorch. Formatting input tensors as channels-last reduces the overhead that is needed for conversion between different format types, resulting in faster inference.

  • Optimize for inference: This TorchScript prototype implements some generic optimizations that should speed up models in all environments, and it can also prepare models for inference with build-specific settings. Primary use cases include vision models on CPUs (and GPUs) at this point. Since this is a prototype, it’s possible that you may run into issues. Raise an issue that occurs on the PyTorch GitHub repository.

Unlocking new potential in PyTorch

Novel methods for accelerating AI workflows are regularly explored on the PyTorch blog. It’s a great place to keep up with techniques like the recent BetterTransformer, which increases speedup and throughput in Transformer models by up to 2 times for common execution scenarios. If you’re interested in learning how to implement specific features in PyTorch, the recipes page allows you to search by categories like model optimization, distributed training and interpretability. This post is only a sampling of how tools like PyTorch are moving open source and AI forward.

To stay up to date with the latest in Meta Open Source for artificial intelligence and machine learning, visit our open source site, subscribe to our YouTube channel, or follow us on Facebook, Twitter and LinkedIn.

First seen at developers.facebook.com

Advertisement
free widgets for website
Continue Reading

Trending