Earlier quoted context omitted.
>What do you mean by that? Varied and novel to the programmer . If you're doing the same thing day in and day out it probably isn't much use. If you're like many programmers and you're jumping between libraries and languages and platforms and APIs and domains and spheres, it's immensely helpful. >doing mainstream, well-trodden work for which a company’s/project’s/domain’s inside knowledge isn’t needed A core disconne…
Everything isn’t well-trodden. I’m mostly doing non-glue, heavily domain knowledge-based work. The main issue I’m running into is that explaining the domain and context to the LLM will take significantly more time than just doing the work myself, and also that parts of the necessary knowledge and most of the source code are NDA-protected, so only a local LLM would do.
Everything is extremely well-trodden at the code level. You're taking some inputs and generating some outputs. You're calling some functions. You're manipulating some strings or lists or sets. You're sorting some things or filtering things. You're building a client to a given API. You're doing some messaging and some encryption.
I guarantee that your code isn't remotely as unique or novel as you think it is. Of course on here everyone is 240lbs, 6'2" and benches 350, and their magically novel, super unique code is just too secret. So everyone's special.
If you had to explain the domain and context to these tools, you might be using them wrong.