I was never trained to code, but I picked up a lot when trying to reverse-engineer a script I paid a guy to write for me a few years ago and with LLM assistance my ability to adapt code expanded dramatically. Now that the LLMs can write code reliably, it's been another exponential expansion. So when I converse with GPT about something I want to build, it's with an understanding of how code works, capabilities, limitations, lingo, etc. As for the actual writing, there's almost no point anymore. Claude or Codex will do it better, faster, and more accurately. That said- experience helps a lot. You start to learn the ongoing limitations and account for them when planning. For example, say you build a window that has a function that generates some text for you. You assume that there will be a button somewhere to save, close, clear, whatever. Or that if you click off that window and back on, your text will still be there. Then you test it out and see you needed to specify things like that. With time you start to integrate gotcha items into your planning.
So my process is to have a discussion with GPT about what I want to build, go back and forth for a while. Make a phased plan. Then go to Codex and have it formalize the plan and make it relevant to my existing codebase (if it exists). Then rewrite the plan. Then I might have Claude implement it, and have Codex check the work. That process works incredibly well if you really want to get it done. I'm actually teaching this to my kids now and even got one of them their own subscription to Claude Code. She's working on an app that helps you write a book.
Now... EHR integration. That comes later. It will be easier to integrate once the product is fully grown. Athena will want to see a fully fleshed out app before I can plug into their API. Right now you can cut and paste context into a box, or use the customized context extraction system (add your files, it will extract facts, store them, then you can call up relevant context anytime you write a note at the press of a button). Then you scribe-- that's the point where the procedure auth loop engages. You tell it what procedure you need an audit defense for, then it outputs your progress to a separate window you can monitor while the visit is ongoing. Haven't tested it out yet, but this should be working soon.
This is an enormous amount of work, and I had to go through 3 simpler versions of my app to arrive at the big boy I'm building now. Start with small projects, learn, and then build bigger ones.