about
I have spent most of my career on systems that move physical things — flowers, parcels, vehicles — which means the code has a deadline that does not care about the sprint board.
The work is usually the same shape: a catalog that has to stay correct, a planner that has to stay fast, and an operations team that needs to fix things without calling me. I like the last part most.
What I reach for
- Node and TypeScript for anything new
- PHP where it already earns money and would cost more to replace than to keep
- MongoDB when the shape of the data is still moving, MySQL when it is not
- Redis for queues and locks, and nothing clever on top of it
- Docker and a single well-understood server, for as long as that holds
How I work
I would rather ship a boring thing this week than a clever thing next quarter. I write the runbook before the feature, and I assume I will be the one woken up by it.
History
- 2019—nowLead engineeriTrinityE-commerce and logistics platforms: catalog, pricing, delivery routing.
- 2015—2019Backend engineerTODOTODO — replace with the real history.
Tools
What I reach for without thinking about it.
nodetypescriptphpmongodbmysqlredisdocker
Elsewhere
Mail is the fastest way in — tell me what you are building and where it hurts.
- githubgithub.com/mnohosten
- based inPrague, Czechia