curated-content
Curated Content September 2022
A few pieces of content I thought were worthwhile in the month of September.
Britton Broderick
Sharing experiences, practices, and learnings to improve the field. Experienced startup CTO, DevOps practitioner, and software engineer. Avid reader and audio book listener.
programming
Strong Style Pairing and Mobbing - The Smart Keyboard
One of the most powerful approaches to pairing or mobbing is “strong-style”. To utilize this style, you just need one simple rule: In order for an idea to go from your head into the computer, it must go through someone else’s hands. The navigator in a traditional pair (or
curated-content
Curated Content August 2022
A few pieces of content I thought were worthwhile in the month of August.
curated-content
Curated Content July 2022
A few pieces of content I thought were worthwhile in the month of July.
curated-content
Curated Content June 2022
A few pieces of content I thought were worthwhile in the month of June.
management
Trust, Care, and Word Choice
If you're an organization leader like me, at some point you've uttered the phrase "I don't care", but what you really meant was I trust you.
culture
You're Here to Solve Problems - Not Write Code
Code is often a useful tool to solve problems. But it can be the wrong tool. It’s expensive to write, and even more expensive to test and maintain.
curated-content
Curated Content May 2022
A few pieces of content I thought were worthwhile in the month of May.
fundamentals
Using Architectural Decision Records
ADRs are a powerful tool for understanding why decisions were made and reflect on if and when it’s appropriate to change them.
curated-content
Curated Content April 2022
A few pieces of content I thought were worthwhile in the month of April.
testing
Tests as Documentation
Tests are more valuable when they serve as documentation, and define the implementation of specification.
fundamentals
Adding the Stopwatch to Level Up as a Software Engineer
By adding the stopwatch, you can understand the effects of time on your software quality. Then use the understanding to improve faster.