Welcome back to The Modern Software Developer. This month’s issue was inspired by a recent coaching client trying to define their level in the industry. One of their questions was, “How do you define a mid-level developer…?” It’s a good question that led me to think about the role a little deeper, reflect on the 100s of mid-level developers I’ve worked with over the years and produce this issue, “Avoiding The Classic Mid-Level Developer Trap”…
Stumbled across this article by chance, and I am so glad that I did!
Currently working as a Junior Data Engineer, but I really appreciated how you laid out the expectations and outlined what differentiates a Mid-Level from a Junior, something I am trying to bridge the gap between.
Superb. This article is something to get at hand in your pocket and read it every time you want to progress in something. You can replace mid-level for junior, senior or any other existing title. I believe it also allows anybody to fight against the impostor syndrome.
This describes what you can do by yourself that is really important but, you should care about external factors as well, for example, if there is room for another senior dev, or the project budget allows for it, etc. I would like to read you an article about this if possible. What do you think?
I was targeting the idea of "Focusing Mid-Level" a lot. Mainly from the perspective of leaders and the culture.
This one here is a great article that shows us the perspective of the developer in detail when in the mid-stage.
Thank you, Richard. This was inspirational.
Some great points in here - and in particular I think your focus on using the time at mid-level to focus on introspection and evolution beyond simply 'getting better at coding' is really very important, and not something we tend to talk about a lot!
Richard this issue of your newsletter is terrific!
It's like an entire book distilled!
Thank you so much for sharing your experience.