Suggestions
Michel Tu
Staff Software Engineer at Google
Professional Background
Michel Tu is a highly skilled staff software engineer currently working at YouTube Ads, under the esteemed Google umbrella. With a deep understanding of software development and infrastructure, Michel proudly contributes to ensuring that YouTube's advertising platform can accommodate all current and future functionalities. His pivotal role within Google not only showcases his expertise but also illustrates his commitment to providing robust, scalable solutions that drive user engagement and enhance the digital advertising experience.
Before his tenure at Google, Michel cultivated a wealth of experience in various technology roles. He started his career as a PHP developer at the Junior Enterprise of Centrale Paris, where he married his programming skills with real-world applications, developing solutions that benefitted both the enterprise and its clients. He later transitioned into a front-end engineer role at RethinkDB, where he contributed to the seamless user interface and user experience design and development. Michel's technical proficiency and attention to detail during this period played a crucial role in improving the product's performance and usability.
Additionally, Michel served as a mathematics teaching assistant at Centrale Pékin. In this role, he not only deepened his understanding of mathematical concepts but also had the opportunity to inspire the next generation of engineers through mentorship and teaching—an experience that further solidified his love for technology and education.
Education and Achievements
Michel's educational background is as impressive as his professional trajectory. His academic journey began at Lycée La Martinière Monplaisir, where he undertook a rigorous Classe préparatoire in Mathematics and Physics. This foundational training equipped him with critical analytical skills and a profound understanding of mathematical principles.
He subsequently pursued a Master's degree in Computer Science, focusing on Artificial Intelligence, Data Mining, and Semantics at Tsinghua University, one of Asia's premier educational institutions. Here, Michel honed his technical skills and explored cutting-edge areas of AI, positioning him well for the demands of the tech industry.
Michel further advanced his engineering expertise by obtaining a Generalist Engineering degree from the prestigious École Centrale de Paris. This distinguished program emphasizes multidisciplinary approaches to engineering and has instilled in Michel a breadth of knowledge across various domains within technology and engineering.
Achievements
Throughout his career, Michel has demonstrated a strong commitment to continuous learning and improvement. His ability to adapt to various roles—from backend development to teaching mathematics—reflects his versatility and eagerness to embrace new challenges. His work at Google has placed him at the forefront of technological advancement, allowing him to be involved in groundbreaking projects that shape the future of digital advertising.
Michel’s educational background complements his professional achievements, giving him a unique perspective on complex problem-solving in software engineering. His focus on AI and data analysis continues to be a valuable asset in his current role, as he navigates the intricacies of advertising technology and infrastructure dynamics.
In summary, Michel Tu stands as a paragon of what it means to thrive in the fast-paced world of technology engineering. His blend of educational prowess, hands-on experience, and visionary thinking has made him a key player at Google. Michel inspires others not only through his professional success but also with his dedication to mentoring and teaching within the engineering community.
Highlights
Growing as an engineer: Limit optional/nullable values
Note: This post aims to be a bit more practical than usual, so let me know if these are interesting to read.
Optional and nullable values are terrible in large systems – this isn’t about aesthetics preferences but maintenance costs, outages and correctness issues. For example, you have probably crossed path with code that looks like this:
function process(order) {
If (order == null) { return; }
// do things with order
}
The issues with optional/nullable values are:
- They tend to propagate everywhere and every call site using them has to write defensive code to figure out what to do when the value is missing – so you have a proliferation of defensive code
- The semantics are unclear – in general this is the problem with defensive code. In the snippet above, is processing a null order a viable call? Why would someone try to process such an order in the first place?
- The defensive code prevents your server from crashing, but it may silence what could be a very bad bug – at the end of the day, you may end up wasting weeks debugging such edge cases (or worse, your company may lose millions until someone realizes that there was a bug).
Similarly as a previous post “Good APIs break early”, it’s much better to cleanly handle null/missing values as soon as they appear and not propagate everywhere. This makes your code more concise, simpler to read and easier to maintain.
#softwareengineering #null #optional #defensivecode
Illustration's prompt: cartoon of a software engineer working on their laptop at their desk and angrily asking "why is this value null???"
Growing as an engineer: Pursuing greatness
There are many reasons certain companies want to hire engineers from Google. Facebook, Databricks, etc. – There are also times when hiring such engineers is a bad decision. One of the interesting reasons I was told is that these engineers have seen ”greatness”.
Greatness here is mostly about technical aspects – some of these engineers have worked on large scale systems like only few have witnessed, some have worked on the bleeding edge of their technical field, some have solved legal issues that exist only for handful companies etc. This experience, knowledge and skills are things you don’t find in academic books as these tend to be a few years outdated – this is one of the experiences certain companies value a lot (e.g. companies who have grown to be successful and are starting to hit similar scalability issues).
If you didn’t have a chance to work in such environments, you may not know exactly what greatness is in your field but you should be aware that greatness is a relentless chase – if you never settle for mediocre systems and continuously push for improvements, you will eventually reach such state (it may take a bit longer though).
A corollary of the statement above is that while you can witness greatness, what matters is to pursue it. This means that not every engineer from top tier companies can replicate what they have seen, especially if they were never part of such efforts. They just have a head start since they know where they should head to but they may not be capable of completing the journey. For example all engineers at Google have a sense of what a good developer experience should be, very few can make it happen in another company.
Last but not least, my 2 cents is that being hungry for greatness is a more valuable trait. There’s a French saying that goes “un intellectuel assis va moins loin qu'un con qui marche” – a smart person sitting goes less far than a dumb person walking. Journeys for greatness are never straight paths since you have many external factors that will make you drift from your goal – this is why relentlessly chasing your goal is the most important thing to do.
#softwareengineering #greatness #journey #chase #hungry
Illustration prompt: cartoon of a software engineer on a journey on their boat toward the sun going down

