// Topics / Career
Career
Definition
Career coverage in this archive spans 4 posts from Jun 2017 to Jan 2024 and is treated as an operating model question: decision rights, feedback loops, and execution clarity. The strongest adjacent threads are leadership, engineering, and ai engineering. Recurring title motifs include engineering, ai, discipline, and music.
Working claims
- A repeated argument is that small teams ship faster when ownership boundaries are explicit.
- The consistent theme from 2017 to 2024 is disciplined execution over hype cycles.
- This topic repeatedly intersects with leadership, engineering, and ai engineering, so design choices here rarely stand alone.
How to apply this
- Write down ownership, escalation routes, and meeting defaults before scaling team surface area.
- Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
- When boundary questions appear, cross-read leadership and engineering before committing implementation details.
Where teams get burned
- Using process to compensate for unclear ownership and weak technical direction.
- Adding management layers before tightening decision loops and execution signals.
- Applying guidance from 2017 to 2024 without revisiting assumptions as context changed.
Suggested reading path
- Start here (current state): AI Engineering Is Its Own Discipline Now
- Then read (operating middle): Engineering Manager vs Tech Lead: What’s Actually Different
- Finish with (foundational context): Leading Without a Title — What Actually Works
Related posts
- AI Engineering Is Its Own Discipline Now
- 2022: The Year the Music Stopped
- Engineering Manager vs Tech Lead: What’s Actually Different
- Leading Without a Title — What Actually Works
References
4 entries tagged “Career”