--- You should drive the car to the car wash, but you should walk yourself.

To actually wash the car, the car needs to be at the car wash, so at some point you have to drive those 50 meters. A sensible approach is:

- Drive the car the 50 meters to the wash bay. - Park or queue as required, then get out and do the wash. - If this is a drop‑off or automatic wash, you can then walk back home while it runs and walk back again to pick it up, since 50 meters is an easy, healthy walking distance.

DevSecOps Engineer United States Army Special Operations Command · Full-time

Jun 2022 - Jul 2025 · 3 yrs 2 mos

Honestly, it is a little scary to see someone with a serious DevSecOps background ship an AI project that looks this sloppy and unreviewed. It makes you question how much rigor and code quality made it into their earlier "mission critical" engineering work.

This person was in communications of the 160th Special Operations Aviation Regiment, the group that just flew helicopters into Venezuela. ... And it looks like a very unusual connection to Delta Force.

Each chapter focuses on one HTTP concept and shows the same runnable example across net/http, Chi, Gin, Echo, Fiber, and Mizu. The key idea is that the README files are the single source of truth. All example code is generated from them and verified to compile and run (some may contain errors, let me build proper CI/CD later).

It is meant as a practical reference and a way to understand where frameworks differ in responsibility and wiring, not just syntax.

Book view here: https://github.com/go-mizu/go-fw/blob/main/BOOK.md

I've kept running into the same problems in popular Go frameworks: hidden context mutation, magic middleware ordering, reflection-heavy binding, and APIs that slowly drift away from the standard library. The Gin ecosystem in particular has accumulated a lot of technical debt and footguns, which this post summarizes well: https://eblog.fly.dev/ginbad.html

Mizu is deliberately boring by design:

  - Built directly on Go 1.22 http.ServeMux
  - Explicit middleware chains with clear scoping
  - No reflection, no codegen, no global state
  - A real request context type that still interoperates with net/http
  - First class graceful shutdown and error handling

Docs: https://docs.go-mizu.dev/overview/intro

https://savannah.gnu.org/users/ttn

> For the love of clean code history, let's remember we're not monkeys banging on keyboards; we're educated, civilized human beings.

A single `events` table falls apart as the system grows, and untyped JSONB data in `event_data` column just moves the mess into code. Event payloads drift, handlers fill with branching logic, and replaying or migrating old events becomes slow and risky. The pattern promises clarity but eventually turns into a pile of conditionals trying to decode years of inconsistent data.

A simpler and more resilient approach is using the database features already built for this. Stored procedures can record both business data and audit records in a controlled way. CDC provides a clean stream for the tables that actually need downstream consumers. And even carefully designed triggers give you consistent invariants and auditability without maintaining a separate projection system that can lag or break.

Event sourcing works when the domain truly centers on events, but for most systems these database driven tools stay cleaner, cheaper, and far more predictable over time.

You rarely replay them to reconstruct business state; you just pump them into analytics or enrichment pipelines.