|
I think those are a decent basic set of criteria. At least you've created some kind of target.
Most companies/managers/people just have no idea.
|
|
|
|
|
I believe that 62 is when one starts reaping the benefits afforded a senior.
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
Sorry, we are getting age creep and now someone must be at least 67.
|
|
|
|
|
What a coincidence I am 67.
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
|
No, it's still 65, just base 16
|
|
|
|
|
Depends on the benefit you're after. For a "senior citizen waiver" on tuition for audited classes at my local community/technical college, 60's enough (and yes, I'm auditing classes - Circuit Analysis I last semester, Circuit Analysis II and Digital Systems I this quarter - eventually I'll be able to start building my very own personal Cylons!).
-Bob
|
|
|
|
|
Yes I know. Just joking anyway. Some items you need only be 55. For full social security it is now 67, up from what it use to be. Use to be able to retire at 59 at some places and get full benefits. Of course few in the US now get pensions and such unless you work for the Government, and most of them are broke.
|
|
|
|
|
I thought at first that this was going to be about someone else you had a bit of a homework rant at (guy with the chess problem). Now, I'd be seriously worried if the guy who posted that called himself a senior dev and was somewhat relieved to see that he doesn't but I'm intrigued as to what question inspired this post ...
I guess it would be unethical of you to tell us, though.
Or would it?
|
|
|
|
|
PeejayAdams wrote: it would be unethical
I wouldn't say it would be unethical, just immaterial. Just seeing a rash of accounts that have been open for anywhere from 4 to 15 years and proclaim themselves to be senior developers at their company and yet can't perform the simplest of tasks, like assigning values to variables or debugging their code to fix an NRE or can't fix a simple missing reference error. One person I am thinking of has very proudly proclaimed that he won't do his own basic research and runs to the forums here all the time to get people to do his research for him. One help vampire got so many people to write his code for him, he was able to get some sort of position teaching others! And, people here still write code for him.
|
|
|
|
|
NotPolitcallyCorrect wrote: One help vampire got so many people to write his code for him, he was able to get some sort of position teaching others!
That is truly terrifying.
Furthermore, it raises a question of how non-technical organisations go about recruiting IT staff when they have no-one to assess candidates from a position of knowledge. I've certainly come across a few technical illiterates who have wound up with far grander positions than senior developer on the basis of their ability to BS a boardroom. They tend to get their next job on the back of their inflated salary and job title and do rather better in life than those who actually know what they're doing.
To my mind, it's dishonest and dishonourable to live that way but to lie your way into a teaching position takes it a whole step further. How does the guy sleep at night?
|
|
|
|
|
He has most likely persuaded himself that he is a brilliant teacher.
The levels of self-delusuion in software development is staggering...
|
|
|
|
|
Yes, you're probably right about self-delusion and I may be being a bit cynical in thinking that these people are actually aware that they're clueless.
Thinking about the dozens of developers that I've worked with over the years, the cr@p ones have all had one thing in common - you can't tell them anything because they already know everything (even if they can't actually code their way out of a wet paper bag).
Conversely, all the good and great developers I've worked with have been completely open to ideas; don't get defensive when criticised and are more than happy to share their knowledge.
|
|
|
|
|
"people here still write code for him." I think that's unethical. Teach, don't proxy.
|
|
|
|
|
|
If one knows how to properly use google, then you can be classified as senior.
|
|
|
|
|
But then 'Who' defines what is proper use of Google?
|
|
|
|
|
KC@CahabaGBA wrote: But then 'Who' defines what is proper use of Google?
Chuck Norris
|
|
|
|
|
I agree! And asking the right questions..
|
|
|
|
|
If you forgot why you came into work today, then you are a senior developer.
|
|
|
|
|
LOL! What say? errr...what were we talking about? Wait, what's this plastic thing under my hands? Keyboard? who?
|
|
|
|
|
Piyush K Singh
|
|
|
|
|
As part of an article that I'm writing, I'll give you a loose definition:
Someone who is senior able to apply scientific methods and has formal methodologies for their work process, demonstrates skill in the domain, tools, and languages, would be considered a master craftsman (ie, proven track record, ability to teach others, etc.) and also treats development as an art, meaning that it requires creativity, imagination, and the ability to think outside of the box of said skills.
Marc
|
|
|
|
|
I like your loose definition . And thinking back to the OP's question...
1. It could be that the senior is assigning work because s/he is so fantastically amazing that s/he doesn't have time for these easy things that s/he is assigning.
or
2. Senior is assigning work because s/he is so NOT fantastically amazing that s/he has no clue about how to get the work done properly.
I'm assuming the OP was alluding to the fact that it was the second condition.
|
|
|
|
|
When their cubicle looks like a kitchen pantry.
|
|
|
|