After developing Paledev Dark Theme for Visual Studio 2026, I decided to bring the same visual identity to Visual Studio Code. Paledev is a modern dark theme inspired by Palenight, built for better readability, stronger contrast, and long coding sessions. clear code readability balanced contrast a clean, consistent palette comfort during long sessions A theme is something you see for hours every d
The problem Every time you open ChatGPT or Claude, it has zero memory of your project. You spend the first 10 minutes of every session re-explaining your stack, your folder structure, your naming conventions, your architecture decisions, before you can ask the actual question you came to ask. 63% of developers in the Stack Overflow 2025 survey (49,000 respondents) said AI tools lack crucial contex
The Problem Most engineers deploy to Kubernetes by clicking buttons in a UI. I built Archnet — a fully automated Internal Developer Platform What is an Internal Developer Platform? An IDP is the infrastructure layer that sits between your code How code gets deployed How secrets are managed How the system monitors itself How failures get detected and fixed Most companies pay Humanitec or Backsta
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
We had ArgoCD running perfectly. Every deployment was reconciled from Git. Drift detection worked. Rollbacks were one-click. Our GitOps setup was clean. Developers still couldn't provision a staging environment without pinging the platform team. That gap — between "GitOps in place" and "developers can actually self-serve" — is where most platform engineering teams get stuck. GitOps solves a real p