Airbnb, Uber and Amazon were already making everything worse. We're past the "bleak threshold" for over 10 years now.
Airbnb is inflating the real-estate bubble everywhere. Apartment building now are mass produced, tiny, and expensive, targeting investors who are only interested in Airbnb.
Uber/ifood and other transport/delivery apps are just working around labor laws, undoing centuries of progress towards worker rights and approaching slavery-like situations.
Amazon is just another monopoly, not sure why you put it beside the others, but it's one of the companies lobbying to make the world a worse place.
Then came crypto"currency", which started the "age of anything goes", where tons of money are thrown in the trashbin for the next speculative pseudo-tech bubble.
AI is just the bubble that came after crypto, little practical utility with lots of hype from billionaires who threw money at it.
As far as Uber, was it better when there was both a medallion system monopoly in cities like New York and less access to cabs? Where people had to rent overpriced medallions and couldn’t make any money
Or sometimes depending on what you looked like, where you were going or where you were coming from, you couldn’t get a cab at all.
I have used Uber all over the US and in a few other countries. Most Uber drivers I talk to like the flexibility.
Half the “benefits” that people bemoan that Uber drivers don’t get shouldn’t be the responsibility of any private employer. For instance health care shouldn’t be tied to your employee anyway.
It's entirely possible to have specifications somewhere between "vague hand-wavy descriptions" and source code. But it's really not my job to defend AI against all the people who want it to be completely useless, seem to need it to be so, really. I just use it, it works a lot of the time, doesn't work other times, and that's that. Results carry more weight than opinions.
It's not a problem. It's in fact the core trait of vibe-codig. The primary work a developer does in vibe coding tasks is providing the necessary and sufficient context. Hence the inception of the term "context engineering". A vibe coder basically lays out requirements and constraints that drives LLMs to write code. That's the bulk of their task: they shift away from writing the low-level "how" to instead write down the high-level "what".
> The whole point is having the LLM figure out what you want from vague hand-wavy descriptions instead of precise specification.
No. The prompts are as elaborate as you want it to be. I, for example, use prompt files with the project's ubiquitous language and requirements, not to mention test suites used for acceptance tests. You can half-ass your code as much as you can half-ass your prompts.
HN has been happily very rude about anything AI related the last year, even in cases here where it's hardly relevant or appropriate. It's depressing and I used to expect a lot better.
It takes more work to build a janky site than just no frills html/css unless you vibecoded it or copy and pasted a crappy template.
I think we should be allowed to push back against sloppy work (which is different from beginner work) instead of ingratiating it with a smile.
We have the rest of you to baby them over adding the worst css transitions I’ve ever seen, something they deliberately swerved into.
They are accused of vibe coding it only through charity because it’s hard to imagine they did it themselves and went “yup that’s exactly what I wanted after spending that extra time adding it.” Whether it’s vibe coded or not isn’t really the point.
Grading on perceived effort is not a rubric destined to last. You cannot detect sloppy work from beginner work without context, and in any case a lot of beginner work these days (and to some degree for the rest of time!) is going to include LLMs or AI.
Is HN only for advertising startups these days? If this post had nothing to do with AI maybe the response would have included some real genuine criticism and feedback, with the assumption baked-in that a beginner was being coached.
To your last point, then downvote it if it's bad. You're right and I agree precisely that it being vibe-coded wasn't the point - but it was brought up regardless. If the result is bad the feedback is still the same. If the "problem" is just that they used tools you don't agree with using, then that's not feedback on the result.
This isn't just reverse engineering, it's a decompiled source from the original binary.
reply