Writing from the workshop.

Treating future changes as a design constraint leads to calmer software.

A useful metric should help someone decide what to do next.

Keeping Go interfaces close to consumers produces simpler and more flexible code.

Admin interfaces should reduce hesitation and make common work feel obvious.

Designing Go services that explain what they are doing when production gets difficult.

Why predictable systems often outperform clever ones as teams and products grow.

Practical notes on keeping systems legible for teams building software that should remain calm and understandable.

Practical notes on designing for reversibility for teams building software that should remain calm and understandable.

Practical notes on writing practical error messages for teams building software that should remain calm and understandable.

Practical notes on simple queues and clear work for teams building software that should remain calm and understandable.

Practical notes on naming the important things for teams building software that should remain calm and understandable.

Practical notes on interfaces that explain themselves for teams building software that should remain calm and understandable.