What does a "Senior" software developer reflect?
-
It that the age, married, having kids, knowledge base, handing the title as pendant, a combination of all or something else. I'm getting frustrated now a days not only in the office but here in CP too.
Nothing, absolutely nothing. The title has been so over used it is meaningless. I have seen people with less than 2 years experience claim senior developer while the same title may be applied to someone with 20 years experience. As for your frustration you can always... no I'm not going there!
Never underestimate the power of human stupidity RAH
-
It that the age, married, having kids, knowledge base, handing the title as pendant, a combination of all or something else. I'm getting frustrated now a days not only in the office but here in CP too.
They should have the ability Meow like a cat, bark like a dog, fly like ninja ... :) On a serious note, I expect he/she should have the ability to mentor, know the subject matter, explain the pros and cons of doing something... I'm junior with few years of experience. I'm met few exceptionally(relative to my knowledge) good as well as dumbest(they might be smart on their own way) seniors. On the CP side, it reflects the same way as of the above. That what I observed so far...
-
They should have the ability Meow like a cat, bark like a dog, fly like ninja ... :) On a serious note, I expect he/she should have the ability to mentor, know the subject matter, explain the pros and cons of doing something... I'm junior with few years of experience. I'm met few exceptionally(relative to my knowledge) good as well as dumbest(they might be smart on their own way) seniors. On the CP side, it reflects the same way as of the above. That what I observed so far...
Vander Wunderbar wrote:
have the ability to mentor, know the subject matter, explain the pros and cons of doing something...
yes ... often being presented with n-ways of doing something, knowing why/why-not for some of them should fall into 'senior' titles, not just because 'its cool/because we can', but "it fits with the business, now and in the future" :-)
-
Vander Wunderbar wrote:
have the ability to mentor, know the subject matter, explain the pros and cons of doing something...
yes ... often being presented with n-ways of doing something, knowing why/why-not for some of them should fall into 'senior' titles, not just because 'its cool/because we can', but "it fits with the business, now and in the future" :-)
Blinding light from coke bottle glasses.
-
It that the age, married, having kids, knowledge base, handing the title as pendant, a combination of all or something else. I'm getting frustrated now a days not only in the office but here in CP too.
You question requirements and not just do as spec says You know how to investigate application issue. You know problem is not always code You have few languages/tools under your belt You waste some time learning some tool/language that is of no immediate use to you You don't post in Q/A asking for "give me code"
Zen and the art of software maintenance : rm -rf * Maths is like love : a simple idea but it can get complicated.
-
It that the age, married, having kids, knowledge base, handing the title as pendant, a combination of all or something else. I'm getting frustrated now a days not only in the office but here in CP too.
Absolutely nothing IMO. I know a few "Senior" developers who write null-checks even for non-nullable types. And upon asking they claim that to be a safe practice. :doh:
You have just been Sharapova'd.
-
It that the age, married, having kids, knowledge base, handing the title as pendant, a combination of all or something else. I'm getting frustrated now a days not only in the office but here in CP too.
It's definitely not knowledge base where I work. I know a few "Senior" developers who write null checks even for non-nullable types. And upon asking they claim that to be a safe practice. :doh:
You have just been Sharapova'd.
-
You question requirements and not just do as spec says You know how to investigate application issue. You know problem is not always code You have few languages/tools under your belt You waste some time learning some tool/language that is of no immediate use to you You don't post in Q/A asking for "give me code"
Zen and the art of software maintenance : rm -rf * Maths is like love : a simple idea but it can get complicated.
virang_21 wrote:
You don't post in Q/A asking for "give me code"
Best response ever :laugh:
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
It that the age, married, having kids, knowledge base, handing the title as pendant, a combination of all or something else. I'm getting frustrated now a days not only in the office but here in CP too.
-
Nothing, absolutely nothing. The title has been so over used it is meaningless. I have seen people with less than 2 years experience claim senior developer while the same title may be applied to someone with 20 years experience. As for your frustration you can always... no I'm not going there!
Never underestimate the power of human stupidity RAH
It's like being a "manager" in a shoe shop. I may not last forever but the mess I leave behind certainly will.
-
It that the age, married, having kids, knowledge base, handing the title as pendant, a combination of all or something else. I'm getting frustrated now a days not only in the office but here in CP too.
I have been hired at two different jobs as the sole SW developer on a team of engineers. I was therefore, by default, "the Senior SW Dev" (and referred to myself as such on a few unguarded occasions). Of course, I was also the Junior SW Dev too (but let's not go there).
-
Nothing, absolutely nothing. The title has been so over used it is meaningless. I have seen people with less than 2 years experience claim senior developer while the same title may be applied to someone with 20 years experience. As for your frustration you can always... no I'm not going there!
Never underestimate the power of human stupidity RAH
I have been hired at two different jobs as the sole SW developer on a team of engineers. I was therefore, by default, "the Senior SW Dev" (and referred to myself as such on a few unguarded occasions). Of course, I was also the Junior SW Dev too (but let's not go there).
-
It that the age, married, having kids, knowledge base, handing the title as pendant, a combination of all or something else. I'm getting frustrated now a days not only in the office but here in CP too.
-
It that the age, married, having kids, knowledge base, handing the title as pendant, a combination of all or something else. I'm getting frustrated now a days not only in the office but here in CP too.
Sumuj John wrote:
or something else
What you can get in terms of a salary or hourly consulting rate. As to what "senior" means to me, it's a few things: 1. the ability to quickly understand the business model 2. review processes and suggest process changes, separate from any software solution, but also including recommendations on how to roll out a new software solution with minimal friction 3. deliver working software on time and in budget, and if not, determine this early and suggest options. and so forth. Senior reflects the ability to problem solve, not just code against a spec that's so well defined for junior person that a senior person could have just written the code. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
-
Sumuj John wrote:
or something else
What you can get in terms of a salary or hourly consulting rate. As to what "senior" means to me, it's a few things: 1. the ability to quickly understand the business model 2. review processes and suggest process changes, separate from any software solution, but also including recommendations on how to roll out a new software solution with minimal friction 3. deliver working software on time and in budget, and if not, determine this early and suggest options. and so forth. Senior reflects the ability to problem solve, not just code against a spec that's so well defined for junior person that a senior person could have just written the code. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Thanks for your input.
-
You question requirements and not just do as spec says You know how to investigate application issue. You know problem is not always code You have few languages/tools under your belt You waste some time learning some tool/language that is of no immediate use to you You don't post in Q/A asking for "give me code"
Zen and the art of software maintenance : rm -rf * Maths is like love : a simple idea but it can get complicated.
You forgot "plz, plz"