A place to begin 06 ways in
You don’t need to know the technical term. Find your situation, open one useful first read, and see where to go next.
You can follow code, but the ideas underneath it still feel abstract.
First read
Binary tree vs binary search treeStart with one simple ordering rule and see why it changes how much work a search needs.
You need to split responsibilities or explain a design decision to your team.
First read
Bounded contexts, concretelyLearn where to draw a boundary by finding the same word with different meanings in different parts of a system.
A query is slow, an index seems ignored, or you want to understand how data is stored.
First read
Why PostgreSQL is not using your indexCheck whether the predicate fits the index, then compare the planner’s estimated costs before changing settings.
You want AI to help ship changes, with checks and people in control.
First read
What a software factory isSee how small agents hand work to each other, where review happens, and how a change reaches production.
You want to explain your reasoning, not memorise a list of answers.
First read
Big-O without the ceremonyGet clear on how work grows with input size, a useful starting point for explaining algorithm trade-offs.
You can ship code and want to understand what the next level asks of you.
First read
What actually changes between mid and seniorUnderstand the move from implementing a decision to helping make it, and recognise it in your own work.