Teamwork
45 articles
- The one thing every experienced engineer gets wrong
- Theory of constraints, AI, and code review
- You get what you hire
- Relentlessly focus on the outcomes
- Engineering levels aren't about skill anymore
- Just fix their PR
- The best engineers just get shit done, sometimes with AI
- In praise of the stacked pull request
- Small projects, clear scope
- How to lead a project
- *People* detangle a ball of mud
- The unreasonable effectiveness of stack ranking
- The job behind the job [of a high level IC]
- Leadership lessons from growing 3x in 1 year
- Pair programming
- A few more thoughts on mentoring
- My mentoring philosophy
- Software architecture IS Conway's Law
- Stateless decision making
- How do you find time for cleanup work
- re: The Industrialization of IT
- What to work on next?
- Always deploy at peak traffic
- The difference between a product and a project
- Sprint vs Shape Up vs Kanban
- Why sprints
- Principles of high output engineering teams
- Code yourself out of the job
- How *do* you break down a large project? INVEST
- How do you prioritize?
- Coaching AI to write your code
- Why learning and teaching the good stuff is hard
- The swarm doc
- "Yes caviar is great, here's a ham sandwich"
- Make mistakes easy to fix
- How big up-front design fails
- What helps you ship confidently?
- Get us over the water, not build us a bridge
- Coordinating at the end is too late
- Approve with comment
- Code yourself out of the job
- The quickest way to kill a team
- The answer to 5 soloists in a trench coat
- 5 soloists in a trench coat
- Effective standups