Every Check Passed
Most of my essays had gone missing from the page that lists them, on production, and every check passed. The same week turned up five more checks on this site that could not fail. What they had in common.
Posts about building on AWS, including the S3 and CloudFront setup that runs this site.
23 posts · all topics
Most of my essays had gone missing from the page that lists them, on production, and every check passed. The same week turned up five more checks on this site that could not fail. What they had in common.
Twenty-one rooms each taught one durable idea. The capstone movement spends them. Four real systems designed end to end, every move naming the principle it came from, so the whole map reviews itself through practice.
Development environments lie in two directions. Clone production and it is too expensive to use. Mock it and it is confidently wrong. Here is a third option, and a working hybrid lab that joins a Kubernetes cluster on my laptop to a real Windows host behind a real AWS load balancer for about nine cents an hour.
THE DESCENT is eleven films that drill every decision fork in the AWS Solutions Architect Associate exam. 265 forks, ten regions, forty three minutes. Free, no signup, no course. The exam does not really test whether you know what CloudFront is. It tests whether you can tell CloudFront from Global Accelerator when both would work and one word in the question decides. That is what these drill. CC BY 4.0.
The cost movement continues. The Promise is how you pay less for the load you can count on. The Shelf is how you pay less for what you store, and the bet hidden in every cheaper shelf.
The security wing closes. The Lobby is about what should even be reachable in the first place. The Cipher is the last line, where the data itself is useless to a thief without the key.
The security wing of Learning Maps opens. The Keyring is how you stop handing out master keys. The Gauntlet is why one lock is never enough, and how to stack locks that fail for different reasons.
The room about beating distance. A CDN opens a branch in every town so the answer is already next door, and it closes the systems-talking wing of Learning Maps.
Two short films on how a system takes a punch. The Breaker is how you stop one slow dependency from dragging the whole desk down. The Allowance is how you keep one greedy caller from eating the counter.
Two short films that open the services-talking arc of Learning Maps. The Book Drop is how one part of a system hands work to another without waiting on it. The Greeter is how a crowd of requests gets spread across a fleet that can lose a machine and not miss a beat.
Two short films that open the coordination story of Learning Maps. The Vote is how a cluster of unreliable machines agrees on one leader and one truth. The Ring is how the pieces survive machines coming and going all day.
Six short films on what happens to data the moment it stops fitting on one machine: the forced choice, the dial, taste, the cache, the branch library, the shard. The first wing of Learning Maps, the durable principle under each rented AWS label.
AWS is taught as two hundred services. Underneath it is a handful of primitives, and every service is a frozen answer to a distributed-systems trade-off. The map I built studying for the SAA-C03, and the two questions that decode any new AWS service.
A static site has no server to check a password, which is fine right up until the day you need one. My staging site is the problem in miniature. It is a full mirror of production, except it also carr...
A strict Content-Security-Policy on a static site allowlists inline scripts by hash. Change one script, forget to update the hash, and every page renders blank. The incident that taught me, and the deploy guard that ends it.
This site was rebuilt from scratch by directing an AI agent, then migrated off cPanel onto AWS S3 and CloudFront. Here is what that actually looked like, the parts that worked, and the day a deploy script quietly deleted production.
AWS is math and Kubernetes is physics, the galaxy and the atom. With managed services you watch the cost; with packed containers you watch the performance. When to reach for each, and for both.
A study film for the AWS SAA-C03 exam, and what moved my practice score: question shapes, trigger phrases, multi-select layers, Security first, and pacing. Rhyming triggers over an EDM bed.
A 3:40 pop-EDM battle-rap. Plan 9 the Bell Labs bunny puts on his headphones at 03:14 UTC, slips into an AWS Availability Zone, and raps every service he passes (Lambda, S3, KMS, kubectl, EBS, Glacier) over a deadmau5-flavoured rework of Bach's Toccata in D minor. Three voice personas (lead Plan 9, autotuned female ad-libs locked to A4, deadpan whisper) plus a Transformer-droid layer in the gaps that delivers the Werner Vogels easter egg, "everything fails, all the time," and the universal devops punchline, "it's always DNS." Five passes from baseline to ship.
Plan 9 the bunny finds a way into the AWS cloud and, at the peak of an A-minor rave track, the camera pulls back on a swarm of dancing Miyazaki bunnies running everything. This is fine.
Plano Noveno, the Plan 9 bunny in Italian-brainrot form, battle-raps the AWS Solutions Architect syllabus as silly Italian mascots: Bucketino Glaciereno, Lambdino Cold-startino, Dynamosa Partizionella. Sound over meaning.
A transparent look at the active workstreams in May 2026: trading systems, animated films, music synthesis, a published book, and an AWS cert study track. All of it agent-directed.
Building the Organic Arts back office on AWS with AI in weeks: CDK stacks for identity, networking, compute and security, and what holding all of it in my head cost.