4 ms·
More than one project manager has insisted that everything about the system must be documented--that's called the source code. As you say, by the time you spec
by Buttons840 1y ago
More than one project manager has insisted that everything about the system must be documented--that's called the source code.
As you say, by the time you specify everything, you've written the code.
- smcg 1y agoTheoretically a PM could say "the code is disposable and obsoleted by the next deployment. let's just document our prompts." I don't know if that's a good idea but a lot of people are going to try it.
- __loam 1y agoThis is an obviously terrible idea that will lead to regressions on every deployment.
- fragmede 1y agoI'm afraid you're going to have to spell it out for the kids in the back who aren't paying attention.
- seangrogg 1y agoHow long should we wait after promotions before prompting to add logging back to the service?
- kibwen 1y agoWho needs logging when we can just ask the LLM to confabulate the logs?
- jjmarr 1y agoIt's like NixOS but instead of the much-maligned Nix language, you can use the English language! What could go wrong?
- bee_rider 1y agoThe prompts are the source code in that case. The LLM is some sort of transpiler. Somebody will have to add some syntax to these LLM prompting systems to include text that doesn’t get converted. So the next round of PMs can ask you to documents your prompts).
- testing22321 1y ago> As you say, by the time you specify everything, you've written the code Sadly not when it’s a 2000 page word document with a million formatting quirks and so many copy-paste versions you don’t know if you should trust “reqs_new25”, “reqs_new25v1” or the x number of other copies floating around.
- bee_rider 1y agoSomeone should come up with a tex2fortran conversion LLM.