Change is scary! Three months ago, ahead of my first day as a Developer Advocate, I had the same pre-first day butterflies in my stomach that I do with every change. Would I be good at this? Was it the right decision?
Despite my strong preparation and research ahead of taking this role, there were a few surprises I found along the way. Here I share five surprises I’ve encountered in my first 3 months as an advocate, for anyone curious about jumping into advocacy, or even those interested in movement from regulated industries such as banking to tech.
Should I stay or move to a new company? That is a question that many engineers and individuals working in the technology landscape today ask themselves when figuring out their next career move.
I wouldn’t call myself an expert on developers resigning, but I do have a few thoughts on the resignation versus mobility debate. In my 10.6-year tenure, I’ve resigned twice, retracted a resignation once, moved teams twice, been promoted once, and moved roles several more times within teams. This experience has moulded my viewpoints on tech careers.
In this piece, I’ll cover the reasons people, and more specifically engineers, quit; when a move might be a better option for you; and tips for managers on how to handle resignations with grace based on my own experiences on both sides of the table.