Hot-Take

It’s extremely daunting to transition from writing code on your own to writing code in a team setting. It’s nerve-wracking knowing that each line of your code can come under the scrutiny of new eyes, and it may not always be clear what the “right” way is. This article includes some tips that should help build your confidence when contributing in a team environment.

A topic that keeps nagging at me as I work on distributed systems is the proper usage of typing across separate components. On one hand, by enforcing strict typing at every layer, you have the potential to prevent changes to the structure of data in one component from propagating to other components as errors. On the other hand, you have a large amount of not-so-mature tooling and tradeoffs that cause a fragility that could otherwise be avoided.

What’s so great about homogeny?

You don’t need to turn every arbitrary string and number in your code into a constant.