4 ms·
I have always worked along the lines of most people here and the article. A Senior Developer is one that has amassed not only solid development experience acro
by amcrouch 10y ago
I have always worked along the lines of most people here and the article. A Senior Developer is one that has amassed not only solid development experience across multiple projects but also has a solid knowledge of your product code base. Someone that can just get stuff done and leads by example. Applies best practices and is pragmatic and always add's value to the code base.
I agree that titles are handed out too easily however, developers are partly to blame here. I have held numerous titles over my career but they are meaningless. Experience is built over years for learning and applying your trade and for those that want to continue doing that where do they go after "senior"? If developer's were not so desperate for the title then this discussion and the questions being raised would be moot and we'd all be back coding.
- JesseObrien 10y agoI read a great article a few months ago talking about how success as a developer could be looked at from a more wholistic POV which I agree with quite a lot these days. It breaks down the "title" mentality into smaller responsibilities across three areas: Technical Skills, Leadership and Community Involvement. You can fairly easily isolate what your company values from employees in these three groups and measure any individuals performance inside each group to weigh them accordingly. I think it would work very well with peer-review processes as well. http://frontside.io/blog/2016/07/07/the-conjoined-triangles-of-senior-level-development.html http://frontside.io/blog/2016/07/07/the-conjoined-triangles-...