slaptijack

Designing Data-Intensive Applications, 2nd Edition is the kind of software book that should make an experienced engineer slightly uncomfortable in a productive way. Not because it is obscure or needlessly academic, but because it reminds you how many "simple" backend decisions are really distributed systems decisions wearing a product feature …

Bazel 8.0.0 was not just another build-tool release. It was the release where Bazel stopped politely suggesting that teams should modernize their dependency management and started making the new world harder to ignore.

The headline changes were Bzlmod becoming the default, WORKSPACE being disabled by default, and more …

Natural language developer queries sound like a toy until you watch someone spend ten minutes answering a question the platform already knows:

• "Who owns the checkout service?"
• "Where is the Terraform for staging Redis?"
• "What changed before the payments incident?"
• "Which services still point at the old Kafka cluster?"
• "Where …

Backstage is already where many platform teams want developers to go for service ownership, docs, APIs, runbooks, and operational metadata. The problem is that developers do not always want to navigate a portal. Sometimes they just want to ask a question:

• "Who owns checkout-service?"
• "Where is the runbook for restarting …

Git is usually the first place developers look when they need to understand a system. That makes sense. The code is there. The commit history is there. The pull requests are there. If you are lucky, the README is not lying too badly.

But Git is only one layer of …

Bazel is fast, reproducible, and battle-tested at scale — but when something breaks, good luck deciphering its logs. Between action cache messages, output groups, and 500-line stack traces, figuring out why a build failed often feels like solving a riddle wrapped in a C++ binary.

In this article, we’ll build …

CI/CD build failures can be brutal — especially when the logs are long, noisy, and cryptic. Developers often waste precious time parsing through thousands of lines of output just to find the root cause. What if your tools could summarize the problem in plain English?

In this article, we’ll …

Secure prompts are not magic words. They are operating instructions for a system that is about to read code, logs, tickets, diffs, infrastructure settings, and possibly the occasional thing that should never have left a developer's laptop.

That is why prompt security matters in developer workflows. The prompt is not …

Pre-push hooks are your last line of defense before questionable code hits the remote repo. Traditionally, they’re used to enforce tests or linting, but they can be brittle and overly rigid. What if, instead, your push triggered a context-aware AI that reviewed your code against team policies, security best …

Merges often bring in massive changes — sometimes dozens of commits and hundreds of lines of code — and the first thing developers ask is: “What just happened?”

Wouldn’t it be great if Git could summarize what a merge brought in, in plain English, right after you run git pull or …

Keeping changelogs up to date is one of those development chores that everyone agrees is important… and everyone forgets to do. Manual changelog curation often falls behind or gets skipped entirely. But what if your Git workflow could automatically generate changelog entries, summarize diffs intelligently, and update your CHANGELOG.md …

Now that you’ve got a fully functional, Python-powered Git hook CLI backed by OpenAI, the next step is sharing it — the right way. A downloadable GitHub repo template helps your teammates (or the open-source world) clone, customize, and integrate the tooling into their own workflows with minimal friction.

In …

Building a local Git hook with Python is great, but if you want others on your team (or across multiple repos) to use it, you’ll want to package it as a reusable command-line tool. In this article, we’ll turn our AI-powered Git hook into a proper Python CLI …

Git hooks are one of the most powerful — and most underutilized — features in the Git ecosystem. They allow you to automate actions at key points in your Git workflow: before committing, before pushing, after merging, and more. Traditionally, these hooks are implemented using shell scripts, but that’s limiting in …

GitHub Copilot is impressive, but what if you could build your own AI-powered Git assistant tailored to your workflow? In this article, we’ll walk step-by-step through building a command-line Git assistant using Python and OpenAI’s API. It will explain diffs, write commit messages, generate .gitignore files, and even …