Articles providing tips to pair program are ubiquitous. Instead, let's talk about pair exploring, including why and/or when to pair program.
Over time I've become better at making the pairing experience better for me and my pair. Here are some tips to pair program more effectively.
When it feels that the learning has slowed down, this is usually a good time to switch to a new pair. Or, switch at the completion of a story or task.
How can a pair disagree while keeping their working relationship healthy? Treat each problem as a negotiation, and we can turn disagreements into solutions.
The skills I spend honing at work are not just applicable to my tech career. I've learned you can power your cause work with your day job.
Removing knowledge silos allows for long-term project success. Here are a few practices my team has put in place to support continuous knowledge transfer.
The next step in our design process for creating an app was an audit of features. The benefit of this audit is determining context, value, and priority.
Product designers and developers commonly have a push and pull relationship, but what happens when they decide on pairing to design an app?
We weren't trying to think up the next great experimental idea. Instead, we were looking to be the best practitioners we could be — taking good new ideas and refining them.
A new perspective on old code can help spur refactoring that will not only make the app more usable, but will also make it a better environment for makers.
Since I joined Atomic in June, "Teach and Learn" has played an important role in both my career as a developer and my becoming a part of the Atomic team.