3 ms·
NGL I'd argue there's a certain appeal to "use AI to prototype a feature as fast as possible and focus your engineer hours on building a comprehensive testing a
by OneDeuxTriSeiGo 3mo ago
NGL I'd argue there's a certain appeal to "use AI to prototype a feature as fast as possible and focus your engineer hours on building a comprehensive testing and fuzzing plan" followed by a "remove and review everything that can be cut without breaking the tests" cleanup pass.
- fwlr 3mo agoI do see the appeal, it’s easy to imagine that workflow working, and working well - but it’s hard to how it avoids this fate: https://youtu.be/QEzhxP-pdos https://youtu.be/QEzhxP-pdos
- Cyberdog 3mo agoThe “cleanup pass” never happens, though. It’ll just be new feature on top of new feature until it’s too large to refactor.
- colordrops 3mo agoExcept it does. It's not some law of physics. I've done exactly this on multiple projects, both personal and corporate.
- dymk 3mo agoYou're describing a problem that's plagued corporate software development for decades. You just get to the "unmaintainable ball of mud" stage faster now. Every few days I spent a while on codebase architecture improvements after landing a slew of features.
- OneDeuxTriSeiGo 3mo agoThat's a leadership failure not a technical failure. If you can't dig your heels in and force time to tidy up technical debt then you need to find someone who can and let them take over as PM.