For vibe coding, what matters more: time spent, complexity, or the strength of the idea?

I have been thinking about how people judge vibe-coded projects.

Some people seem to measure the value by time spent:

“Did you build this in one night, one weekend, or over several months?”

Others measure it by complexity:

“How many features, integrations, agents, APIs, databases, auth flows, deployments, etc. does it have?”

But I am starting to think the real differentiator may be the idea itself.

A simple app with a strong idea can be more valuable than a complex app that nobody needs. At the same time, complexity still matters when the product has to scale, support real users, handle edge cases, and survive production.

So maybe the question is:

Is vibe coding impressive because it saves time?
Because it lets non-traditional builders handle complex systems?

Or because it allows people to test more ideas faster?

My current view is that the idea comes first, time spent proves speed, and complexity proves execution ability.

But I am curious how others see it.

When you look at a vibe-coded project, what impresses you most?

Happy coding!

reddit.com
u/startup-1 — 7 days ago
▲ 1 r/u_startup-1+1 crossposts

Agentic AI and Skills: I think this is where things are going

Lately, I have been thinking about agentic AI in general and skills in particular.

To me, agentic AI is not just a chatbot giving answers. It is more like an AI system that can take a goal, break it into steps, use tools, check the result, and keep moving forward.

But the part I find interesting is skills.

I don’t see skills as just prompts. I see them more like reusable playbooks. Almost like a way to teach the AI how you want certain work done.

For example, instead of explaining the same deployment process over and over again, you could have a deployment skill. Instead of explaining your code review process every time, you could have a code review skill. Same for testing, documentation, database setup, security checks, or app generation.

So the agent becomes the one deciding what needs to happen, and the skills become the repeatable ways of doing the work.

That feels like a big shift to me.

We are moving from:

“AI, answer this question”

to:

“AI, use the right process and get this done.”

I think this is especially important for software development, because a lot of value is not only in generating code, but in repeating the right process consistently: build, test, deploy, validate, improve.

Are skills just better prompts, or are they becoming something closer to reusable operating procedures for AI agents?

I am genuinely curious what everyone thinks about the subject. Let’s explore together.

Additionally, are you using tools like OpenClaw or Hermes?

reddit.com
u/startup-1 — 8 days ago