You Do Not Have an AI Adoption Problem. You Have a Verification Problem.
Senior engineers often avoid AI-generated code for rational reasons. The real constraint is not adoption, but the cost of proving that a change is safe.
Articles
I write about the decisions that make or break software teams: AI strategy, vendor choices, technical debt, developer careers, psychology, and the workflows that keep customers and teams aligned.
Senior engineers often avoid AI-generated code for rational reasons. The real constraint is not adoption, but the cost of proving that a change is safe.
LLMs can pass a small document demo and still fail when the same task scales. A simple invoice benchmark shows why deterministic workflows still need deterministic software.
A malicious dependency can read SSH keys, API tokens, and CI secrets before your code ever runs. Safer uv, npm, and JavaScript package manager defaults reduce the blast radius.
AI vendors promise a lot. This checklist helps founders separate real capability from polished sales material before the invoice lands.
AI is making developers faster on paper and more anxious in practice. A psychology-informed look at why teams crack under AI pressure and what technical leadership needs to fix.
LLM features are easy to ship and hard to operate. Five kinds of AI tech debt that quietly build up when teams treat AI as a feature, not as a system.
Every AI feature has three paths: buy it, build it, or fine-tune it. Pick the wrong one and you burn money on complexity you did not need.
A full-time CTO is expensive, slow to hire, and often too much too early. Here is how to decide when fractional technical leadership is enough, and when it is time to hire full-time.
Psychology made me a better engineer, manager, and product thinker. Not because it replaced technical skill, but because it explained the human problems behind the technical ones.
AI will not remove developers. It will remove the parts of the job that looked like development but were mostly typing. What remains is harder, more valuable, and less forgiving.
Most engineers do not lose salary negotiations because they lack talent. They lose because they negotiate from their current salary instead of their market value.
Traditional customers want flexibility, fixed dates, and firm prices. Those things fight each other. Gitflow is one way to keep the fight under control.