2024-11-23 π programmerhumor β RE: yogthos
So breaking things up aggressively into small components you can reason about in isolation tends to be the best way to write reliable code you can maintain over time.
This is so true. Something that has really improved my coding has been having a linter that whines to me about assignment branch condition size. Compared with learning how to properly stub methods in tests it has helped me break tasks down into simple manageable chunks with little room for error.
I find itβs also helpful to explicitly think about high level flow in the code. There are typically two types of code in an application. Thereβs routing code that figures out where the payload [β¦]
ββββ
ββββ