We have launched a new blog for small nuggets of technical information ('bytesized' - geddit?) that we have picked up along the way.
In this blog I’m going to talk about some strategies that we are experimenting with to help us improve our pairing and work more effectively together. Whilst suggestions to help improve pairing often focus on behaviours whilst pairing, I’m going to focus on things that you and your pair can do before and after pairing to plan and review how you work together.
How can we change our behaviour to have more positive code review experiences? Here is a simple framework we can follow.
We introduced participants at a pairing workshop to a framework for “pre-pairing” conversations, designed to help anticipate and prevent communication difficulties during pairing. The overwhelmingly positive feedback from the workshop reinforced to us how valuable this technique can be.
Module nesting in Elixir is syntactic sugar with some unexpected (undocumented) alias and import behaviours
A short introduction to the concept of circuit breaking in programming.
We recently had the opportunity to make a Visual Studio Code extension that needed to communicate with an embedded device. This post explains the architecture we chose to achieve that and the decisions that led to it.
We open sourced our shared configuration for tmux, Spacemacs and other tools we use daily for development
Cultivate do not differentiate between Front End and Back End Developers, yet we acknowledge that expertise in either field is too difficult for most people to achieve. How do we resolve this apparent contradiction?
Winning an argument by conceding in good faith