Working With AI: What Actually Works For Me
I think a lot of people still imagine AI coding as opening ChatGPT, asking for code, and copy-pasting the result. That's not really how I work anymore…
Latest Team Management news from Tech News
I think a lot of people still imagine AI coding as opening ChatGPT, asking for code, and copy-pasting the result. That's not really how I work anymore…
Every time I asked Claude to review my branch, I got one of two answers: a cheerful "Looks good! 👍" or a vague list where I couldn't tell a real bug f…
Think about the last time you merged a PR without a proper review. Maybe tests passed. Maybe it looked fine at a glance. Maybe you were moving fast an…
GitHub moved Copilot Chat's richer pull request experience to general availability this week — side-by-side chat with diffs, inline editing, and conte…
TL;DR — AI assistants are producing C# that looks correct and passes review, but reintroduces production regressions we spent years training out of te…
When a PR on my team crosses 500 changes, it gets the same response every time: this one's too big...let's break it down. I don't enjoy being the line…
When you ship alone, nobody catches your 2 AM mistakes. This article gives you a working Claude-powered review bot that runs on every pull request via…
For the past ten days I've been building a GitHub bot that reviews pull requests against a team's own written conventions. Not a generic "linter with …
If you searched "AI code review" six months ago, the landscape looked roughly like CodeRabbit, a handful of GitHub-bot startups, and your IDE's built-…
Last month I approved a 847-line pull request after spending maybe twenty minutes on it. Tests were green. Linter was clean. Coverage sat at ninety-on…
What "agentic" actually buys you over a linter, why single-model approaches stall, and why false positives — not raw model capability — determine whet…
I shipped 3 bugs after 'looks good to me' AI code review last quarter I had one of those quarters where every PR went through an AI reviewer, every PR…
Your team's code review process was designed for a world where a developer wrote every line. In that world, a PR with 200 lines meant 200 lines of hum…