How Knowledge Flows: Hallway or Document?
Knowledge stuck in one person's head and knowledge buried in a wiki nobody reads end up the same way: the reasoning behind a decision is unreachable.
All posts 
Tag
#Career
A software career: seniority, responsibility, changing jobs and the skills that last. (Page 2/4)
There are 22 posts with this tag.
Role Boundaries: Where There's No Job Description, Everyone Does Everything
A role gap closed by individual sacrifice becomes invisible — and an invisible fault never gets fixed. Drawing a boundary, from three desks.
When Is Process Armor, and When Is It a Shackle?
Process isn't a virtue — it's a coordination tax you pay. When it should be added, why it never gets removed, and how it looks from three different desks.
How Decisions Get Made: Approval Chain or Single Signature?
Companies don't fail at going fast or going slow — they fail at matching the speed to the decision. A reversibility frame, and three desks to view it from.
Corporate or Owner-Run? Size Isn't What Separates Them
What separates company types isn't headcount but where decisions are made and how much reasoning gets written down. Four axes, three desks.
Vibe Coding vs AI-Assisted Development — and Why You Still Need a Senior
Vibe coding made shipping easier, but what someone without systems knowledge ships isn't what a senior steering the AI ships. Three levels.