Software Engineering

Your job involves turning the unknown into the known and translating vague ideas into actionable plans. This often involves a blend of:

• Detective work — ask the right questions, collect evidence, build a case theory, validate it


• Isolating uncertainty to the smallest components and proving / disproving theories


• Divide and conquer — breaking down the

... 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

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

• Solution : Apply the Single Responsibility Principle - each microservice should focus on one single capability that it masters.


• Benefits : This specialization makes microservices easier to comprehend, test, scale, and upgrade. It's like having a coordinated team where each member excels at their role.


• Pitfalls : Violating this principle leads to

... See more

Whenever you write a log, it’s important you choose the correct log level.

I personally mostly use ERROR, WARNING, INFO, or DEBUG (yes there are a few more).

Log levels TLDR

• ERROR: Parts of the flow failed, we want to send alerts to our on-call for this failures.


• WARNING: Doesn’t necessarily point to a failure, but an unexpected behavior that should

... See more

More than reading popular books on Design Patterns, two things that helped me write and structure a large codebase better were

reading a lot of good open source codebases (with similar stack)coding and collaborating a lot on the same codebase

I understand the importance of reading general-purpose design patterns, but they might not suit your... See more

A thread pool is a collection of pre-initialized threads that can be used to execute tasks. Instead of starting a new thread for each task (which can be resource-intensive), a thread from this pool is reused to perform the task. This approach is beneficial for handling multiple operations in parallel, especially when these operations are blocking... 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.