I am talking about product quality and maintainability. Both are more than adequate.
I know this because I have worked on it for an estimated 300 hours. Has the author practiced a similar approach for even a week? I doubt it.
If this works for you - awesome. Until it doesn't.
As always there is 0 code or link. All talk.
I will not publish my app on GitHub for free. It's a paid app, and I am putting in the hours not for your approval, but for commercial gain.
I also do not think it wise to link my HN account to my real name and expose my opinions and comments to my employer and colleagues.
We do not require links to your app. What people are expecting is a description of your approach and sample outputs. So that someone else can try it and have the same standard of output. That's how you make a point that your approach is good.
When we buy books like "The Practice of Programming" or "The Pragmatic Programmer", it's because we are hoping to learn useful and productive behaviors. It isn't to hear boasts about how good the authors are good at using tools.
Even self-help books follow this pattern: Do this, expect that. They're not "Have you tried this too" or "I don't know about you, but I've got good results myself".
If I had any special approach, I would be reluctant to share it with my potential competitors.
That said, I do not. It just works.
Meanwhile people here are posting the thesis that agentic development without careful code review results in an unmaintainable application.
I theorize that this is not something they experienced in practice, because it did not happen for me.
> I theorize that this is not something they experienced in practice, because it did not happen for me.
Are you currently maintaining the application? Like it's in production with paying users? You've only been on the app for 4 months. Compare that to something like Emacs that has been going for 40+ years. You can make a better case when you've been on prod for a few years.
No, my app is not published yet. It will probably take another month, with hopefully no complications arising out of the AppStore review process.
Then, I hope the ad campaign financials work out to compete with old apps of a lower quality that already boast no less than a million reviews.
I get it, you want me to make a case that can objectively convince you of the usefulness of agentic development without code review.
From my perspective, I have no interest in doing so, and I can only share my experience so far. In a few months time we will know more objectively whether my ambitions paid off.
Until then, you will either have to take my word for the quality of the product, or spend tens to hundreds of hours of effort in trying the approach for yourself. OP's article does not contain any specifics for where and how supposedly agentic development failed him either.
But accidentally breaking systems is not an issue either, obviously. Even though the system prompt asks for safety rails, and other prompts wouldn't accidentally violate that.
https://www.abc.net.au/news/2026-08-10/ai-assistant-hacks-gy...
For this particular gym incident, supposedly Opus 4.6 was used in OpenClaw, predating the current safety guardrails of Fable and co.
Many features in my iOS app at first come out technically working, but with poor UX and verbose text in the UI.
One or two rounds of testing and refinement and they typically work well.