4 ms·
The more jobs I have the more I think collective code ownership is the problem. I've never worked at a place where that hasn't resulted in a sprawling mess. No
by lacampbell 10y ago
The more jobs I have the more I think collective code ownership is the problem. I've never worked at a place where that hasn't resulted in a sprawling mess. No methodology will save it.
- ZenoArrow 10y agoI know this is going against the grain here but, have you ever worked somewhere that followed the Waterfall methodology? For all its problems, the one thing I've found it works well for is cutting down on technical debt. Developers get requirements up front, and documentation can be planned out alongside development. You do need skilled business analysts/project managers for it to work well, but it definitely cuts down on the sprawling mess I've seen in Agile. I'm sure Agile can work well, but from my limited experience too much emphasis is placed on moving fast, resulting in considerable technical debt (not a problem if a codebase is small enough that a team can entertain the idea of a rewrite, but it's disastrous for large codebases).
- lacampbell 10y ago> I know this is going against the grain here but, have you ever worked somewhere that followed the Waterfall methodology? I haven't. I feel like the simple waterfall model is too rigid, but one of the modified versions would work well. I am trying to design more of my code upfront these days, and spend less time coding directionlessly. Trying to become more prolific. Waterfall seems to encourage that.