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.
Tags
22 pages
AI
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.
Technical CV writing is still hard, and now a robot reads it first
My CV stopped landing because a machine reads it before a person does. Reworking the structure for the filter without losing the voice.
A configurable AI endpoint is an attack surface
A user-settable AI base URL decides where your API key gets sent. Validating it to reject userinfo, non-HTTPS schemes and redirects.
