The Unreasonable Effectiveness of Pair Programming
One of my favorite parts of work is pair programming. At first glance it may seem like a waste of time, having to include two developer’s time instead of just one, however I have found it pays it back in coming up with more robust solutions. Having a bit of time to think through opposite ends of a problem and not get pidgeon-holed into one route or solution is good, and I have often found or been reminded of edge cases while working with another dev.
Another aspect of this interaction with my job is the cool range of people I get to work with. For analytical efforts, getting to pair program with an analyst stretches me into that domain, while I can hopefully share some more CS focused concepts that may be useful to them. This is also something that comes up when we have aero engineers who flex into CS roles, and vice versa. This overlap on the Aero-CS and analyst-CS spectrums is where I find most of the useful work getting done, as well as being the most personally rewarding.
Written by a human.
For questions, bug reports, or complaints, please contact me!