davefarley77.bsky.social
Software Engineer, Consultant & Author.
The Modern Software Engineering Channel: https://www.youtube.com/@ModernSoftwareEngineeringYT
Support Me On Patreon: https://bit.ly/ContinuousDeliveryPatreon
69 posts
1,959 followers
23 following
Prolific Poster
Conversation Starter
comment in response to
post
Hi Richard. I'm open to suggestions and it may well inspire something I'd like to cover.
comment in response to
post
Code ownership leads to one-person silos, hindering collaboration and making the organization vulnerable when someone is absent. Shared code ownership is a stronger model. Pair programming breaks down those barriers by allowing devs to familiarize themselves with different parts of the code base.
comment in response to
post
Download my FREE guide on adopting GREAT developer habits: www.subscribepage.com/great-progra...
comment in response to
post
Absolutely, treat every story as an experiment, and monitor the results. It’s the only way to steer our products toward success!
comment in response to
post
This would require developers to become active participants in the business, which I appreciate may have many running screaming for the hills. But asking users what they want or need is by far the least effective way of finding out :-)
comment in response to
post
Not specifically on that topic, but I do talk about it in this video
youtu.be/aItVJprLYkg
comment in response to
post
By @jezhumble.net & @davefarley77.bsky.social
comment in response to
post
Best not to organise too rigidly. All combinations seem to work, they just have different characteristics. My preference for teams, once they have some experience of PP is to rotate pairs daily, so everyone gets to pair with everyone. That way learning for the whole team happens fastest.
comment in response to
post
2 juniors works, but they need some external oversight, but that is true, pairing or not.
comment in response to
post
There are certainly differences with different people, but problems are very unusual
comment in response to
post
…and pretty easy to adapt to for most people.
It’s possible that somehow, magically, the teams I worked on had these skills by accident, but I don’t think so. I think pairing helps teams to get better at working together, that’s part of the win.
comment in response to
post
Get better “experienced programmers” perhaps. My experience has been that the really great experienced programmers do whatever it takes to make the team successful. Including doing some of the less glamorous bits!