About that 'no AI'...
A correction to my own post: the culler does contain machine learning, and the distinction I drew between ML and AI does not survive scrutiny.
Tags
44 pages
AI
House rules
Running three different coding agents against one repository, and the house rules that stopped them undoing each other's work.
The take-home goes in the bin
Hiring engineers for judgement rather than output, and why every part of a normal interview is measuring the wrong thing.
I filed a feature request into my own framework
Building on your own framework means finding its gaps as a user rather than an author, and having to file the request against yourself.
Everyone wants Rust's safety, nobody wants Rust
Refereeing the memory-safety retrofit argument from someone who ships framework code in both Rust and Go, and likes them for different reasons.
Generate a command from a script or a sentence with go-tool-base
Generating a Go command from a shell script or a plain sentence, and the repair agent that has to make the result build before you see it.
Why I still write code
The case for a head of engineering staying hands-on, written as a confession rather than a boast, because the compulsion is the problem.
Anything under an 8
The national vulnerability database is buckling under defunding and volume, which changes what a severity score is actually worth.
Building a CLI with go-tool-base, part 4: an AI dungeon master
Build an AI dungeon master in Go: keep the model to prose only by putting the rules in the system prompt and the mechanics in typed tool calls.
Building a CLI with go-tool-base, part 3: expose your CLI to AI agents
Expose an existing Go CLI to AI agents over MCP without writing any AI code, using built-in commands. The agent reach equals the CLI reach.
