War Story: I Ditched My CS Degree for a Bootcamp and Became a Go 1.25 Engineer I never thought I’d be writing this. Two years ago, I was three semesters into a traditional Computer Science degree, drowning in abstract calculus and outdated Java curriculum, wondering if I’d ever write code that actually mattered. Today, I’m a backend engineer working full-time with Go 1.25, building low-latency m
Stripe Payment Flow Explained (Where Does the Money Go?) Most Stripe tutorials show how to take a payment. But they don’t explain the most important question: 👉 Where does the money actually go? Does it come to you first? If you’re building SaaS, marketplaces, or client projects — this matters a lot. ✅ What You’ll Learn 🧠 1. Basic Stripe Payment Flow Let’s start simple. When a customer pays usin
Another confession In the last post, I went after the bug that every Claude Code discipline plugin seems to share: the rules live in the main session, the work happens in the workers (subagents), and the rules don't make the trip across. I named names. I quoted the maintainer of superpowers closing a related issue as "not planned." And then, with a straight face, I claimed that sonmat was differ
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
If you have ever SSH’d into three terminals during an incident, copy-pasting kubectl get, kubectl logs, and kubectl describe while the clock ticks, you already know the problem: manual capture is slow, inconsistent, and easy to get wrong—especially on large clusters. GROOT is a small open-source Go CLI ( Cobra + Viper ) that automates that workflow. You configure namespaces, workloads, and options
AI coding tools are starting to look similar on the surface: they all offer chat, agents, code edits, terminal awareness, and some form of autocomplete. But the real differences are in the workflow. The question is less “which one has AI?” and more “where does the AI live in your development process?” For me, VS Code is still the baseline. It is flexible, extensible, familiar, and easy to compose
Last night, I stayed up too late because I was building something I was excited about. That sentence used to mean something different. A year ago, staying up until 3:30 AM meant I was deep in a feature, fighting CSS, debugging edge cases. Last night, it meant I went from recognizing a repeated workflow problem to having a working, tested, production-ready application. In about twelve hours. (7 of
The codebase was old. React 16 with class components everywhere. React Router v3 with routes-as-children. A webpack 4 config that had been edited by a dozen people over five years and contained loaders nobody could explain. The dev server took 45 seconds to come up. Hot reload was 8 seconds on a good day, 20 on a bad one. The production build was 6 minutes. CI deploys took 14 minutes end to end. I