|
|
|
|
|
by anonzzzies
540 days ago
|
|
While true, LLMs are just a more advanced version of it. Let's take Go as example as that is a very boilerplatey language; with claude, I only have to write the meat, for instance; result, err:= doSomething() and it'll generate the rest around it. Every time. Faster than I would type it and with more eye for detail (I am lazy, I will forget things as I did it now the 10004th time). So you can imagine some boilerplate scaffold thing that would do this err handling for you, but if you have a custom one, for 'old' tools you would have to tell the tool; now it just does it. It especially becomes clear in frontend tasks: it just generates 100+ lines of react that work and look good; who likes writing they type of thing manually? I know 0 people who do: after that you will want to tweak it, but the 100k+ lines of react we generally have in a project are not something we would want to write these days from scratch. Which old school scaffold etc tool does that? So that it is 80-90% there for SaaS first shot? I know nothing (doesn't exist) without the lovely verboseness of having to type a million tags? It saves us a lot of time we don't have to spend on boring stuff. We only have to write the actual business logic and data models; the rest drops out. And of course we only have to write that very loosely, not formally. |
|
What is boring is the time I’ve wasted on a recent project fixing all of my coworkers LLM mistakes. I think I’ve nearly rewritten the entire php wordpress plugin. So his work really was a waste of time.
For golang I have never had a problem writing if err != nil. It takes a few seconds, paying some LLM company to write something I could write myself but I don’t want to because “I’m bored” is ludicrous use of time to me.