So, you are a middle developer. Moving from the status of a junior developer to the middle was not difficult. However, it seems as if no matter how much you try, you cannot become a senior developer. Moreover, you frequently feel that the projects aren’t as attractive as they used to be, and the joy from completing even the most challenging task has gone.
Why so?
How to Reduce Onboarding Costs by Using a Code Repository
Onboarding new developers into a project is a time-demanding and costly process, isn’t it? Just finding a proper specialist isn’t sufficient. We all know that every software development company has its own practices and uses its own tools. And those tools might even be in-house developed.
Therefore, it doesn't matter how skilled and experienced your new team member is, they will need to learn a lot. Sometimes, it takes pretty much time for them to learn all about the project they start working on (to start coding new features, for example), about the company’s corporate culture, and the commonly accepted practices and processes. Needless to mention the extensive documentation, and similar.
Why We Need Tool Choice: A Developer’s Story
As I landed my first real job as a developer, Britney Spears had the song of the summer, Y2K bugs were about to throw the world into the dark ages, and everyone on my new team used the same tools to code, test, and deploy. As a fresh-out-of-college noob, I was thrown onto tools with steep learning curves resulting in low productivity rates. I thought it was the way it worked and I had to pay my dues to get comfortable with the system.
I have since come to understand that there are better processes. In the words of Britney, Oh baby, baby, how was I supposed to know that something wasn't right here?
Your dev team lead is not controlling enough
Three phases of a controlling engineering manager
Every morning, I see the unfiltered thoughts of 1200+ engineering leaders as one of the community moderators in the Dev Interrupted Discord server. We start every day with a Daily Interruption topic about how to make agile work in real life; scaling teams, building culture, hiring, continuous improvement, metrics - fun stuff like that.
Recently this Daily Interruption popped up and stopped me in my tracks:
Why Does a Dev Need to Know About DevOps?
Like any developer, priority number one is to produce readable, reusable, and maintainable code. Only those items would be enough to write many books, but not only did the area of development itself grow, the area of operations grew rapidly, and in a segment where once it was only the "infrastructure field", Operations now stands out as its own area with professionals, tools, literature, as well as more and more work opportunities related to the now called "DevOps."
Part of the DevOps concept itself has features directly related to development, so being a software developer today and neglecting this trend is almost impossible. Moreover, it can be somewhat detrimental to your career by not noticing what goes on around you.