3 ms·
This has been my experience too. I've been involved cleaning up a half dozen or so projects that got out of control. In each case, technical complexity was bl
by mathattack 11y ago
This has been my experience too. I've been involved cleaning up a half dozen or so projects that got out of control. In each case, technical complexity was blamed as the reason. After digging in, I found that following commonalities:
- Incomplete, conflicting and misunderstood requirements.
- Lots of "We never thought we would need to do X".
- Poor team communication.
- Mistrust, frequently well earned.
- Harmony valued over truth.
Once these were winnowed away, the problems rarely overwhelmed the technical teams. This isn't to diminish the importance of technical skills. Rather - when everything else is f*cked up, you can't blame the technology or expect a 10xer to pull you out of it.
- crpatino 11y agoThe advantage of the 10x-er is that he will be reporting directly to a Jr. Executive and therefore cutting ahead of the middle management echo-chamber. If you genuinely can write code 10x as fast as the average developer, and get feed requirements through a 10x faster channel, that would be the life! I suspect that's where the mythical 100x developer comes from.
- mathattack 11y agoI agree. There are actually two 10x things that can happen - sometimes in one person. One is choosing the right things to do the first time around. The other is doing them very efficiently. When you get a developer who intuitively understands the domain, and programs very quickly, the sky is the limit. I certainly don't intend to diminish the impact of these 10x developers, just that projects generally get messed up independent of developer quality.
- BurningFrog 11y agoCleaning up buggy legacy code is a goldmine for learning what not to do.