Independent builder · Kvelde, Norway
A few prompts can become an entire connected system
I wanted to find out what happens when Codex stays with the work—not only for one answer, but across the building, testing, documentation and continued life of a system.
“A few prompts” describes the instructions I give. Behind them, the environment still has substantial work to do.
01
Bringing practical experience into the work
For more than 23 years, I have learned through hands-on technology and problem-solving. I work across software, electronics, websites, automation and infrastructure. I am interested in the whole chain: what someone needs, what the software must do, how it connects to other systems and how it will keep working.
Through Finnandre and IntentForce, I bring those parts together. Codex helps turn the direction I provide into specifications, implementations, tests, documentation and the next stage of development. The work can extend from an interface on a screen to the services and device software behind it.
Experience still matters. It helps me judge a result, ask better questions and recognize when an attractive answer needs a closer look.
02
Building continuity into the workshop
I have developed an environment in which project knowledge can carry forward. Requirements, decisions, verified results and unresolved work are recorded so that a later session can continue from an understood starting point instead of beginning again.
On 5 August 2026, this environment formally documented Codex in a resident-operator role. That date records the role and working architecture; it is not a claim of uninterrupted uptime. Within defined responsibilities, the resident role follows operational work, coordinates bounded building tasks and preserves evidence for the next action. I set the direction and retain responsibility.
This connects development with the life of a system after its first version. We can return to it, understand what changed, improve it and preserve what we learned.
03
A few instructions, many steps of work
In my own work, I can describe a substantial outcome in a few high-level prompts and use the environment to build a complete application, connect it to a website and coordinate the services behind it across controlled server environments.
The short instruction is not the implementation. Codex still has to inspect the relevant project, understand requirements, plan, write code, connect components, run tests, check the real browser or runtime, record evidence and prepare a controlled release. Live deployment remains a separate, verified step.
The amount of guidance varies with the task and the useful context that already exists. New requirements and important decisions can still need a conversation. “Few prompts” is my first-person description of the human input—not a universal promise about prompt count, time or autonomy.
04
Showing the result without exposing people
Video is part of the work too. With Codex, I develop scripts, explanations and demonstrations that turn technical results into something people can follow. I also publish selected source code and bounded evidence so a reader can distinguish a design, a prototype and a verified operational result.
My rule is simple: show the calculator, never another person’s calculation. Methods, versions, tests and limitations can often be public. Credentials, private operations and identifiable work stay protected. Powerful tools deserve transparency, privacy and human responsibility at the same time.
The wider story is what one independent builder can create when practical knowledge, persistent project context and an AI working environment reinforce each other over time.
A visible example
From an idea to something people can inspect
IntentForce App Studio is a public, fictional and interactive browser prototype. It demonstrates how an application concept, responsive interface, website publication, browser checks and a reversible WordPress release can become one documented delivery without using customer material.