Three patterns that appear constantly in real codebases - what problem each solves, what the structure looks like, and where you have already seen them.
The compiled vs. interpreted distinction is blurrier than you think, and understanding the spectrum explains tradeoffs you make every day.
JavaScript is single-threaded but non-blocking. The event loop is the mechanism that makes both of those things true at the same time.
You do not need Haskell. Pure functions, immutability, and composition will improve code in any language you already use.
Most teams argue about Gitflow vs trunk-based development. The better question is what you are actually trying to solve.
Two concepts that are constantly confused and constantly misimplemented. Here is what each means and how to get both right.
MVC, MVP, MVVM, MVI - the patterns for structuring mobile apps explained through what problem each solves, not just what the letters stand for.
Three more patterns from the everyday toolkit - adding behavior without inheritance, bridging incompatible interfaces, and treating actions as objects.
A code review is not a gatekeeping exercise. Here is what makes them useful - from both sides of the diff.
Refactoring is changing structure without changing behavior. The hard part is keeping those two things separate.
What actually happens between your SQL query and the rows that come back - storage pages, the query planner, and why understanding this makes you a better developer.
