3 ms·
As someone who has done lone-wolf development, let me tell you that so many issues go away once you develop a well-functioning team to work on problems collabor
by hatsix 10y ago
As someone who has done lone-wolf development, let me tell you that so many issues go away once you develop a well-functioning team to work on problems collaboratively.
My initial reaction is that there seems to be much bigger issues with the way your company is structured. The words you're using ("lone", "carved", "straining on the edge") suggest a stressful situation where each individual carries their own weight... If that's the case, I can certainly see why you'd be upset by someone else impeding your ability to work. I wouldn't last long in an environment like that, either pushing it to be more collaborative, or just leaving.
I can't imagine any coding that isn't improved by adding collaboration (a great starting point is code reviews... make PRs early and get opinions on rough-cuts). If you don't have this in your current environment, I highly encourage trying to kickstart it... you're really missing out on a great way to remove stress, improve quality, and have more fun.
- fsloth 10y agoSorry, I was perhaps not quite precise enough. I agree that collaboration on complex technical topics is wonderfull. There is quite a lot of collaboration and we do have a great team. The system is divided to many components and each of those components has usually only one or two active developers. The inherent technical complexity of the components is such that sometimes a feature needs days of coding - thus the 'more locksmith, less of a ballgame' analogue. I should have perhaps pulled some other analogue.