|
|
|
|
|
by jauntywundrkind
177 days ago
|
|
Conceptually yes, but trying to understand what affordances you have what tools you can use what options are about, to begin to then decide to learn those systems, is incredibly incredibly hard. With LLMs, you can ask for what you want and it can assess approaches. And try to solve. And adjust rapidly. Trying to understand what affordances are available has been a nightmare of computing. Yes people do incredible things & take ownership of systems in amazing & incredible ways! But I just think it has required such deep esoteric knowledge just to get started, to have an idea of where you have leverage. I really think there's such a chance for more agency here, and without such being totally lost and confused and having no idea and so little help pointing the way. |
|
And programming isn't? It requires even deeper esoteric knowledge about language intricacies, build systems, architectures, etc.
LLMs might help with getting a prototype up and running, but fixing issues or adding new features to an existing codebase still has a low success rate, and high chances of introducing other issues. These chances are directly proportional to the size and complexity of the software. Often the only way to address these issues is for the user to dig into the codebase themselves, which becomes a gargantuan task if they don't have an understanding of it to begin with.
So, sure, these new tools are useful for writing small and dirty scripts as the author needed, but then again, they can also be used to write configuration, help with integration issues, and to gain understanding of existing software. Asking them to write software is a riskier proposition, IME. Especially if that software is released into the wild and is used by more than one person.