Just curious, does it matter? For some simple boilerplate code, simple test cases and simple skaffolding, which is needed in most applications, do you even care?
But simple scaffolding, test cases, boilerplate was around before LLMs via code generators/scaffolders, so yes, it’s revised history to pretend like an LLM invented those things. None of those things are complex ideas either.
I’m not sure I understand what you’re asking though.
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.
I love writing code, perhaps these software developers who do not will enjoy a different career once they LLM themselves out of this career. Writing 100k lines of code is a great achievement. Sorry to hear you’re so bored.
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.
But it doesn't cost time is the point; it'll just fall out faster than you can type. Each their own; we save tons of time and errors with it; ymmv and that's fine.
I'm yet to find a convincing definition for super intelligence. "Intelligence that surpasses human brain" is such a half hearted definition that I don't know what to make of it.
It would have made sense to have GraphQL support in cURL, had GraphQL been a standard transfer protocol rather than a query language. Support for query languages is out of cURL's scope AFAIK.
You can avoid this by allowing only specific queries in staging and production environments, this way, the introspection query can be disabled too.
Not sure if this violates the GraphQL spec though, because, ideally the server supports introspection, but it is disabled in some cases for safety reasons.
But if your limiting to only a whitelist of queries what's the difference vs a standard API? You might as well then just have a REST endpoint with the query defined on the server if your only allowing certain queries. Get your Javascript dev's to write a Node service or equivalent with the query logic inside it; that way the query logic doesn't need to be replicated per client.
This is where GraphQL shines. You give your developer a schema and "they" choose the queries and mutations they want to make to make their life easy. Also, there's very less friction because the GraphQL schema can be completely documented.
And while going to prod, you just allow the queries that are being used, disable rest.
1. Have you tried mindfulness meditation?
2. Which type of mindfulness meditation have you tried?
3. Why do you think it is useless when most people find it useful?
4. With what goal did you try the meditation that it seemed useless?
You cannot throw a word "useless" without emphasising the "use".
> Not everyone is perfect just how they are but everyone doesn't have to act the same way to be acceptable.
This undermines the very concept of "law and order". There "must" be restrictions on behaviour if it is intrusive, offensive, inflamatory, indecent etc. I think it is okay to have an enforced "code of conduct" to prevent assholery.
1) Laws are supposed to be precise. If there was a law against "stirring shit and troublemaking" as the OP suggests, it would be applied mostly against those who are out of favor.
2) Laws presume that the accused person is innocent and give them a say in defense. Good luck with that if you're accused of a code of conduct violation.
I respectfully disagree. I think most people would be okay with "average aesthetics" as long as the functionality of the product is designed well (flexible batteries in this case)
What looks good to 5/10 people, might not look good to the other 5/10. For an instance, consider an iPhone 4S. It is a pretty average design "aesthetically" IMO. But the phone did extraordinarily well because it was a well engineered phone. Another example is this website that you're looking at. I would call this average aesthetics as well.
Of course good aesthetics is an awesome add-on, but it is not fair to disqualify a product based on just aesthetics.
I slightly disagree because I prefer the code to be consistent all across my codebase.
Sure it is some effort to backtrack to the util functions, but I think the effort is worth it because I would rather have a developer spend multiple hours debugging and figuring out the code than having something that is a nightmare to iterate upon.
A lot of people are not comfortable with confrontation in the first place. And it is entirely normal. It just how people are wired and expecting them to change themselves drastically is not fair on them. It should be a gradual process and a thing like thoughter is a great use for "getting started". End goal is of course to confront.
Just curious, does it matter? For some simple boilerplate code, simple test cases and simple skaffolding, which is needed in most applications, do you even care?
reply