Well… Why not?
Posts related to Development.
View All TagsI already made Claude Code shut the fuck up.
Then I looked at Codex.
Same job.
Different knobs.
The goal is still not:
Make the coding agent stupid enough to fit inside a fortune cookie.
The goal is:
Keep the engineering depth. Stop wasting the context window explaining the engineering depth back to me.
I use Claude Code for actual engineering work.
Not:
Write me a function.
More like:
Inspect this repository, understand the architecture, find the problem, make the smallest correct change, test it, verify it, and don't fuck up anything unrelated.
Claude is pretty good at that.
The problem is that after doing the work, coding agents have a tendency to write a fucking autobiography about it.
Two weeks ago I asked an innocent question.
"How does Jones in the Fast Lane actually work?"
Reasonable question.
Perfectly harmless.
The sort of curiosity that should result in reading a Wikipedia page and then going to bed.
Instead...
I accidentally built a game engine.
One week.
One week and a couple of days.
That's all this has been.
I keep looking at the roadmap and laughing because it feels like I've been working on this project for months.
Then I look at the commit history.
Nope.
One week.
The more I build with MCP, the more I think we're still at the beginning.
Right now people are connecting AI to GitHub.
When most people hear GitOps, they think Kubernetes.
At some point, every beginner runs into this question:
Should I use
docker run, or should I use Docker Compose?
The practical answer is simple:
docker run when you want to start one container quicklyYou can think of it like this:
docker run = one command, typed by handdocker compose = a saved recipe in a docker-compose.yml fileThis guide walks you from zero → running containers on Windows 11. No prior Docker knowledge needed.
We’ll cover:
winget