Scaling Fast Book
74 articles
- Taming chaos is a learnable skill
- Probably the realest thing I ever wrote
- The 3 curves that make a scalable business
- In praise of the stacked pull request
- How you migrate is everything
- The future of software engineering is SRE
- Place good startup bets
- Small projects, clear scope
- *People* detangle a ball of mud
- The unreasonable effectiveness of stack ranking
- Make sure it works first
- Leadership lessons from growing 3x in 1 year
- Yes it's like spinning plates
- Quick update on Scaling Fast, my next book
- Software architecture IS Conway's Law
- Common abstraction traps
- DRY – a common source of bad abstractions
- Say no to abstract code
- re: The Industrialization of IT
- 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
- What I learned from Accelerate
- Looking for beta readers
- Atoms, molecules, organisms
- Smart core, thin interfaces
- Empirical evidence for code modularity
- Finding modules in a big ball of mud
- Why you need observability more than tests
- The swarm doc
- Big Ball of Mud – the world's most popular software architecture
- Why software only moves forward
- "Yes caviar is great, here's a ham sandwich"
- Make mistakes easy to fix
- The Laws of Software Evolution
- The Series A inflection point
- You can side-step a yak, they don't all need to be shaved
- Better is good
- How big up-front design fails
- Why software projects fail
- Let small fires burn
- 90% of performance is data access patterns
- DRY – the common source of bad abstractions
- Scaling Fast, my talk on lessons from tech startups
- You can't side-quest a product
- The dangers of spurious automation and how to automate anything
- It’s okay to just do the work
- Notes for my Scaling Fast talk next week
- How to use feature flags
- Validate your assumptions early
- A better roadmap solves many issues
- Get us over the water, not build us a bridge
- Coordinating at the end is too late
- Approve with comment
- Architecture is like a path in the woods
- 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
- The market always wins
- Why you need a regular retro
- 5 tips for effective standups
- Can I get your opinion
- Ask me a question
- Two types of complexity and their impact
- You can't fix the wrong abstraction
- DRY vs SoC, a difficult choice
- Coding forces you to understand the problem
- Writing software is like kicking a can
- WorkInProgress kills your progress
- Tech debt is a tool