> At least 50% of the code you write right now should be done by AI; Vibe coding experience is non-negotiable.
That is absolutely ridiculous.. As the kids say these days, I think that company is cooked.
0 - https://www.ycombinator.com/companies/domu-technology-inc/jo...
"The safety and welfare of society and the common good, duty to our principals, and duty to each other, require that we adhere, and be seen to adhere, to the highest ethical standards of behavior."[0]
It's kind of like using autocomplete in Gmail: nobody says, “Well, Google wrote 20% of that message.”
We just quietly thank the autocomplete gods for saving us from typing “per my last email” one more time.
"Putting in 12 to 15-hour days, the engineering team has traveled to +10 cities in the past half-year for product launches."
"Solve deep product problems like how to collect more money with a voice AI agent."
Next "killer app"...an app you can send a phone call to the moment you realize it's a spammer/collector/etc. The app uses an LLM and voice synth to have the most boring and frustrating conversation ever with the caller. It should frequently ask them to repeat themselves, pretend to misunderstand common words, and for bonus points...speak in a broken accent. I'd pay $20 for that app right now.
Which is kind of funny, because if it's an automated call you don't need to even take it. Who picks up the phone from unknown numbers these days?
Shocking that no one wanted to work there.
For me at my day job, I find success with Cursor as “fancy autocomplete”. It’s aiding me when I am writing the code. The most code it’ll ever generate is to start on unit tests.
I’ve also used Cursor on the side for little personal hobby projects where I let to go wild in generating the overwhelming majority of code. I can’t say whether it’s faster or not, but it certainly helps reduce and overhead, initial blockers, ir lowering the barrier for myself to make something.
For those who are skeptical or haven’t tried it yet, ignore this article and just go give this new tool a decent try -carefully on your existing code base, and in no-stakes hobby projects - to form your own real opinion.
In the boring professional setting though, I can totally relate. The really hard questions I have to answer at work are usually not about code.
For a one-off script or a weekend project, on the other hand, even the current gen AI is a life-changing thing.
I thought vibe coding was just a meme. There are people who put vibe coding on _their resumes_??
> Solve deep product problems like how to collect more money with a voice AI agent.
> Ready to grind long hours, including weekends, to hit our ambitious goals.
Sounds like hell for an engineer.
EDIT - Both times I've joked about this ad, suddenly my account is rate limited and I can't post anything new without a "you're posting too fast" error. Maybe coincidence, but absolutely humorous.
Do they have a list of clients I can access, so I can avoid using any of their products? The first time I get a phone call from an AI bot starting with "I see you opened our email about...", I'm throwing my phone out the window.
-- edit "impossible" not "possible"
https://www.ycombinator.com/companies/domu-technology-inc/jo...
>Your onboarding will be making collection calls.
>At least 50% of the code you write right now should be done by AI
You're doing collection calls for a company that does "Automated human-like voice calls for the insurance industry".
> Putting in 12 to 15-hour days
These two don't correlate. AI is sold as saving time, so why not advertise it as a part-time job? If 50% of code is AI generated, then I expect it to be a 20 hour / week contract at 100% pay. Right?
> Your onboarding will be making collection calls.
...but there's AIs that are supposed to do that. Right?
This has got to be a troll advert or shell company. Their website doesn't list any employees or products. Half the people working for them on linkedin are deleted accounts, the rest are students or serial founders [0]
Not the first job post I've seen lately that has reverted to an aggressive tech-bro tone, either. I thought we moved on from the brogrammer shit of the last decade but it's back in full swing.
- Social Media Engagement Strategist
- Brand Evangelist
- Vision Alignment Strategist
- Chief Happiness Officer
...are also real job titles nowadays.
I see lots of arguing over point 1. but I think we can reason about 2. such that it makes the veracity of 1. irrelevant.
There is literally no skill you have to learn NOW (meaning today, this week, this year) that will ruin your career if you don't learn it. There are still very productive and well compensated people writing using editors and other tooling created in the 20th century.
Equally, your boss isn't going to come in to work tomorrow and say "you aren't already a vibe coder?! We expect you to be even though this is the first time I am mentioning it. You're FIRED!"
So if you want to learn "vibe coding", go ahead, but don't feel some great existential anxiety over it. People saying you will "fall behind" are just creating clickbait nonsense.
Vibe coding, or just letting AI take the wheel will work in some situations. It allows non coders to do things they couldn't before and that's great. Just like spreadsheets, no code tools, and integrations tools like Zapier, this will fill a bunch of gaps and push the threshold where you need to get software devs involved.
But as with all these solutions there is that threshold were the complexity, error margin gets, and scale go beyond workable and then you need to unfuck that situation and enforcing correctness. And I think this will result in plenty "oops my data is gone" types of problems.
If you know upfront that your project will get complex and/or needs to scale you might be best off skipping the vibe coding and just getting it right, but for prototypes, small internal tools, process "glue", why not.
It's not a replacement of software engineering as a whole (yet), it's just another tool in the toolbox and imo that's great. Can I use it, no.. I have tried and it just doesn't work at all for bigger more complex projects.
I do (just sayin')...
But there are actually uses for sloppy coding (whether "vibe," or some other [low|no]-code variant).
In particular, prototyping. This has always been a great application for that kind of thing. I'm old enough to remember when Flash and Director were used to prototype UI (Heh. I remember Microsoft demoing their "Longhorn" UI from Director, and trying to hide it).
Also, if your actual product is the company, then sloppy code is fine (I guess). You are basically just showing a prototype, anyway.
On the one side are the super enthusiasts who grossly oversell to try to seem innovative and "with it", hoping they can claim some land in the great new AI development world.
On the other side are the head-in-sand types who keep railing about how useless AI is, it's a stochastic parrot, only super juniors find it useful and it holds no value for the Super Novel Work that they engage in, etc. You see this sort of commentary on here all the time.
Right now it's somewhere in the middle. I find the tools extremely helpful in my day to day, and they've completely changed how I work, and the tools are growing more valuable with each passing week.
On the other hand I've run into way too many people (dozens in person, hundreds online) who are overselling AI, most with a direct financial interest as their motivation.
It's not true that the sides are at all balanced unless you create an extreme "anti-AI" side that doesn't exist.
There are even very skilled and accomplished engineers that don’t even use language servers.
Not programming, but even some legendary Disney animators still draw out their key frames by hand… on paper… in pen.
Build with what you build best with.
Personally, they help with little refactors and occasionally a quick, difficult to google, question, usually about syntax.
We are weavers looking at a loom for the first time.
[1] https://www.construct.net/en/blogs/ashleys-blog-2/reality-lo...
But vibe coding does work reasonably well for solo greenfield/demo projects. When there is no external complexity, no inferred requirements, no consequences to getting it wrong, nothing to integrate with, nobody to collaborate with ... just you and a blank editor - vibe coding works.
While it can be nice living in a little self-contained fantasy world, on existing projects you'll find absolutely none of the same conditions. And a whole slew of other engineering challenges that aren't solved by throwing generated code at it. As the value of code trends to zero, the value of those other engineering skills increases.
AI - of any kind - is about getting the computer to execute these poorly-defined heuristics, and because they're bad at it, they use a lot of energy to do so.
'Vibe coding' makes the computer execute the heuristic of generating code from requirements, and then makes the programmer execute the algorithm of ensuring that the code is correct: both human and machine are doing the thing they're bad at. It only makes sense if the only problem you have with 'move fast and break things' is that you haven't been able to move fast enough.
I'd second that. There's a huge difference between "coding," and "shipping" (not to mention "maintaining," and "supporting").
You also don't necessarily need all of that to hack together an MVP. I think a lot of people are not acknowledging that and they are negatively looking down on people embracing a new way of 'writing' code. Users don't care how you make a thing, they just want the thing to work.
Before ChatGPT made a breakthrough in LLMs, code was leverage. Now, LLMs are leverage. I think people suddenly finding that their leverage has been significantly eroded is the source of the negativity towards a "vibe coder".
So while anyone can write a book (the technology has existed since about 500 CE), few do, and there are fewer really good books. No matter the medium it's how you leverage the tool(s) you got.
I think this is a Prometheus moment, LLMs are giving coding to humanity, and it's getting adopted right now by people brave enough to try and embrace it even though 'software development' might be way outside of their comfort zone. I think it's worth cheering those people on even if they fail their way forward.
First is the degree to which your target framework, language, and domain are in-distribution for the model. You’ll get far rather in python than in Verilog, for example. You’ll get further vibecoding next.js than whatever people use for web apps in Elixir.
Second is the amount of context gathering. A greenfield project has no context - every project starts from the same zero point: an empty repo or generated scaffold. Large codebases must be loaded into working memory even for humans. This is why professional software engineering depends so heavily on getting into “flow”: https://i.imgur.com/3uyRWGJ.jpg
It’s just horses for courses.
My prediction is LLMs will get there; they’ll scale to larger and larger codebases as context windows get larger, and working out-of-distribution will happen thanks to scaling inference-time compute and agentic capability to research, read code, build understanding, and store said understanding in a scratchpad dedicated to you.
>I've also sometimes let AI do quite heavy lifting; for example, the frontend for my latest weekend project, SquadUtils, was done almost entirely by Claude. It's important to note, though, that I was always able to reason about the code and guide Claude in the correct direction if it made mistakes.
AI coding - if you know how to prompt and follow-up-prompt and review well - can greatly boost productivity for almost everyone reading this comment. This article is warning about unguided, "AI-take-the-wheel" outsourcing, not prompt-based programming in general.
Maybe in a few years something approaching true vibe coding will be much feasible, as well. We're early.
I have terrible news for the author: LLMs are quite good at the things that surround the code. The danger here isn't that someone will one-shot a working application; that's silly. The practical consequences are that you can now synthesize and rapidly iterate on technical design documentation, then transform it into architecture documents, and quickly into actual (contradiction in terms here) project-specific boilerplate.
As a senior or principal, if you don't keep up with this, you'll wash out.
https://x.com/karpathy/status/1886192184808149383
>There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard. I ask for the dumbest things like "decrease the padding on the sidebar by half" because I'm too lazy to find it. I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I'd have to really read through it for a while. Sometimes the LLMs can't fix a bug so I just work around it or ask for random changes until it goes away. It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.
Everyone seems to have missed this part.
I actually feel ambivalent about that. I think that companies should either succeed or fail on their merits (which can include the Court of Public Opinion), and, personally, I don't really like publicly slagging the work of others; even if I find it problematic.
If I challenged you to build a large piece of quality software using only AI edits, could you do it? If you don’t believe it’s possible (or productive), I would be happy to generate some codebases or products live, in exchange for $$$ ;)
"I'll use ChatGPT/Claude instead of StackOverflow" doesn't sound like Vibe Coding to me.
More like someone who can't code instructing "i want"'s and "do fix" to an AI, that sounds like Vibe Coding to me.
(maybe that's not vibe coding :)
There were five points.
So what? If we presume vibecoding makes the problem no longer the code, there's still the everything else of business. How would I compete with EventBrite? What would I even do with my clone?
Not recognizing that the limits are melting away, that what is coding is rapidly changing, and writing blog posts in defense of mechanics is increasingly silly and cope.
Here’s the tweet that literally made up vibe coding: https://x.com/karpathy/status/1886192184808149383?lang=en
One might say blindly following hype is silly and cope too.
I’ve seen no indication that relying entirely on AI can produce quality software.
It can produce prototype quality code, just as it has since gpt-3.5. Advantages of technology is never considered. Security concerns are often missed. And, from what I’ve seen, the codebases are bloated.
For your avg crud app, much of that doesn’t matter. It starts mattering when you start having real business constraints, like server budgets or data compliance. If you don’t see that, then you don’t have enough real world experience yet. That’s all.
Remember how crypto was going to change everything? Or the metaverse?
We live in a period of extreme technological hype backed by insane company valuations.
Don’t get too fooled by market.
These tools are useful. They are here to stay. And they do not replace the entire field of programming nor the work that programmers do.
But as soon as projects balloon in complexity, the less "vibe" the AI gets in my experience.
