← All articles

Felix Tay ·

10 months of progress in 3 days

I finally took a serious swing at vibe coding. 

I’ve had chances in the past, but they were often lower in priority. 

But circumstances finally forced my hand and I have to say…I’m so glad it did!

Because it got me more progress in the past 3 days than 10 months of working with developers combined.

Bloody hell - why didn’t I get started with this sooner?

For the past 10 months, I’ve been working with human developers to build NEO. 

It was excruciatingly slow.

The cycle was always the same: 

  • I would send a feature request

  • Wait 12-24 hours for their reply

  • Exchange clarifying questions across timezones

  • Get a late delivery full of bugs

  • Repeat

Each small change took us anywhere from days to weeks.

Then last Friday, my latest hire - an addition because the old dev quit - handed the usual overdue delivery riddled with bugs. 

And informed me that he’s gonna be away until 8th Jan.

I couldn’t just sit around doing nothing, so I decided that I’m gonna give Replit a try.

That was three days ago.

God help me, I couldn’t stop since.

I barely got any sleep because I was too excited working to go to bed, and too excited to keep sleeping.

So I woke up early, without any alarm, and just kept vibe coding away.

We’ve already fixed almost all the bugs that were created since I started working with the first dev, 10 months ago!

There were a ton of small little details I’ve been putting up with, tolerating because I didn’t want to “overload” my developers with too many tasks.

In fact, it’s more progress in 3 days than we had in 10 months.

When working with AI, the experience was, I can honestly say, better than working with a human.

I would describe what I want roughly.

It tells me what it thinks I want.

Once I verified it, the AI built it in only a few minutes. 

There’s been a few tasks here and there that took 30 minutes to an hour, but most of the time it takes less than 10 minutes. 

It would pass me the completed work and I would test it.

If it doesn’t feel right, I tell it what feels off, and it would even give suggestions on design best practices.

(!!!)

This way, we’ve been doing 30-50 iterations per day instead of per week.

I always thought I needed ‘technical knowledge’ to vibe code well. 

Turns out, I just need better communication.

And I need fast feedback loops. 

One where I could test something in minutes instead of days, so that I discover what the product actually needed. 

It’s really funny, the parallel between my experience in this new domain with what I’ve observed watching people sell their offers online. 

New ACF members (and clients) often think clarity comes from better planning or more knowledge.

But the truth is that the speed of iteration itself is the most reliable action for clarity.

You do not need perfect clarity on your offer and positioning before testing with real prospects. 

You just need speed of iteration.

You need to make many offers.

Get the data. Iterate. Repeat.

You discover what resonates by testing fast with real people, not by planning longer in isolation.

Speaking of, ACF membership is open for the next 48 hours. 

I give you a proven 16 weeks implementation plan to build your own AI Client Factory. 

Powered by 52 AI processes that solves most of your client acquisition woes.

By the 6th week you’d have installed all the core components in your business, which lets you iterate for the rest of the 16 weeks.

Check it out here: [Archived link retired.] 

FELIX


More from the NLC blog →