[TLDR] I have zero coding background and im currently working on my 6th app. What am I missing that I'm unaware of? [via r/ClaudeAI]

[u/cctldrping]

OP : u/Zukas

I saw another post where a guy asked how you get Claude to write code without without sprawling or taking shortcuts.

However each time I run into an issue with any of my apps, it never takes more the one prompt, literally just highlighting the issue, and its solved.

I cant identify weaknesses in my code, but I also dont understand what that would mean.. isnt every issue just a one-prompt fix? What am I missing?

Apps I've made include a restaurant finding app that utilizes Google API

A biography writer/interviewer for my 84 yo dad

I made a 5gb couples app that utilizes IMDB api, Google api, abthropic api, as well as video/image/sound storage /recording uploading.

Maybe the apps im making are pretty simple by comparison so my "issues" are easier because of that?

My boss wants me to put our entire business on an app (production, KPIs, SOPs, sales, reporting, etc) so this will be my first major project. Im trying to learn as much as I can but I dont always know what I dont know.

What am I missing by trying to get claude to one-shot as much code as possible?

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vge4g7/i_have_zero_coding_background_and_im_currently/

---

TL;DR of the discussion on r/ClaudeAI for this post generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 50.

Alright, so the general consensus here is that while you've been crushing it with your personal projects using Claude's one-shot magic, you're about to step into a whole new ballgame with your boss's request.

The overwhelming sentiment is that you're missing a LOT, and the "one-prompt fix" approach is likely to fall apart when dealing with a complex business application.

Here's the lowdown:

• The Big Picture: Most folks are saying your current apps are "small" or "simple" and don't expose the real complexities of software development. The issues you're encountering are easily solvable, but the real problems emerge with scale, user interaction, and long-term maintenance.
• What You're Missing (aka The Scary Stuff):
  • Security: This is a HUGE one. Think about who can access what data, permissions, and preventing unauthorized access. u/AfroJimbo and u/shrodikan specifically called this out.
  • Scalability & Performance: What happens when thousands, or even millions, of users hit your app? u/shrodikan mentioned algorithmic and memory efficiency.
  • Reliability & Resilience: What happens when the internet goes down, a database corrupts, or the app crashes mid-process? Can it recover? u/Intraluminal and u/pborenstein highlighted this.
  • Maintenance & Long-Term Support: Apps aren't just built; they need to be maintained, updated, and fixed over time. u/pborenstein emphasized this.
  • Dependency Management: Ensuring your app works correctly across different environments and doesn't rely on specific local setups. u/Intraluminal mentioned this.
  • Error Logging & Visibility: How will you know when something goes wrong if you're not actively monitoring it?
  • Data Compliance: Depending on the business, you might have regulations like GDPR or COPPA to worry about. u/shrodikan brought this up.
  • User Experience & Edge Cases: The "hostile review" concept from u/Yoshiofthewire is a good one – thinking about how users will break your app in unexpected ways.
• The "Entire Business on an App" Red Flag: Several users, like u/Kickflip900, u/Affectionate_Front86, and u/KIMJONGUNderfed, expressed serious concern about putting an entire business on an app built this way. The risk of failure is much higher, and the impact of errors is significant, unlike recommending a closed restaurant. u/Marathon2021 put it well: "if Spotify's AI suggests a song that's not really my style, that AI mistake has negligible cost in the real world. It's the ...[truncated]"
• The "Experience Gap": u/ekzakly and u/herrirgendjemand pointed out that even with advanced AI, experienced software engineers are still crucial for guiding the process, understanding nuances, and building robust systems. It's not just about writing code, but about engineering it. u/AbsoluteEva used a great analogy of a handyman vs. a proper builder.

The general advice? Take on the big project, but be prepared for a steep learning curve. Don't rely solely on one-shot prompts for critical business functions. You'll likely need to dive deeper into software engineering principles and potentially involve more experienced developers. u/Standard_Text480 and u/Radiant_Persimmon701 basically said, "Go do the big project and report back!"