I believe it's ultimately a tug of war between what the business wants (more features, faster, etc) and the engineers want (maintainability, documentation, scalable patterns etc). Engineers rarely win this tug of war. At times it feels like watching a car crash in slow motion. I don't think this trend will meaningfully slow or change, until businesses interests are hit. That may take a while for this cruft to start causing pain. Even then, you may just throw money at the problem, or just live with it. Will companies go bankrupt because of vibe coding? I don't think so, and that's why ai coding is here to stay. My 2 cents

I believe the economic machine gives an edge to people who do more right things than wrong. Bob does things wrong, but given a 10x amount of output, the balance of right output vs wrong output may still be favored upon by the economy. A speculation, to be sure, we'll have to see how it pans out.

I think this will become the prevailing sentiment when the dust settles.

AI writing feels like putting a michelin course into a blender and drinking it

This is what struck me as well. I got weird undertones of 'Now you don't even need to have real memories! Just fabricate them.' They even prominently showcase edits of placing you with another person, further deepening disingenuous or parasocial relationships

>then tell it to give you the top 10 things wrong with the code, then tell it to fix the five of them that are valid and important.

I would be cautious of this. I've tried this multiple times and often it produces very subtle bugs. Sometimes the code is not bad enough to have 5 defects with it, but it will comply, and change things that don't need to. You will find out in prod at some point.

To be clear, I'm instructing it to generate a list of issues for me. I then decide if anything on that list is worth fixing (or is an issue at all, etc.)

Crappy spreadsheet is just the codification of business processes. Those are inherently messy and there's lots of assumptions, lots of edge cases. That's why spreadsheets tend towards crappy on a long enough timeline. It's a fundamentally messy problem.

Spreadsheets are an abstraction over a messy reality, lossy. They were already generalizing reality.

Now we generalize the generalization. It is this lossy reality that people are worried about with AI in HN.

>but couldn't care less if it disappeared tomorrow.

Wonder how true that is. Some things incorporate in your life so subtly that you only become aware of them when totally switched off.

What were the clues, in hindsight?

I wonder if someone can get scent of 'want you to fail' early, so one can play their cards a bit differently armed with this knowledge.