·9 min read
Your team doesn't want to use AI. Now what?
The CTO buys licenses, sends an email, a month later two out of twenty are using it. Resistance is normal. Here's what works better than a top-down mandate.
Read morePractical tips and insights about AI in software development.
/
+25
Security (2)Refactoring (2)AI Models (2)Workflow (2)advanced (1)Code Review (1)Debugging (1)Documentation (1)Enterprise (1)Cost Management (1)Governance (1)Legacy Code (1)Onboarding (1)Code Quality (1)Collaboration (1)Testing (1)behind-the-scenes (1)ai-workflow (1)case-study (1)Claude Code (1)Tips (1)CLI (1)Guide (1)Comparison (1)Prompt Engineering (1)
·10 min read
CLI agents: why the terminal beats the editor for complex AI tasks
Claude Code, Aider, Goose, Codex CLI — terminal agents have access to everything you do. The editor sees files. The terminal sees the system. That's the fundamental difference.
Read more·8 min read
AI as a pair programmer: when it works, when it doesn't, and how to get the most out of it
Pair programming with AI isn't like with a human. It's better at implementation and worse at decision-making. Understanding that difference changes how you use AI.
Read more·8 min read
Security risks of AI in development: what your team is probably doing wrong
At trainings I ask: 'Who has sent production code to ChatGPT?' Most hands up. 'Who checked for API keys in it?' No hands.
Read more·10 min read
Prompt engineering for developers: a guide that saves you hours every day
The difference between a developer who uses AI effectively and one who dismissed it is often just one better prompt. Here's how to write prompts that work on the first try.
Read more·8 min read
AI and documentation: a practical workflow that actually works
Nobody wants to write documentation. AI turns a half-day task into a half-hour one — and the result is often better than what you'd write yourself.
Read moreStay ahead with AI insights
Practical tips on AI for dev teams. No spam, unsubscribe anytime.