Tagged - process
Code should communicate intent
It's one thing to write code that does the thing. It's another to write code that tells the reader what it's doing
Team Topologies: Beyond the Spotify Model
On Handling Incidents
A few things I’ve learnt about handling incidents.
On Prioritising
Some heuristics on how to pick the highest value thing to work on when embedded in a product team.
Implementing Lean Software Development
Book Notes
Dan North - Value of Flow
discusses the concepts of flow efficiency and resource efficiency and emphasizes the importance of optimizing flow to achieve real efficiency.
On Assigning your team to full capacity
The title here is misleading, because I’m here to make a case for not assigning your team to full capacity.
Pull Request Etiquette
We’ll look at this from two perspectives, the pull request author, and the reviewer
Ambient Pair Programming
Shared room, different tasks
Weekend Longreads #1
Some long form content
Ping Pong Pair Programming
An asynchronous pair programming method
Denis Čahuk on Estimates
Communicating our understanding of the problem and Forecasting completion of the solution
on small PRs
If a task is big enough, multiple small & focused PR's are a solid way to approach it
On Refactoring
Some musings & observations on refactoring
Flow of Value through a system
Putting together all related resources around this topic.
Energy Management
An alternative or add on to time management
Feature Flags
Some things to think about when considering feature flags
Pitch → Shape → Kickoff -> Commit → Cooldown
MTTR > MTBF
Optimising Mean Time To Recovery is more important than trying to minimise Mean Time Between Failures.
Book Notes: Engineering Management For The Rest of Us
highlights, quotes, & other interesting bits from Engineering Management For The Rest of Us
Pull Requests & WIP
I often open Pull Requests immediately when I start on a task.
On WIP Limits
How WIP limits can help your team ship software faster, & more effectively
Cognitive Load Theory
How can this theory can be a helpful heuristic for effective team design
Book Notes: Team Topologies
highlights, quotes, & other interesting bits from Team Topologies
Team topologies with James Lewis
Thoughtworks' James Lewis shares his experience & research on Team Topologies, software architecture, & complexity science
Team Topologies: ING Bank
A case study of ING bank and their experiments with team topologies
Dan North - Patterns of Effective Teams
Notes from an insightful talk by Dan North
Book Notes: Accelerate
highlights, quotes, & other interesting bits from Accelerate
How I work
My values, and how that translates to my preferred ways of working & communicating
Notes & Resource: Martin Fowler
Various lessons and clippings from Martin Fowler.
Shape Up - writing the pitch
Summary of the ingredients that make up a pitch…
Shape Up - The shaping process
Summary of Part 1 of the book…
Introduction to Shape Up
Ryan Singer shares how the Basecamp team builds software…