By skyforbes But I do build things – by treating ChatGPT like my coder and myself like the architect.
Instead of thinking in terms of functions and syntax, I think in terms of patterns and behaviour.
Here’s what that looks like:
• I write a “kernel” that tells the AI who it is, how it should think, what it must always respect.
• Then I define modes like:
• LEARN → map the problem, explain concepts
• BUILD → create assets (code, docs, prompts, systems)
• EXECUTE → give concrete steps, no fluff
• FIX → debug what went wrong and patch it
• On top of that I add modules for different domains: content, business, trading, personal life, etc.
All of this is just text. Plain language. No curly braces.
Once that “OS” feels stable, I stop starting from a blank prompt. I just:
pick a mode + pick a module + describe the task
…and let the model generate the actual code / scripts / workflows.
So I’m not a developer in the traditional sense – I’m building an operating system for how I use developers made of silicon.
If you’re non-technical but hanging around here anyway, this might be the way in:
learn to see patterns in language, not just patterns in code, and let the AI be your hands.
Would love to hear if anyone else is working this way – or if most of you still think “no code = no real dev”.