Software Engineering

Here's a list of those log levels from lowest precedence to highest:

notset (0) - Indicates that ancestor loggers should be consulted for the log level or that all events are logged (default setting)

debug (10) - Detailed information that would be of interest to the developer for diagnostic purposes

info (20) - Information that confirms that your... See more

Netflix created a scoring system from 0 to 100 that assigns a priority to a request, with 0 being the highest priority and 100 being the lowest priority.

The score was based on 4 dimensions

Functionality - What functionality gets impacted if this request gets throttled? Is it important to the user experience? For example, if logging-related requests... See more

For high-priority tasks , like designing the main user interface content or creating content for a major product launch, you might spend 10–20 hours a week. These tasks need detailed planning and close collaboration with your team.

Medium-priority tasks , such as updating help center articles or creating content for minor feature updates, might take... See more

We ship often

Shipping early is not enough. We also need to keep shipping tiny iterations daily instead of waiting months to ship something big.

Having a strong sense of urgency , and making hard decisions fast is how we enable that process. Our sprints only last 1 week and are quite short when compared to the rest of the industry - this is by... See more

Comments are helpful sometimes. But sometimes, they are just an indication of bad code.The proper use of comments is to compensate for our failure to express ourself in code [1].Whenever you have to add a comment in your code, ask yourself if it is really required or if you could instead put that into a new function and name the function so that it... See more

When a test fails, you should be able to begin investigation with nothing more than the test’s name and its failure messages —no need to add more information and rerun the test.

Effective use of unit test frameworks and assertion libraries (JUnit, Truth, pytest, GoogleTest, etc.) serves two important purposes. Firstly, the more precisely we express... See more

Each log message in the system should be unique.

If I query for a log in a specfic service, I will be confused to see the exact same logs at different flows inside the service.

More than that, I’ll just have to start debugging for the issue, since the logs are now offically useless.

One way to keep the logs unique is to denote the service name and... See more

Build & Deployments

Our build process starts by pushing changes to a repository on GitHub. When code is pushed to a repository through a pull request, it triggers a job to build the changes made to the branch and deploy them in isolation. This worklow happens interactively within the pull request, where the author has visibility of all steps.

Some... See more