Software engineer

How things actually work, written down.

I build software, and I’m interested in the mechanics underneath businesses and markets — the part that usually gets skipped. This is where I write that down, and where the things I build end up.

Get the letterRead the writing

Background

Where the writing comes from.

Production engineering

Building and running systems in production — TypeScript and Node, distributed services, infrastructure that has to stay up while people are using it. The habit that transfers: things fail at the seams, and the boring parts are where it gets decided.

Markets, with my own money

I’ve traded gold and crypto with my own capital, and taken real losses doing it. Sitting in a drawdown teaches you things about risk and position sizing that reading about it doesn’t.

How money moves between businesses

Letters of credit, payment terms, guarantees, settlement, and what happens when one side doesn’t perform. Most business advice skips this, and it’s usually where the answer is.

The letter

One idea a week, taken apart properly.

Every Sunday: one idea from business, standards, or character, and the mechanism underneath it. Long enough to be worth the time, short enough to read before the coffee goes cold.

No motivation. No countdown timers. No course at the end of a funnel.

One email a week. Unsubscribe in one click.

Work

A small number of engagements at a time.

I take on a limited amount of engineering and advisory work — architecture reviews, systems that have outgrown the design they started with, and teams that want a second opinion from someone who has run this kind of thing in production.

If that sounds useful, write and say what you’re dealing with.

hamedsedaghatcrt83@gmail.com