Process
-
Change through consensus
Nichol and Alec walk through the journey to making collaborative change and share lessons learned along the way. -
Frictionless developer environments
Reducing friction and pain points for new contributors can reduce your time-to-first-commit. -
Effective and easy strategies to hate bugs a little less
'I would rather fix bugs than work on the shiny new thing,' said no one ever. Still! You can make the experience more pleasant with simple bug strategies. -
What I learned from pairing by default
I never used to pair program, and then I spent four months on a pair-by-default team. Here's what I learned. -
Learning good habits by watching a staff software consultant
What is good software consulting? Watching a staff level engineer is a great way to learn good habits. -
Why are we adding another modal?
So you want to be a product-minded engineer? Minnie Lee shares personal perspectives and experiences around environments that foster these skills more naturally, plus the benefits for both the individual and the company. -
Do more with less: get scrappy and creative
What do you do when the economy, industry disruption, and more impact your team? You get scrappy and creative, plus plan to encourage and support innovation. -
Preparing for extended leave
Whatever the reason, your extended absence from the team at work shouldn't cause chaos. We have some tips on how to make the transition smoother. -
Architecture Decision Records help you, your team, and future teams
Architecture Decision Records (ADRs) can be a huge help to your team. Whether facilitating discussion or recording the Why, ADRs give you a way to understand and revisit team decisions. -
Why you need job descriptions at every stage in your software career
Find out exactly why job descriptions are a useful tool for software developers at every career stage.
1 of 3
