32 lines
1.8 KiB
Markdown
32 lines
1.8 KiB
Markdown
# AI assistance
|
|
|
|
I am an AI-assisted systems developer. I use automation to scale how much I can
|
|
build, but I still own the architecture, the constraints, the integration and
|
|
the final result.
|
|
|
|
For Nereus, the main assistants were Codex CLI and Claude Code CLI, using
|
|
GPT-5.6 Sol and Sonnet 5.0. Some application code, infrastructure configuration
|
|
and documentation were drafted or implemented by those tools. Other parts were
|
|
written by me. The agents handled a lot of the repetitive implementation work;
|
|
I decided how the system should fit together, reviewed the changes and ran them
|
|
against the real environment.
|
|
|
|
The debugging process was also mixed. I investigated some failures manually
|
|
through logs, metrics, packet paths and command-line tools. Some research came
|
|
from Google and official documentation. Other problems were handled through AI
|
|
sessions or longer Codex loops that inspected the current failure, changed one
|
|
thing, reran the check and continued until the system reached the expected
|
|
state.
|
|
|
|
Most of the difficult failures were not application-code problems. They were
|
|
networking and integration details: firewalld blocking VXLAN, permissions on
|
|
pod log files, missing RBAC verbs, incorrect image tags, stale buoy IDs after a
|
|
database reset and Prometheus windows that still contained earlier errors.
|
|
Those are the parts I debugged on the actual hosts and cluster. An AI-generated
|
|
configuration was never treated as working just because it looked correct.
|
|
|
|
I am responsible for the final project. AI helped type, research and iterate;
|
|
the architecture, acceptance criteria, hardware debugging, system integration
|
|
and final review remained mine. The checks that actually passed are recorded in
|
|
`docs/evidence.md`, and anything still dependent on external hardware or
|
|
credentials is marked honestly in `docs/roadmap.md`.
|