The Development and Infrastructure Team Dysfunctional Relationship
If you spend any time making software in a big company whose primary job isn't making software, the following patterns about the development and infrastructure teams probably apply:
Unfortunately, as the mighty MC Hawking likes to riff, Order from disorder is a scientific rarity.
Whether it's outright silly and misguided arguments, or the "WTF are they thinking?" kinds of conversations had within each group after a meeting, it seems these two groups consistently spend too much time acting like slashdot commentors and not enough time reading Peopleware.
What's difficult about this problem is that it's not a technical problem. It's the natural result of two diametrically opposed organizational forces.
If the developers would just stop writing crappy software.
If the infrastructure manager would just stop being such a grump.
If the business would just go away.
Believe me - they'd love to. This whole time they're wondering why your crappy system costs them millions of dollars, and still doesn't work as well as their free Picasa photo album, which arguably does more than your system that's shoveling bits from A to B just like all the other thousands of companies exactly like yours. But that's a whole 'nother story coming up...(the software sausage factory from a normal person's point of view).
- The development and infrastructure manager are different people.
- The managers and their staff sit too far apart for osmotic communication.
- They are in calls or meetings together all the time.
- Yet angst abounds between the two groups all the time, whether it's overt or simple passive aggression.
Unfortunately, as the mighty MC Hawking likes to riff, Order from disorder is a scientific rarity.
Whether it's outright silly and misguided arguments, or the "WTF are they thinking?" kinds of conversations had within each group after a meeting, it seems these two groups consistently spend too much time acting like slashdot commentors and not enough time reading Peopleware.
What's difficult about this problem is that it's not a technical problem. It's the natural result of two diametrically opposed organizational forces.
If the developers would just stop writing crappy software.
If the infrastructure manager would just stop being such a grump.
If the business would just go away.
Believe me - they'd love to. This whole time they're wondering why your crappy system costs them millions of dollars, and still doesn't work as well as their free Picasa photo album, which arguably does more than your system that's shoveling bits from A to B just like all the other thousands of companies exactly like yours. But that's a whole 'nother story coming up...(the software sausage factory from a normal person's point of view).
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home