From research lab to Dubai operations: what transferred
A short map of skills that survived the jump into automation engineering.
The lab and the warehouse are further apart than the flight from Debrecen to Dubai suggests.
A year ago my days were Motion-X++ categories and evaluation tables. Now they are n8n pipelines, AWS health checks, and an e-commerce team that needs its inventory right by morning. Some skills crossed over intact. Others stayed in the lab, where they belong.
What transferred
Measurement discipline, first of all: deciding what "correct" means before building, and reporting failures with the same energy as wins. Reading documentation the way I read papers. And the research habit of changing one variable at a time — which turns out to be the only sane way to debug a production pipeline.
What did not
Perfect datasets, open-ended timelines, and the luxury of "interesting" failures. In operations, an interesting failure is just an incident with extra steps. The score is kept in recovered hours and unbroken mornings, not points out of fifty.
Production graded my research habits harder than any reviewer did.
This is sample copy for the article template. Replace with the final essay when you publish.
← All stories