| ▲ | noduerme 2 hours ago | ||||||||||||||||||||||||||||
Other than the delay time, I'm not sure I see the difference. You're removing your primary from the job of writing code, putting them into an editorial role, which removes responsibility and agency and actual hands-on understanding. The quality of the code is beside the point. More friction (language barriers, time zone difference) is actually better if you want to maintain institutional knowledge, because it requires more intellectual engagement. Accepting the LLM answer is too easy and leads to a decay of the systems knowledge and of the thought process. [edit] as the sibling points out, decayed system knowledge leads to relying on the LLM to fix the bugs the LLM introduced, which causes further decay in the institutional ability to reason with the business logic in code. | |||||||||||||||||||||||||||||
| ▲ | someguyiguess an hour ago | parent [-] | ||||||||||||||||||||||||||||
I reject the premise that using LLMs absolutely leads to loss of institutional knowledge. It is trivial for an LLM to generate a knowledge base of any kind in any language which can answer any question about your institution at any time. How is a bunch of fragmented humans with limited knowledge who can’t all communicate with each other better than that? | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||