A senior developer does have years of experience. Experience is how they get that sixth sense you talk about. Years of making mistakes and learning from them gives you a spider sense about when your approach to a problem solution will cause you to code yourself into a corner, perhaps resulting in performance issues, maintainability issues or say bugs resulting from adopting to quickly immature new technologies with rapidly changing code bases resulting in code which is discarded and rewritten completely shortly afterwards. These kind of pitfalls are traps many inexperienced programmers fall into because they need to learn from failure as well as success. Sometimes success is based on not picking the newest technology, programming language or tools, because the senior developer knows what skills everyone has in general and can gauge the reasonable time needed to meet deadlines and knows when to choose a well traveled path vs. a new and untried one in order to get the project in on time, hence securing future funding. I have found newer programmers will always argue for new technologies without consideration to other factors. This is not to say senior programmers don't embrace new technologies and approaches, only that they know when and when not to. Experience is not a bad word or a bad thing to have. In fact most experienced senior programmers review completed projects to determine how well they went, what they could have done differently or better or not at all. That is how we learn the most from our mistakes! That is how you become a senior developer/programmer with all the qualities listed in this article.
Oh P.S. Something the article seems to gloss over a bit, writes good code documentation. You're not there, where ever you are, to impress everyone with your cryptic code, because you are the only one who can understand it and modify it or for some personal job security. That is NOT how a good senior programmer/developer behaves.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A senior developer does have years of experience. Experience is how they get that sixth sense you talk about. Years of making mistakes and learning from them gives you a spider sense about when your approach to a problem solution will cause you to code yourself into a corner, perhaps resulting in performance issues, maintainability issues or say bugs resulting from adopting to quickly immature new technologies with rapidly changing code bases resulting in code which is discarded and rewritten completely shortly afterwards. These kind of pitfalls are traps many inexperienced programmers fall into because they need to learn from failure as well as success. Sometimes success is based on not picking the newest technology, programming language or tools, because the senior developer knows what skills everyone has in general and can gauge the reasonable time needed to meet deadlines and knows when to choose a well traveled path vs. a new and untried one in order to get the project in on time, hence securing future funding. I have found newer programmers will always argue for new technologies without consideration to other factors. This is not to say senior programmers don't embrace new technologies and approaches, only that they know when and when not to. Experience is not a bad word or a bad thing to have. In fact most experienced senior programmers review completed projects to determine how well they went, what they could have done differently or better or not at all. That is how we learn the most from our mistakes! That is how you become a senior developer/programmer with all the qualities listed in this article.
Oh P.S. Something the article seems to gloss over a bit, writes good code documentation. You're not there, where ever you are, to impress everyone with your cryptic code, because you are the only one who can understand it and modify it or for some personal job security. That is NOT how a good senior programmer/developer behaves.