AI Coding
Using AI coding assistants without losing control of your codebase: reviewing generated code, spotting the risks that don't show up in a diff, and keeping your own skills sharp.
4 articles tagged AI Coding.
Git tips and tricks I'd teach every developer on day one
Most developers use five Git commands and fear the rest. These are the ones worth learning next: undoing mistakes safely, finding the commit that broke things, cleaning up history, and working on two branches at once, with exact commands.
Slopsquatting, leaked secrets, and other AI coding risks
AI coding assistants bring risks that go beyond buggy code: invented packages, secrets in prompts, poisoned instruction files, and agents with too much autonomy. Here's what the risks are and a practical program for managing them.
A checklist for reviewing AI-generated code
AI-written code usually compiles, usually looks tidy, and is sometimes wrong in ways that read as convincing. This checklist covers what to look for: scope creep, weakened tests, missing authorization, invented packages, and quiet performance traps.
A practical Claude Code workflow for real projects
Claude Code works best when you treat it like a capable colleague with a tight feedback loop: plan first, work in small verified steps, commit often, and keep its context clean. Here's a workflow that holds up on real codebases.