I am a software engineer at Uber, working on a large scale highly distributed systems with Golang, Java and Python.
My interests are in distributed systems, software engineering and architecture, programming languages, engineering culture and effective teams.
I believe in engineering done right: in good architecture design and well crafted code focused on solving the customer’s problems. I always nurture good peer code review practices in my teams: reviews that enure correctness and robustness before everything else and then go above and beyond to improve the overall system design and code health.
I also teach C++ and OOP in my alma mater – New Bulgarian University.
If you want to get in touch – LinkedIn would be my preference.
Unconditional code is code that just works, without errors or exceptions, without funny edge cases represented with tedious IF statements. In this article I will share how this can be applied to situations in Golang where you need to map incoming protobuf messages to internal or external (i.e. outgoing) structures. A Word about Golang Golang …
Have you ever had your head explode while trying to trace the execution of a use case through a complex codebase? Well, I certainly have. Sometimes the code I am trying to decipher is my own, marking the process not only painful, but shameful as well. In this article, I will explore the concept of …
Well, can you blame them? Code reviews might be the only thing in software engineering that is universally considered “good” and “the right thing to do”. Furthermore, it is one of the few things that are empirically proven to improve our software . And yet, I oftentimes hear particular about reviews. Nobody complains about the …