3 ms·
I've personally adopted doing multiple refactoring passes after any large code implementation done by AI. In pretty much any scenario where I'm adding code usin
by _fat_santa 1mo ago
I've personally adopted doing multiple refactoring passes after any large code implementation done by AI. In pretty much any scenario where I'm adding code using AI, it's 1 turn to add the feature and and then another 4-5 turns to refactor and clean everything up.
Often times it's not even that the code is bad but rather that it's overengineered. I see it happen so much that I'm tempted to actually go the other way on a toy project. Like what would Claude or Codex come up with if I told it I wanted an enterprise grade, globally scalable, compliant and auditable tic-tac-toe game.
- goldenarm 1mo agoReminds me of the "entreprise grade fizzbuzz" https://github.com/enterprisequalitycoding/fizzbuzzenterpriseedition https://github.com/enterprisequalitycoding/fizzbuzzenterpris...