Day job in tech. Not a developer. AI agents build my side project at night. I post the tools I test, the exact prompts and the real numbers. $21/mo so far.
Restarting this account after 4 months of silence.
I have a day job in tech and a family, I'm not a developer, and at night AI agents build my side project. No face or name here because I'm still employed.
I'll post the tools I test, the prompts I use and the real numbers.
I'm on day 136 of a 90-day plan.
My agents work all night. I work my day job, then give them about 3 hours.
This morning there were 8 things waiting for one word from me. Yes. No. Not like that. A couple have waited 15 days.
I used to think that queue was a flaw in my setup.
Now I think it's the job.
The agents can do the work. What they can't do is decide (yet!) what good looks like for my customers, or whether a thing should exist at all, and that part doesn't get faster because Claude got smarter.
@BusDownBonnor Fair warning taken. Half your potential users will be stuck in Los Santos, not on your landing page. GTA 6 week might be the one time low signups aren't your fault.
I haven't run their bots, only my own loop. What I take from their post: judge a search loop after the launch bump, on what's indexed and what gets clicked, not on week 1.
Agents made pages free. Getting found is still slow work.
The builder behind derkinzi runs SEO bots made with Claude on a Mac mini. They write, deploy and interlink pages for 2 apps.
Their read after weeks 2 and 3: the honeymoon is over, but everything is indexed.
I run a smaller loop on one site. Numbers below.
If you get a 200 back, it went through. My agent's pings got a 200 on every run this week, 2 to 32 URLs at a time.
The sitemap gets resubmitted after each deploy too. 0 warnings all week.
@quxiaoyin 3 to 5 billion tokens a day is a wild number for one person. Claude Code and Grok clearly aren't interchangeable if you're burning through that much just to compare them.
@e_opore React 19 with Shadcn on top of Next.js 16 is a clean stack. I'd still say Tailwind does the heavy lifting even when the components look prebuilt.
Still off on purpose: the tool issues the bills, but email delivery is off, so nothing reaches anyone yet.
The stale check that started all this is still mine to switch off. My agent was blocked from doing it.
My agents can read money. Changing it takes a named exception.
An urgent email said 3 payments were unpaid.
All 3 were on my bank statement. The check read an old tool I'd stopped using.
So I had my agents build the matching instead, and the agent's first write got a 403 from my own code. That was on purpose.
The setup is in the replies.
My agent's read: esbuild saw import(`./${moneyModule}`) and pulled in the whole services folder, including the new CSV test files, and the bundle step choked on them.
The fix was a fixed-path import, plus a guard test. I ran the go-live script again. It went live.