The Seniority Roller Coaster and Down-Leveling in Tech
In tech, switching jobs almost always comes with either a financial or a title
upside. However, it doesn’t always come with both. Switching for higher
compensation can result in a “lower” title, like going from Senior Software
Engineer to SWE 2 or VP Engineering to Senior Engineering Manager.
Once you become an engineering executive, an invisible timer starts ticking in the background. Tick tick tick. At some point that timer will go off, at which point someone will rush up to you demanding an engineering strategy. It won’t be clear what they mean, but they will want it, really, really badly. If we just had an engineering strategy, their eyes will implore you, things would be okay. For a long time, those imploring eyes haunted me, because I simply didn’t know what to give them: what is an engineering strategy?
Conflict Free Replicated Data types (CRDTs) can be tricky. You may spend months reading papers and implementing different algorithms before they finally click and become simple. That or they'll seem simple out of the gate and you'll be missing a bunch…
20 Things I've Learned in my 20 Years as a Software Engineer
Important, Read This First You’re about to read a blog post with a lot of advice. Learning from those who came before us is instrumental to success, but we often forget an important caveat. Almost all advice is contextual, yet it is rarely delivered with any context. “You just need to charge more!” says the company […]
It has been a while since I’ve been working as SRE/Platform/Cloud Engineer, and lately and I realize I’ve been repeating some questions to developers that I rarely get an answer for straight away.
These are not meant to make anyone’s life harder, au contraire, the whole pourpose of having a solid answer to this list of questions, is to make everyone less worried about the probabilty of some high stakes, overnight failure or a data handling missuse that could potentially cause big losses, and of course a lot of unnecessary stress.
Shreyas Doshi’s Twitter thread ‘Destined to Fail’ introduced the idea of Customer Problems Stack Ranks — a new way to think about contextualizing the relative priority of the problem a product aims to solve.