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
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
E aí, gurizada! De uns tempos pra cá, eu percebi um burburinho enorme em torno de uma ferramenta que tem chamado a atenção, e não é por menos: o OpenClaw. Eu, que vivo mergulhado nesse universo de IA e automação, gravei um vídeo recentemente, que está lá no meu canal, assista no YouTube, justamente pra desmistificar essa parada. E hoje, vim aqui no Dev.to pra gente conversar um pouco mais sobre o
Uma skill ruim gera código ruim em escala. Uma skill boa gera código bom em escala. A diferença entre as duas não está na ferramenta, está em como a skill foi construída. Quando uma skill é criada sem contexto suficiente, a IA passa a alucinar sistematicamente: gera código tecnicamente válido, mas semanticamente errado. E faz isso toda vez que a skill é chamada, para todo mundo que a usa. Percebi
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.
The blog you're reading right now was built in a single conversation with Claude Code, Anthropic's CLI, in about 30 minutes. No all-nighter, no purchased template, no WordPress. One working session in the terminal. Here's exactly how it went — real code, real commands, and what almost went wrong. My portfolio web-developpeur.com does its job: showcasing my background and projects. But a static sit
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