▲ 2 ▼ the binding constraint has moved from 'can you build it' to 'can you tell whether it’s right' (www.brethorsting.com) submitted 5 months ago by zecg@lemmy.world to c/stuffandsuch@lemmy.world comment fedilink hide all child comments
[+] mabeledo@lemmy.world 12 points 5 months ago (4 children) [deleted] permalink fedilink source hideshow 4 child comments replies: [–] cschreib@programming.dev 3 points 5 months ago (3 children) You end up with a nice spec that you wouldn't have had otherwise? That has value even if you discard all the LLM-generated code. I think experienced engineers are able to go straight from a vague requirement to an implementation without that intermediate step, and that power is easy to abuse. We build an implicit spec on our head, which gets translated to code on the fly, and then gets forgotten. Not defending the LLM technology, but i do think this is one of the upside. permalink fedilink source parent hideshow 3 child comments replies: [+] mabeledo@lemmy.world 4 points 5 months ago (2 children) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] cschreib@programming.dev 1 point 5 months ago (1 child) I think this will depend on the industry. Slow vs fast moving, regulated vs not, whether someone depends on your API or not, etc. But regardless, having had to deal with some legacy code written 10 years ago by someone who isn't working at the company anymore, I would take an outdated spec over none at all. At least then I know what people intended back then, what they cared about, what they had and hadn't considered. As long as the spec is written by a human, that information is surely valuable. permalink fedilink source parent hideshow 1 child comment load more comments (1 reply)
[–] cschreib@programming.dev 3 points 5 months ago (3 children) You end up with a nice spec that you wouldn't have had otherwise? That has value even if you discard all the LLM-generated code. I think experienced engineers are able to go straight from a vague requirement to an implementation without that intermediate step, and that power is easy to abuse. We build an implicit spec on our head, which gets translated to code on the fly, and then gets forgotten. Not defending the LLM technology, but i do think this is one of the upside. permalink fedilink source parent hideshow 3 child comments replies: [+] mabeledo@lemmy.world 4 points 5 months ago (2 children) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] cschreib@programming.dev 1 point 5 months ago (1 child) I think this will depend on the industry. Slow vs fast moving, regulated vs not, whether someone depends on your API or not, etc. But regardless, having had to deal with some legacy code written 10 years ago by someone who isn't working at the company anymore, I would take an outdated spec over none at all. At least then I know what people intended back then, what they cared about, what they had and hadn't considered. As long as the spec is written by a human, that information is surely valuable. permalink fedilink source parent hideshow 1 child comment load more comments (1 reply)
[+] mabeledo@lemmy.world 4 points 5 months ago (2 children) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] cschreib@programming.dev 1 point 5 months ago (1 child) I think this will depend on the industry. Slow vs fast moving, regulated vs not, whether someone depends on your API or not, etc. But regardless, having had to deal with some legacy code written 10 years ago by someone who isn't working at the company anymore, I would take an outdated spec over none at all. At least then I know what people intended back then, what they cared about, what they had and hadn't considered. As long as the spec is written by a human, that information is surely valuable. permalink fedilink source parent hideshow 1 child comment load more comments (1 reply)
[–] cschreib@programming.dev 1 point 5 months ago (1 child) I think this will depend on the industry. Slow vs fast moving, regulated vs not, whether someone depends on your API or not, etc. But regardless, having had to deal with some legacy code written 10 years ago by someone who isn't working at the company anymore, I would take an outdated spec over none at all. At least then I know what people intended back then, what they cared about, what they had and hadn't considered. As long as the spec is written by a human, that information is surely valuable. permalink fedilink source parent hideshow 1 child comment load more comments (1 reply)
[–] tyler@programming.dev 3 points 5 months ago That $500 million dollar bill says otherwise. permalink fedilink source
no comments (yet)