← Back to context

Comment by Krei-se

19 hours ago

I work on my project for 2 years now and using an LLM always came back to bite me. Learning how something works is needed, slow and painful - but pain is gain.

If this works for you - awesome. Until it doesn't.

As always there is 0 code or link. All talk.

And when do you expect my approach will stop to work? The core features are complete and the codebase is already sizable.

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.

  • Then you may as well said you've solved P=NP.

    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".

    • I am here to discuss my opinions on AI for software development because it's interesting. Not because I am selling a book or to prove anything to you.

      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.

      8 replies →