Engineer by trade.
Writer by choice.

A misguided cache strategy taught us the cost of theoretical assumptions in production systems, where latency and consistency are a trade-off, not a checkbox.

I stopped buying books for a year and found new value in the ones I already owned, my approach to reading changed and so did I

I spent a week with no meetings, watched my team figure things out on their own, and discovered that fewer scheduled talks can boost ownership and clarity.

I still remember a code review that went horribly wrong and what I learned from it about giving and receiving feedback. My feedback had been too harsh and not constructive, focusing on criticizing the code rather than helping my colleague improve.

My first on-call rotation was a chaotic experience that taught me the value of documentation in system design. I learned more about it in one week than in years of writing code.

I spent years building a system that had grown unwieldy, forcing me to scrap it and start over. The experience taught me valuable lessons that I still apply to software development today.