5 ms·
@alanctgardner2 Agreed, there are limitations. If that guy is a fan of cut-n-paste then there are bigger issues at hand than just social interaction. Working
by adeaver 14y ago
@alanctgardner2 Agreed, there are limitations. If that guy is a fan of cut-n-paste then there are bigger issues at hand than just social interaction.
Working in a siloed environment doesn't mean not learning new skills or techniques. And I don't mean that you are only working on the same project/chunk of code the entire time. We would often switch projects so that what I'm working on today is completely different that last week and has been touched/edited/tweaked by just about everyone on the team at some point.
Having a Big Picture perspective is vital be being able to work individually. You have to know how your work will ultimately impact everyone else and how their will impact you.
I don't mean that everyone is working on completely separate projects but that Employee 1 might be working on a feature enhancement on version 4.5.3 while Employee 2 is working on a refactor of the back end code and I might be working on implementing a change control request on version 4.5.4.
Perhaps this is a better way to explain: everyone is working on the same Project but on individual and separate Tasks
- alanctgardner2 14y agoThat just seems like every team ever, except for pairs programming I can't imagine having two people in the same part of the codebase at the same time. Is there an alternative you can think of that isn't just poor management, or ambiguous descriptions leading to conflicts? Also, you can reply even during the cooling-off period by hitting the 'link' link.
- adeaver 14y agoMajors bugs that involve both the front and back end developers. Major feature enhancements in which multiple devs touch the same set of files. There are probably ways around these issues, just some instances where I've had to sit next to someone and work out a bug/problem.