What's your definition of a "senior" developer?
-
And we watched Ninja Turtles.
Jeremy Falcon
Watched? The kiddies watched. We'd read the comics. We sneered at the kiddies who watched.
I wanna be a eunuchs developer! Pass me a bread knife!
-
webcrawler!! Don't forget the cool logo for webcrawler!
Jeremy Falcon
But they couldn't get it down to 32x32, so they were doomed.
I wanna be a eunuchs developer! Pass me a bread knife!
-
But they couldn't get it down to 32x32, so they were doomed.
I wanna be a eunuchs developer! Pass me a bread knife!
:-D
Jeremy Falcon
-
Watched? The kiddies watched. We'd read the comics. We sneered at the kiddies who watched.
I wanna be a eunuchs developer! Pass me a bread knife!
Didn't have time to read... I had video games to play.
Jeremy Falcon
-
I think my definition of a senior dev is vastly different than others. I am not so sure that a 10 year member working as a senior developer would be asking us to do his homework assignments for him.... So, what would your definition of a senior developer be?
I think it's relative to the number of years one has been practicing the craft, typically at least 7 years imho. It implies that one has enough knowledge to solve problems at most levels without handholding which apparently is not always true. :laugh:
"Go forth into the source" - Neal Morse
-
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.
-
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! -
I think it's relative to the number of years one has been practicing the craft, typically at least 7 years imho. It implies that one has enough knowledge to solve problems at most levels without handholding which apparently is not always true. :laugh:
"Go forth into the source" - Neal Morse
kmoorevs wrote:
is not always true
Unfortunately, there is so much hand holding going on it almost looks like one of the old "I'd like to teach the world to sing" Coke commercials. I find it somewhat ironic that people lose their jobs to outsourcing only to end up teaching the people that got the outsourced jobs how to perform the jobs they lost.... for free.
-
Bloody hell YOU have a cubicle!
Never underestimate the power of human stupidity RAH
-
Bloody hell YOU have a cubicle!
Never underestimate the power of human stupidity RAH
Yes, we have cubes. The Agile experiment didn't work out in our org culture; so the cubes were brought back. Actually, I have a small office, but the "senior developers" that I have worked with tend to have 6 months of food and drink in their cubicles just to let everyone know they aren't planning on retiring anytime soon.
-
I think my definition of a senior dev is vastly different than others. I am not so sure that a 10 year member working as a senior developer would be asking us to do his homework assignments for him.... So, what would your definition of a senior developer be?
As a senior developer you know when to use what and you know why something should be used. Domain knowledge helps but even if you don't have specific domain knowledge that you can acquire over the course of time. As a senior developer you know that you don't know everything and there are people better than you. You learn from your mistakes and you try to improve yourself. Keep on learning and improving your skill is very important in this industry. I have seen people with 15 years experience but you feel that they have done the same thing in all those 15 years. As technology progress new becomes old and old becomes legacy that no one should touch but as a senior developer you still poke around those legacy code. I have done few development work were all they had was a legacy code ( systems that are written in Basic and FoxPro ) and no documentation and my task was to uplift it in new technology looking at the code. You should not be afraid to understand how old technology works even though you will never write something in it. And I am still an Analyst Programmer. Should I consider myself senor developer ?
Zen and the art of software maintenance : rm -rf * Maths is like love : a simple idea but it can get complicated.
-
I think my definition of a senior dev is vastly different than others. I am not so sure that a 10 year member working as a senior developer would be asking us to do his homework assignments for him.... So, what would your definition of a senior developer be?
-
I think my definition of a senior dev is vastly different than others. I am not so sure that a 10 year member working as a senior developer would be asking us to do his homework assignments for him.... So, what would your definition of a senior developer be?
One that takes the blame for the team.
-
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?
-
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?
-
Sorry, we are getting age creep and now someone must be at least 67.
-
Yes, we have cubes. The Agile experiment didn't work out in our org culture; so the cubes were brought back. Actually, I have a small office, but the "senior developers" that I have worked with tend to have 6 months of food and drink in their cubicles just to let everyone know they aren't planning on retiring anytime soon.
LOL!! I detest Agile and started refusing Agile dev shops, saying "I'm not a team player" (apparently this is worse than not knowing how to code ... :omg: ) And even though the company who contracts me gives us lunch, I still have loads of snacks lying around. I'm not a senior developer, though, I'm more of a senior moment developer :-\
-
If you forgot why you came into work today, then you are a senior developer.
:thumbsup:
Piyush K Singh
-
He has most likely persuaded himself that he is a brilliant teacher. :-\ The levels of self-delusuion in software development is staggering... :confused:
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.
-
I think my definition of a senior dev is vastly different than others. I am not so sure that a 10 year member working as a senior developer would be asking us to do his homework assignments for him.... So, what would your definition of a senior developer be?
How 'bout one that's almost 60 and has been doing this for 40 years? ;-)