Why Some Developers Will Never Improve

In the quickly evolving field of software development not improving is the same as falling behind. Technologies are changing rapidly and those who keep up are rewarded greatly and those who don’t quickly become outmoded. In this article, I will outline the most common ways developers fall behind and how to avoid them. <img alt="" src="https://miro.medium.com/v2/resize:fit:630/0*xrdxX3rSpFuOdJpn" style="height:468px; width:700px" /> By <a href="https://unsplash.com/@bozhstudio" rel="noopener ugc nofollow" target="_blank">Vadim Bozhko</a> From <a href="https://unsplash.com/photos/lbO1iCnbTW0" rel="noopener ugc nofollow" target="_blank">Unsplash</a> <h2>They Don’t (Actually) Take Feedback</h2> Without a doubt, constructive feedback is the major catalyst that propels developers forward in their career and levels up their skillset. Whether it be in the form of Pull Request feedback, manager feedback, team feedback, it can be the difference-maker between a good developer and a great developer. If a developer can’t take feedback effectively, they are putting a ceiling on their skillset and potential. You might be be thinking “I’m great at taking feedback, I don’t take it personally and I’m always nice to whoever’s giving it to me”. Although thats a great thing to do, it’s not how you should be taking feedback. Feedback should redefine how you code and engineer, at least in some small way. It’s not something you incorporate only on one or two pull requests to appease whoever gave you the criticism. <a href="https://levelup.gitconnected.com/why-some-developers-will-never-improve-d7f095df9604">Read More</a>