I sometimes wonder about the similarities between this paradigm switch (coding -> vibe coding) and when the industry switched from writing assembler to using high-level languages. I both cases we switched from having to specify every posibble implementation detail to focusing more on higher level concepts and letting the machine work out the rest. Maybe in the future instead of sharing source code, we will share prompts that we used to create a program. Similarly how different compilers produce different assembly now, "compiling" prompts with different agent/model would give different results. Maybe in the future an analog for "optimizing compiler" would emerge for agents, which would turn the (working) slop into something more clean.

xcancel? What is the purpose or benefit of providing a free mirror to x? Doesn't it end up sparing the x servers and causing their costs to decrease?

tl;dr - All this AI stuff is just Universal Paperclips[1]

I see a lot of comments about folks being worried about going soft, getting brain rot, or losing the fun part of coding.

As far as I'm concerned this is a bigger (albeit kinda flakey) self-driving tractor. Yeah I'd be bored if I just stuck to my one little cabbage patch I'd been tilling by hand. But my new cabbage patch is now a megafarm. Subjectively, same level of effort.

[1]: https://en.wikipedia.org/wiki/Universal_Paperclips

> LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building

as the former, i've never felt _more ahead_ than now due to all of the latter succumbing to the llm hype

Basically mirrors my experience.

Interestingly, when you point out this ...

> IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side.

... here on HN [0] you get a bunch of people telling you to get with the times, grandpa.

Really makes me wonder: Who are these people and why are they doing that?

[0] https://news.ycombinator.com/item?id=46745039

> Slopacolypse Really… REALLY not looking forward to getting this word spammed at me the next 6-12 months… even less so seeing the actual manifestation.

> TLDR This should be at the start?

I actually have been thinking of trying out ClaudeCode/OpenCode over this past week… can anyone provide experience, tips, tricks, ref docs?

My normal workflow is using Free-tier ChatGPT to help me interrogate or plan my solution/ approach or to understand some docs/syntax/best practice of which I’m not familiar. then doing the implementation myself.

> The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking.

If current LLMs are ever deployed in systems harboring the big red button, they WILL most definitely somehow press that button.

Next milestone: solving authoritarian LLM dependencies. We can’t always get trapped in local minima. Or is that actually okay?

I don't know about you guys but most of the time it's spitting nonsense models in sqlalchemy and I have to constantly correct it to the point where I am back at writing the code myself. The bugs are just astonishing and I lose control of the codebase after some time to the point where reviewing the whole thing just takes a lot of time.

On the contrary if it was for a job in a public sector I would just let the LLM spit out some output and play stupid, since salary is very low.

> do generalists outperform specialists?

Depends what we mean by specialist. If it frontend vs backend then maybe. If it general dev vs some specialist scientific programmer or other field where a generalist won’t have a clue then this seems like a recipe for disaster (literal disasters included).