#collaboration

How architecture can guide teams with clarity without limiting freedom.

Solution notes are short, searchable records of problems and their fixes.

How i stopped worrying and learned to love failure (or at least learned to live with it).

Want your team to perform at its best? Add some slack!

A walking skeleton forces developers to talk, aligning both code and teams from day one.

If you want to get more done, focus on finishing rather than starting.

I think a team with a sense of purpose works better than one with a sense of urgency.

A guide to writing technical documentation that is clear, informative, and fun!

When developers ask difficult questions it is often a sign that they care.

Don’t be a backseat driver, trying to take over the PR through comments.

Are developers rational machines or just out of touch with our emotions?

Create abstractions to communicate intent to your fellow programmers.

A few examples of how viewing tests as documentation can affect your test writing.