Christian

Six weeks in, and I still haven't touched a desktop. Everything architecture decisions, debugging, database migrations, the whole thing happens through a phone screen and an AI agent doing the actual typing.

What's strange is how different the failure modes are from what I expected. I thought the hard part would be not knowing how to code. It wasn't. The hard part was learning to think in prompts instead of logic how to describe a bug precisely enough that the agent fixes the real problem instead of patching the symptom, three times, in three different wrong places.

I keep wondering if this is a preview of something bigger, or just a novelty that works because I happen to have a lot of patience and a phone that doesn't die. Curious what others here think: for the people who've built with AI agents has it changed how you think about programming as a skill, or does it just feel like outsourcing typing?

And for anyone who hasn't tried building this way yet what's stopped you? Time, trust, or just never having a reason to?

I've spent the last few weeks building an app called Actually Done basically a home for all the scattered life-admin stuff (documents, passwords, medical info, reminders, bills) that normally lives across six apps and a shoebox.

The part I keep thinking about: I built the whole thing on my Android phone, using Replit's AI agent, with no formal coding background. No laptop, no IDE just a phone and a lot of back-and-forth with an AI pair programmer. It's been a strange way to learn software development in real time the agent writes the code, I do the actual QA (I don't trust "it's fixed" without proof), and I make the product calls.

I'm veteran-owned, so a lot of what I'm building comes from wanting things to just be organized and findable when it actually matters not just neat.

Launching on Product Hunt in a few days. Before that, I'm curious about this community:

I'm a veteran and solo founder with no formal coding background. Spent the last few weeks directing Replit's AI agent (with Claude as a strategic/QA partner) to build a real production app, entirely from my phone.

The part that surprised me: the "vibe" is the easy 20%. The other 80% was the same discipline any build needs catching bugs by hand (missing auto-capitalization, a timezone off-by-one, a file upload limit rejecting real phone photos), refusing to accept "it's fixed" without proof, running full walkthroughs section by section, chasing root causes instead of patching symptoms.

That's made me rethink what "vibe coding" even means. It's not skipping the engineering discipline it's relocating it. Instead of writing code, you're writing precise instructions, reviewing output critically, and doing QA like a hawk. If anything it demands more discipline, not less, because you can't rely on catching mistakes by reading your own code you have to actually test everything.

For others who've directed an AI agent instead of hand-coding: has your experience matched that, or did you find a different bottleneck? What ended up being the hardest part for you the instructing, the reviewing, or something else entirely?