theflyingcoders

How this blog is built and hosted for nothing

Mon, 14 Sep 2026 09:00:00 +0100

This site has no server and costs nothing to run. Here is the whole stack, why every piece is the boring choice on purpose, and how fast I can stand one up for you.

How I lay out a Go repo: three layers, one direction

Sat, 12 Sep 2026 09:00:00 +0100

Domain imports nothing and internal owns the logic. Transports hold none of it, whether that is an HTTP handler or a queue consumer, and the data layer swaps under the service without a handler noticing.

Three is a pattern: conventions that survive generated code

Thu, 10 Sep 2026 09:00:00 +0100

An agent will happily write the same function four times in four files, each slightly different, each passing its own test. So will a tired human on a Friday. The volume just went up, so the habit that keeps a codebase coherent has to be written down where anyone, and anything, working in the repo will read it. Here is the one I lean on hardest.

Services

Mon, 01 Jan 0001 00:00:00 +0000

Three things we do. Most engagements start as a scoped piece of one of them, and we’d rather tell you it’s the wrong one than sell you the wrong one.

Start a conversation

Mon, 01 Jan 0001 00:00:00 +0000

Mail is best: hello@theflyingcoders.dev. No forms required, no discovery call before the discovery call.

theflyingcoders is one platform architect, writing in the open.

Mon, 01 Jan 0001 00:00:00 +0000

I’m Mark Smith. I’ve spent 10 years on backend platforms, mostly Go, mostly the services other teams quietly depend on. The “we” everywhere else on this site is deliberate: engagements sometimes bring in people I’ve worked with for years. The person answering your mail is still me.