Introduction I've been seeing more developers say that Codex has become easier to use, more cost-effective, or simply a better fit for some workflows than it used to be. This is not a "Claude Code is bad, everyone should switch" article. I still use Claude Code at work, and if cost were less of a factor in my personal setup, I would probably be using both more actively. If you're already comfort
Last Tuesday I lost about three hours to a regression in our checkout service. The cart total was off by a cent on certain promo combinations, and the only signal was a Slack ping from finance with a screenshot. No stack trace. No exception. Just wrong numbers. I did what I always do first. I opened the diff for the last deploy, scrolled, squinted, and tried to feel my way to the bug. Forty minute
Hello everyone! I wanted to write this article to share my experience with agentic coding without Claude and Codex, I started dabbling with agentic coding a few months ago when Claude had decent limits on the 20$ plan, You prompt the agent: I want e2e tests, and it will study the codebase and implement them. When I've started hitting limits on Claude code, and this is not a secret that they reduc
I Built a VS Code Extension to Bring IntelliJ’s “Show History for Selection” Experience If you come from IntelliJ, you probably miss one super useful feature in VS Code: Show history for selected lines. I built a new extension to solve exactly that. Show History for Selected Code This extension helps you inspect Git history for a specific code selection, not just the whole file. Shows commit h
Microsoft's 'Co-Authored-by Copilot' Tag: Unpacking the Strategic Play for AI Dominance in VS Code The persistent insertion of 'Co-Authored-by: Copilot' into commit messages within VS Code—often irrespective of GitHub Copilot's active contribution to specific changes—is far from a benign engineering detail. It represents a calculated, multi-faceted strategic maneuver by Microsoft, signaling a pr
I have a bad habit of jumping between projects. It's not a big deal. But it happens every single day. So I built rewind. rewind That's it. No setup, no IDE, no agent loop burning through tokens. Just one binary, one command, one LLM call. cargo install git-rewind GitHub: https://github.com/Chronos778/git-rewind Would love feedback — on the idea, the UX, anything. Still early days.
If you use GitHub's merge queue and had a rough week around April 23rd, 2026, you were not imagining things. Your code actually disappeared. Not because of a bad commit, not because of a rogue team member, but because GitHub itself quietly deleted it. This is the story of what happened, why it was way worse than the official numbers suggest, and what it means for the way we all trust the tools we
Introduction In Part 1, we successfully moved the resume from a local editor to a live URL. But an empty repository is like a house without a front door, functional, yet inaccessible to those looking in. In this second installment, we’re going back into the terminal to master the art of the README. I’ll show you how to turn a folder of code into a polished, technical portfolio that speaks for it