I'm starting this topic in case there are like minded people on this forum who would like to share experiences.
I've learned a lot. And have produced stuff I like. I NEVER look at the actual code. I do write "guides" to myself which I'd be pleased to share.
I provided the ideas and direction. I own the scope, taste, purpose, acceptable risk, user experience, whether the app does the right thing and whether the project is becoming too complicated. Codex acts like a wise team of assistants with skills in all the other parts. Any time I don't know what to do, I discuss it with Codex or ChatGPT (or both).
Here are my most resource-intensive projects. Mostly native apps on a Mac, some HTML apps.
- TeslaCam Investigator - a tool to display and analyze Tesla video and telemetry
- WordGridGame - a word game I came up with (Mac app and web app)
- Star Trek Game - a reimagining of a 1978 Apple 2 game
- Assembly Code stuff - actually experiments in code optimization using the Mandelbrot set as a CPU-challenging example
- Root - housekeeping reports and cleanup (mostly web apps)
- Garmin Analyses - analysis and display of cycling computer data from over a decade of rides
- Seagrass 2 - an animation experiment with fish and ells etc (as a web page)
- Solar analysis - analysis of solar/battery/EV data
- MacDown 3000 Personal - a rework of a Markdown editor from GitHub adding a "zoom" capability
- GT7 Tuning Tools - a blend of GT7 tutor, reference and tuner (as a web page)