By calling iterations "Sprints", Scrum implies a need for constant running. Don't be fooled.

Frequently delivering software, but not considering feedback on how to improve, isn't agile.

Don't focus on lofty goals. Fcus on daily making the code a little bit better.

Maybe strict TDD isn't necessary for experts, but it's still useful to learn.

It's not the red/green/refactor cycle. The important thing is working in short test/code or code/test cycles.

What does "transparency" even mean? What decisions could you make differently if you had it?

Various strategies to logging and log management and what you can start implementing today.

Write code as if every function is a doorway, and every reader of my code will always experience the doorway effect.

An alert that you can't respond to is a wasted alert. But monitoring can cover anything.

With different teams responsible for development and release, we often end up with silos.

A deployment failure should go through standard alert channels, but should it page whomever is on call?