took me a few reads but this is indeed correct (lol)

I just finished an implementation of CI across three codebases totalling >50k lines and I can confirm a lot of the author's pain points, especially around logging and YAML variables.

Commit with one character YAML difference? Check.

Commit with 2-3 YAML lines just to add the right logging? Check.

Wait 5+ minutes for a YAML diff to propagate through our test pipeline for the nth time today? .. sigh .. check

BUT, after ironing all these things out (and running our own beefy self-hosted runner which is triggered to wake up when there's a test process to snack on), it's .. uh.. not so bad? For now?

We use them on our cats and have found the trouble-maker cat 3 times out of 3 when needed (in an urban apartment area; most recently the cat was scared by a noise which may have kept her hidden out all night in the cold, unless we had found her/shooed her back to the house)

By your reasoning, Putin invading the US and kidnapping President Trump for his crimes is equally valid

I would personally pay $2x market price for a Phone, Computer, Tablet that guaranteed privacy (via whatever technical means necessary) for all my interactions with the internet.

Is that so much to ask?

Could the next "Apple" produce such hardware/software stack to black box this for the consumer -- simply buy "Pineapple" products and guarantee this stuff can't touch you (user obsfuciation for all external platforms could be a hard technical challenge, I know - hence the big value if delivered)

I can't help myself and surely someone else has already done the same. But the query

  obj.friends.filter(x=>{ return x.city=='New York'})
  .sort((a, b) => a.age - b.age)
  .map(item => ({ name: item.name, age: item.age }));

does exactly the same without any plugin.

am I missing something?

The verbosity.

To your point abstractions often multiply and then hide the complexity, and create a facade of simplicity.

they'll take apart this criminal empire brick by brick

no stone will be left unturned

As long as nothing blocks the investigation!

I doubt we see many knee jerk mistakes on this one...

i think we have stoned this analogy to death now

That is also not enough. An agent could build an application that functions, but you also need to have a well-designed underlying architecture if you want the application to be extensible and maintainable - something the original dreamer may not even be capable of - so perhaps a shared extended dream share with a Sr. architect is also needed. Oh wait .. I guess we're back to square 1 again? lol

I joined a company with 20k lines of Next/React generated in 1 month. I spent over a week rewriting many parts of the application (mostly the data model and duplicated/conflicting functionality).

At first I was frustrated but my boss said it was actually a perfect sequence, since that "crappy code" did generate a working demo that our future customers loved, which gave us the validation to re-write. And I agree!

LLMs are just another tool in the chest; a curious, lighting fast jr developer with an IQ of 85 who can't learn and needs a memory wipe whenever they make a design mistake.

When I use it knowing its constraints it's a great tool! But yeah if used wrong you are going to make a mess, just like any powerful tool

Here's a question for you then. Imagine your own future years and decades spent doing nothing but rewriting crappy code like that. Not as a one-off thing, but as a job description. Does that sound enticing? Do you think you'd able to avoid burnout in the long run?