HN user

sergioschuler

387 karma

Product leader.

Posts5
Comments35
View on HN

I spent 3 months "vibe coding" with Lovable as a non-technical PM.

It's both magical and infuriating.

My conclusion is that non-technical people CAN build simple prototypes, websites and internal tools, but would struggle to build production-grade products without any technical expertise. Think of current AI as a junior dev with outstanding syntax knowledge but terrible judgment.

Here are some things I learned in the last 3 months that seem to work well:

1. Treat it like a software development intern (write PRDs, user stories, acceptance criteria)

2. Work in tiny increments—big changes confuse the hell out of it

3. Use the "Uncle Bob" persona for cleaner architecture

4. Always refactor when prompted (but test before/after)

5. Don't be afraid to revert and start over—code is now the cheap part

Insight about the future of product: When writing code becomes cheap, many experiments that would've been discarded can now be released. We're transitioning from discovery-heavy processes to rapid iteration in production. Engineers won't vanish—they'll take on more PM responsibilities. And PMs/UXers need to learn some engineering to ship independently too.

The best advice I can give you: if you're a product person still sitting on the sidelines, what are you waiting for? Start building.

I have failed (about 50k people saw how I failed and what I learned here: http://www.sergioschuler.com/startup-lessons-learned-from-my...) and now I work for a pretty normal company, as their digital marketing head (not as impressive as it sounds, but I enjoy it).

I am building something very simple on the side (libertarian tshirts, since the idea is growing here in Brazil) and I still crave to solve problems.

Your evaluation certainly have merits and a lot of it we confirmed when speaking to clients later. Just one thing to make clear: I have 5+ years of team management/leadership development and I used a similar tool I created and evolved (in paper form) to improve a loooot of teams. So the tool works - BUT you are correct, it is a pain to apply and you probably need consultancy to get out of the team management hole if you are not a skilled manager.

I replied the same thing above: tech business are usually not about tech, they are empowered by tech. A company that uses phones to sell their products is not about "phones", they are about the product and the phone is just a tool. For me, the web was just a tool.

A lot of non-tech co-founders exist and they succeed, so certainly not absurd.

I believe this is a marketing problem (from the developers). See, I am a non-tech founder, I don't understand why X is cheaper than Y. If I perceive the same benefit, I will get the cheapest one.

(This is hypothetical, but not so much: I understand a bit of tech and even so I don't have so much clue on how to judge a developer besides what he shows me he had done).

I disagree because most "tech business" are empowered by tech, they are not ABOUT tech. My business was about team management/leadership, we just used tech as a means to an end. We could have done the same thing with consulting, but decided to get scale using the web.

It is like saying a given business which sells through the phone is about phones. Phones are just a way of doing it.

Hardly, no, one mistake that I didn't mention (because I am still processing it) is how long we took to have v1 (more than a year). This was a mix of my incompetence, too many features and also an inexperienced developer (in fact we changed developers once too).

So, yeah, a looooot of the time was put into building the product, refining it, getting bugs out of the way, testing it again, finding the same bugs...

Then there was marketing. Finding more clients, because we believed finding more people meant someone would buy the product.

PS: I was not completely full time, the developer was. In those 2 years, I have been freelancing (one needs to eat).