A sequential mini-course in Git for people who ship — fundamentals and conventional commits, then the branching, review, and collaboration workflows that hold a team together.
1Conventional Commits, End to End
2A .gitmessage Template and Commit Hooks That Enforce It
A field guide to system design for the engineer who has to make the call and ship it — no FAANG-scale hand-waving. The five axes of every tradeoff, the CAP theorem without the folklore, idempotency, caching, designing for failure, and a full worked design at the end.
Who can do what, and how you prove it — roles vs attributes, policy tests that hold the line, multi-tenant isolation, audit trails, and what happens when permissions become a graph.
1RBAC vs ABAC: Roles, Attributes, and Where Each One Breaks
2Testing Authorization Policies Like the Boundary They Are
3Multi-Tenant Authorization: One Database, Many Customers, Zero Leaks
A working dev's field guide to coding agents — what "agentic" actually means, Claude Code in the terminal, the feedback loops and guardrails that make it trustworthy, and shipping real features from prompt to deploy.
CVE-2026-109618 and CVE-2026-109619 are unauthenticated remote code execution flaws in PHP core, both rated CVSS v4.0 9.2. Fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released 21 October 2026. What the bugs are, who is at risk, and a patch-day checklist.
The LORD Will Provide is a name Abraham gave on a mountain where he almost lost his son — not in a season of surplus. Genesis 22:14 on what God actually provides, and why the provision often looks nothing like cash.
He who speaks in a tongue edifies himself, but he who prophesies edifies the church. 1 Corinthians 14:4 on the private prayer language that strengthens you — and why public worship aims at building up everyone.
You cannot lead people where you have never been. You cannot preach with power what you are not practicing with integrity. Ezra 7:10 on why the order — study, obey, then teach — is everything.
Auto-increment works right up until you add a second writer. The story of how distributed systems mint unique IDs without asking each other permission — ticket servers, UUIDs and the birthday math, Snowflake and ULID, and the one idea underneath all of them: who owns which slice of the ID space.
Google's Zanzibar modeled access as relationship tuples — editor of the folder that contains the doc. When your ABAC policies turn into chains of relationship-walking, ReBAC (OpenFGA, SpiceDB) is the tool built for it. What it buys, what it costs, and the seam that keeps you free to adopt it later.