“Have you tried this out yet?” Corvallis asked.

“Not against a real subject,” Pluto said. “I invented a fictitious subject and deployed some APEs against it, just to see how it worked in the wild. The fictitious subject has already attracted thousands of death threats,” he added with a note of pride.

“You mean, from people who saw the defamatory posts seeded by the APEs and got really mad at this person who doesn’t even exist.”

Here, some may notice an obvious behavior for infant and arrogant people who chose not to learn, gain knowledge, focus on accountable actual research, develop their mind and self-confidence, but just invent a harassing and namecalling term to at least anyhow feel themselves worthy.

I believe that one day, the author known as `romulo@rsaksida.com`, set in the footer there, will realize their infant and indifferent attitude, that every single psychologists instantly notices.

Thank you! I'll associate that term with you now, romulo. You do you.

Related:

- https://web.archive.org/web/20241109033457/https://slopwatch... (Using AI Generated Code Will Make You a Bad Programmer) by Rudis Muiznieks

- https://lemmy.world/post/43725501 (Ideon - I'm building a self-hosted project cockpit on an infinite canvas...)

I really like to understand the practice of software engineering by analogy to research mathematics (like, no one ever asks mathematicians to estimate how long it will take to prove something…).

Something I think software engineers can take from math right now: years of everyone’s math education is spent doing things that computers have always been able to do trivially—arithmetic, solving simple equations, writing proofs that would just be `simp` in Lean—and no one wrings their hands over it. It’s an accepted part of the learning process.

It's so great to be alive in this time of of dehumanizing AI.

The reason we have programming languages is the same reason we have musical notation or math notation. It is a far more concise and precise way of communicating than using natural languages.

We could write music using natural language, but no one does because a single page of music would require dozens of pages of natural language to describe the same thing.

I know it's not what the thought piece is about, but it's equally accurate to say engineers are "aping in" on AI coding without doing any research. Very much the same vibe, my anti-AI friends suddenly flipped their tune to shill slopped together apps.

I expect it to go about as well as it did in crypto.

I also have two levels "beneath" vibe coding:

- Power Coding: Like power armor, you describe chunks of code in English and it's built. Here you outsource syntax and stdlib, but remain in control of architecture and data flow.

- Backseat Coding: Like vibe coding but you keep peeking at the code and complaining ;)

- Vibe Coding: Total yolo mode. What's a code?

You don't talk about all the assembly high level languages make, or at least it's no longer how people view things. We don't say "look at this assembly I compiled." Instead the entire concept fades to the back.

It's an interesting question: Will coding turn out to be more like landscaping, where (referring to the practice specifically of cutting grass) no one uses hand tools (to a first approximation)? Or it will it be more like woodworking, where everyone at least knows where a Stanley hand plane is in their work shop?