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.
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.
God did not part the Jordan while Israel rested in their tents. He waited until the priests stepped into the flood-stage water. Joshua 3 on why faith moves first — and the miracle meets the movement.
Authorization decides what happens; the audit trail proves what happened. What a useful audit event records, spatie/laravel-activitylog for model changes, logging the denials (not just the changes), and why append-only is the property that makes it an audit log at all.
A full FrankenPHP local dev setup on macOS — one catch-all config that serves every site in /var/www/sites with no per-site vhost, a launchd daemon that survives reboot, and an fp-pin helper that routes legacy projects to older PHP-FPM pools. Plus how to evict Nginx or Apache and translate their config.