Codex as a Coding Partner, Not a Magic Button
A practical way to use Codex for focused implementation work without handing it a vague pile of wishes.
Now
What I am paying attention to now.
Updated June 2026. Current focus: VPS plan pages, affiliate link hygiene, and vibe coding workflows.
Current focus
Maintaining VPS plan pages
Keeping BandwagonHost and ION pages readable, current, and linked through the configured affiliate URLs.
AI as daily infrastructure
Tracking how AI changes research, editing, coding, and the way small sites should organize knowledge.
Small static pages
Keeping the site static, portable, and easy to version instead of depending on a heavy CMS.
Better defaults for writing
Finding formats for essays, notes, project logs, and resource pages that are easy to keep using.
Site housekeeping
The next practical steps before this becomes the permanent home page.
Replace temporary contact details
Domain, email, and social URLs should be set before the site is published publicly.
Refresh provider data
Check prices and availability on a regular cadence so deal pages remain trustworthy.
Expand vibe coding notes
Add compact notes when Codex, Claude Code, or GPT workflows produce reusable lessons.
Recently published
View all posts ->
Claude Code and the Vibe Coding Loop
Vibe coding becomes useful when the loop is tight: describe, inspect, edit, run, and correct.
GPT Prompts That Survive Contact With Code
Better coding prompts are small, inspectable, and tied to verification rather than vibes alone.