Software Engineering

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

We ship early

We constantly review the scope of a project and work toward a v0, not a v1.

That means identifying the most crucial part of a functionality , and pushing the smallest pull request possible to make that happen. In fact, a PR should always be optimized for the speed with which we can merge it in.

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

How to build this skill:

• Maximize what you can do on your own: by ruthlessly prioritizing your time, pushing back on activities that have small ROI, and focusing on areas where your input is crucial; for engineers, it often means less coding (if more junior people can do that piece of coding).


• How you can maximize what you can do through others:

... See more

Problem : Tight coupling leads to fragility - a change in one microservice breaks connected services.

Low cohesion results in unclear responsibilities.

• Solution : Apply loose coupling and high cohesion. In a loosely coupled system, each component is independent and changes in one will not affect the others. High cohesion means that each component

... See more

Use nested objects for future extensibility

A follow on from the previous tip: try to logically group fields together. The following:

customer.address = {

line1: "Main Street 123",

city: "San Francisco",

postal_code: "12345"

};

Enter fullscreen mode

Exit fullscreen mode

is much cleaner than:

customer.address_line1 = "Main street 123";

customer.address_city... See more

Why is Continuous Delivery for ML/AI hard(er)?

Since the challenge is not new and many valid solutions exist targeting traditional software projects, is there a reason to treat ML/AI systems any differently? Consider these three core challenges that are endemic in ML, AI, and data projects:

1. Development and debugging cycles are more tedious due to

... See more

factory_boy

factory_boy is a fixtures replacement based on thoughtbot's factory_bot.

As a fixtures replacement tool, it aims to replace static, hard to maintain fixtures with easy-to-use factories for complex objects.

Instead of building an exhaustive test setup with every possible combination of corner cases, factory_boy allows you to use objects... See more