Because there is nothing remotely close to Laravel for JS. I don't want to think about auth, job queues, mailing, cache layers, auditing etc. I want an opinionated default from my framework that is thoroughly documented and part of the AI training corpus. Laravel gives that to me.

>single-handedly keeping PHP relevant

While architecture astronauts are clutching pearls, I've built multiple profitable products with Laravel without caring the slighest about the internals, both before and after AI.

PHP was always all about just building stuff while ignoring code quality. Laravel is a natural extension of that approach. Let us live.

I agree, but what you describe is agile, not Agile (capital A).

Agile (capital A) is Scrum (capital S) where you have Backlog Grooming (patent pending) where the team clears any ambiguity to define a spec (ticket).

Deviating from said spec is seen as Scope Creep (gasp) and might lead to complaints during Sprint Review (trademark).

So yes, agile prefers working software over detailed spec. But typical manifestations of Agile (capital A) are exactly the opposite.

Sending armed agents at protesters is seen as being the same thing as sending pest control to clear out beaver dams on the creek. Nobody cares what the beavers think, they are not human, they do not have feelings. They are simply a menace to be dealth with.

The author didn't, and used a general tool to their aid - why is that unfortunate?

The IF is doing a lot of heavy lifting there.

I understood the OP in the context of "human history has not produced sufficiently many tokens to be sent into the machines to make the return of investment possible mathematically".

Maybe the "token production" accelerates, and the need for so much compute realizes, who knows.

Or at least that's what many C-level people believe to be true. "We need to move like a startup" is a common mantra repeated by executives, even megacorps like Amazon.

I guess it's true to some degree though, anecdotally as an IC at a tech company, I feel like I could move a lot faster if some people around me removed and replaced by an automation instead.

Not stupid, just corrupt :)

If we did this, the money would get misappropriated or stolen - most likely completely legally through overpaid consulting fees.

So clearly we should pay someone to prevent that from happening.

Wait a minute...

Anecdotally, the last three greenfield projects I was a part of, the Architects (distinct people in every case) began the project along the lines of "let us define the microservices to handle our domains".

Every one of those projects failed, in my opinion not primarily owing to bad technical decisions - but they surely didn't help either by making things harder to pivot, extend and change.

Clean Code ruined a generation of engineers IMO.

I teach at an internship program and the main problem with interns since 2023 has been their over reliance on AI tools. I feel like I have to teach them to stop using AI for everything and think through the problem so that they don't get stuck.

Meanwhile many of the seniors around me are stuck in their ways, refusing to adopt interactive debuggers to replace their printf() debug habits, let alone AI tooling...

They should not have done any of this in the first place, let alone disclose it publicly in this manner.

I too did similar things when I was younger, riding high on that feeling of power, and learned the hard way that even attempting to hack something can be considered computer fraud in EU.

I was lucky to not suffer any consequences in the long run.

You can brag all you want about being an "ethical hacker", the law is probablycnot on your side - especially if you publish incriminating evidence in the form of an immature post like this.