Writing from the work.
Practical guides, field notes, and engineering essays for people who have to operate what they build. Payments, operations software, and shipping.
What agencies should know before adding payments to a client project
Clients ask for 'a payments option' as if it were a plugin. It is a long-lived responsibility. Here is how to scope it without becoming a payments company.
By Omar Farouk
Designing adapters that do not try to own your ERP
Operations software earns trust by sitting between systems, not replacing them. The adapter layer is where that promise is kept or broken.
By Daniel Whitfield
Paying contractors in stablecoin: an operational playbook
Faster settlement is easy to promise. The hard part is approvals, records, and an ERP that still has to balance. Here is how a field-services company did it.
By Omar Farouk, Layla Haddad
Idempotency in payment intents: making retries boring
Every network call can be repeated. The only question is whether repeating it is safe.
By Daniel Whitfield
Confirmation policy is a business decision, not a constant
How many confirmations is enough? The honest answer depends on the network, the amount, and what you release when you say yes.
By Layla Haddad, Mohamed Saad
Is this internal tool worth building? A worksheet for operations leaders
Before you commission software, put a number on the workaround. A five-step way to decide whether to build, buy, or leave the spreadsheet alone.
By Emily Sinclair, Omar Farouk
TypeScript tips for code that handles money: 20 patterns that prevent bugs
Branded types, exhaustive checks, BigInt arithmetic, boundary validation, and Result types — using the type system to make payment mistakes hard to write.
By Mohamed Hasan, El Sayed Abd Almohaymen
Reconciling stablecoin payments: a treasury operator's guide
Three records, one truth. How to tell what is owed, what is confirmed, and what is still in flight — without opening three tools.
By Layla Haddad, Daniel Whitfield
Handover runbooks: writing for the 2am case
A runbook is not documentation of the happy path. It is a letter to the person who is alone, tired, and looking at something odd.
By Daniel Whitfield, Emily Sinclair
How to choose a software studio: twelve questions to ask before you sign
Portfolios look the same. These questions do not — they surface how a studio scopes, communicates, and hands over.
By Omar Farouk