About Practical Engineering Management
Engineering management rarely gives you clean problems.
You make decisions with incomplete information. Priorities shift. Systems behave differently in production than they did on paper. People need answers before you feel certain enough to give one.
Practical Engineering Management is for technical managers operating under that kind of uncertainty.
I write practical tips, field notes, and first-principles insights to help you make better decisions when there is no obvious playbook.
What you’ll find here
- Ways to make progress without pretending to have certainty
- Small, tactical bets that reveal what is actually happening
- Lessons from leading technical work under real constraints
- First-principles thinking applied to teams, systems, and decisions
- Useful ideas you can test in your own work
This is not management advice from a distance. I’m interested in what survives contact with reality: what worked, what failed, what changed my mind, and what I would try next.
Why I’m writing this
Much of engineering management is presented as a collection of answers: the right process, the right team structure, the right way to lead.
Real work is messier.
The same practice can succeed in one team and fail in another. The important skill is not memorizing more answers. It is learning how to see the situation clearly, test your assumptions cheaply, and make the next decision with better information.
That is what I want to explore here.
About me
I’m Justine, CTO of a Philippine-based startup I’ve helped grow through millions of pesos in client projects. I lead technical teams, shape product and infrastructure decisions, and work directly with clients.
I’ve spent more than eight years building software across logistics, data analytics, internal business systems, and public-service platforms.
My technical roots include graduating magna cum laude from one of the country’s leading universities and earning multiple national and international awards in robotics, informatics, and applied science, including as a Philippine representative abroad. I’ve since been invited by technical, academic, and civic organizations to speak about engineering and technology.
My work has taught me that technical leadership is less about always knowing what to do and more about finding a useful way forward when nobody has the full picture.
If you’re figuring this out too, I hope these notes make the work a little clearer and less lonely. Subscribe—I’d be glad to have you along.