Technology
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
view the rest of the comments
As I'm slowly evolving my own flavour of spec driven development, I'm starting to think about the generated code as a secondary artefact where main quality criteria is that it's doing what it needs to and it's covered with tests.
I guess my current analogy is that I don't care about how readable or dry is the assembly code generated by compiler.
I have the specifications and the working code with tests. I can always regenerate it if I need to.
But. I still read the produced code, steer the design and correct the obvious blunders. No vibes.
Might want to read on TDD, it's been around since last the last millennium (OK 1999 according to Wikipedia, point is, it's not new).