HeyJaredHands-On DevOps Engineering
60-Day Intensive Program Building Ultra-Scalable Platforms: From Zero to Production Scale
- Indexed issues, last 90 days
- 16
- Latest publication
- Sep 30, 2026
- Audience
- Checking…
- Earliest in this view
- Aug 7, 2026
Latest issues
Day 61: Anonymous Polling — Voting with ZK-SNARKs (opens the original)
Read excerpt
The Abstraction TrapHere’s how a junior engineer ships “anonymous voting” in 2026: pull in a Node.js wrapper around snarkjs, spin up a verifier microservice per proof request (often literally docker run or a forked Python py_ecc process because “the crypto library needs its own runtime”), and enforce one-vote-per-person with a Postgres UNIQUE(nullifier_hash) constraint on the votes table. It demos beautifully at 50 concurrent users in a conference talk.The abstraction hides three things simultan
Day 60: ZK-Proofs — Verifying Age Without Private Data (opens the original)
Read excerpt
The Abstraction TrapHere’s how this ships in most shops: a junior engineer gets the ticket “add age verification for regulated content,” pulls a KYC vendor SDK, wraps it in a Node.js Express service, containerizes it, and calls it done. The request flow looks like this — client sends {dob: "2003-04-11"} over TLS, the service POSTs that payload to a third-party verification API, the vendor’s response gets cached in Postgres “for audit purposes” alongside a verified_at timestamp, and a sidecar cro
Day 58 — The Fediverse Inbox: Receiving Mastodon Updates at Hyperscale (opens the original)
Read excerpt
The Abstraction TrapHere’s how a junior engineer solves “accept signed ActivityPub Create deliveries for every tenant inbox”: terminate TLS in nginx, forward every POST /inbox/:tenant into a Node federation worker, verify the Signature header against whatever bytes arrived on the wire, JSON.parse the activity into a heap object, push it onto a Redis queue, and let each tenant’s delivery worker drain at leisure. It looks correct in the Mastodon-compatible screenshot. It collapses the moment a wav
Day 57 — Federated Identity: ActivityPub Actor Discovery at Hyperscale (opens the original)
Read excerpt
The Abstraction TrapHere’s how a junior engineer solves “resolve @actor@host into a usable Actor document for every tenant”: hit a remote WebFinger endpoint over HTTPS, chase the rel=self link into an ActivityPub Actor JSON blob, deserialize the whole claim graph in a Node federation sidecar, stash the result in Redis keyed by acct-handle with a 60-second TTL, and let each tenant pod call that sidecar on every delivery attempt. It looks correct in the Mastodon-compatible screenshot. It collapses
Day 59 — The Fediverse Outbox: Domain-Sharded Fan-Out at Hyperscale (opens the original)
Read excerpt
The Abstraction TrapHere’s how a junior engineer solves “deliver one signed ActivityPub Create to every follower inbox”: serialize the activity once in the app, then — for each of the N followers — canonicalize again, Ed25519-sign again, open a fresh HTTPS connection (or pull a pooled one that still pays a userspace copy), POST the body, and push failures onto a Sidekiq/Redis retry queue keyed by follower id. It looks correct in the Mastodon-compatible screenshot. It collapses the moment a popul
Publishing over time
Last 90 days. Choose a month to open its work.
Recurring subjects
Named in the text we hold. One piece can cover several.
Audience
No verified audience measurement yet.
About this data
Counts cover the work we have indexed. Tone needs enough text and a confident classification. Excerpts and episode notes are not full articles or transcripts.
Identity or attribution wrong? Suggest a correction.