Surviving the Organisational Side Quest — No Idea Blog
noidea.dog/blog/surviving-the-organisational-side-quest
What Jamie wrote
Video game analogy to working through blockers across multiple teams. The reference to this as a component of dealing with growth is spot on.
A key engineering skill is noticing what’s blocked, and figuring out why, following a thread of hints from person to person until you can see what's not moving. You might end up asking the same question again and again. You might get handwavy responses that seem like answers but don't actually give you extra information. That’s how these games go.
Read the above and think about that for writing code. It’s the same thing, just applied to a different system.
Saved the same week · 11 links that week
- I Add 3-25 Seconds of Latency to Every Page I Visit
- Why are we so bad at software engineering? | www.bitlog.com
- How I Stopped Checking My Phone So Much - For The Interested - Medium
- 1on1-questions: Mega list of 1 on 1 meeting questions compiled from a variety to sources
- Wikipedia Is the Last Best Place on the Internet | WIRED