This is pretty interesting.

A couple of days ago, Rocket.new announced something new called “Vibe Solutioning,” claiming it makes their previous “Vibe Coding” seem incomplete. Honestly, the name alone sounds a bit mystical, but when you think about it, it hints at a major trend in AI-powered programming tools.

What’s Vibe Coding?
In short, it’s coding by “feel.” The AI generates code snippets, and you tweak and adjust them as you go, almost like feeling your way through a programming “vibe.” It was all the rage last year, with many tools jumping on the bandwagon. But after prolonged use, a problem emerged—it only handles code output, ignoring the steps before and after. It’s like handing you a great screwdriver but not telling you which screw to turn.

What’s Vibe Solutioning Trying to Solve?
According to Rocket.new, the goal now is to cover the entire development lifecycle. From strategic planning and product deployment to “continuous memory” (presumably meaning the AI remembers project context), everything is automated. This isn’t just about writing code anymore; it’s more like a Frankenstein’s monster of AI product manager + architect + DevOps.

Why Does This Matter?
First, it shows AI programming tools are starting to “steal jobs.” Before, they just saved programmers time; now, they’re restructuring workflows. In the future, startups might genuinely get by with AI plus one or two technical leads handling the entire process. How low can labor costs go? It’s hard to imagine.

Second, software engineering education might need an overhaul. If AI can handle requirements analysis and deployment, how relevant are the waterfall or agile methodologies taught in schools? Are we just training students to work for AI? (Though, let’s be honest, that might already be the reality.)

My Skepticism

  1. Buzzword or Real Need? “Vibe” is too abstract—it sounds like marketing fluff. How is this better than existing tools? We’ll need real-world examples.
  2. Over-Automation Risks: Handing everything to AI could backfire. If it misinterprets the requirements from the start, the whole project might go off the rails from line one.
  3. Will Developers Let Go? Programmers hate two things: others touching their code and not being allowed to touch others’ code. Now they can’t even touch the architecture?

Final Thoughts
The direction is undoubtedly right. AI-assisted development will inevitably evolve from “writing code” to “building products,” but right now, it’s likely just stitching together existing tools. For a truly useful solution, AI’s “context amnesia” needs fixing—it can’t forget the original problem by the time deployment rolls around.

(By the way, the original article is here. I’ll bet five bucks the comments will feature someone arguing, “This thing is worse than Vim + command line.”)