Re: Who gets higher salary a Java Programmer or a C++ Programmer?
Tommy <plas@dacxsee.com> wrote:
Daniel T. wrote:
Tommy <plas@dacxsee.com> wrote:
Tom Anderson wrote:
... at the end of the day, considering the topic (who gets a
higher salary among Java, C++), one who attempts to cover the gambit
or believes the better pay will come by self-proclaiming to be a
"Software Engineer" in his resume, better have the credentials and
experience to back it up. A CE degree is nice, but it must also be
coupled with practical experience.
Agreed. A CE degree is nice but ultimately not relevant IMHO. A kid
fresh out of college simply is not going to make a good Software
Engineer, he's got too much to unlearn first. Experience is the best
teacher.
When I talking to potential hire,
a good clue that the person has promise is when he tells me he can't
live without his white board. :-)
I never use the damn things. Hate them. I do keep a pad of graph paper
on my desk at all times though. :-) When a coder tells me he likes to
keep the lights off, that tells me he believes the only thing that is
important is that which is on the screen. Big mistake IMHO.
He would be just as well calling himself a "Software Developer", or
Project Developer or Product Developer.
The former tells me he has R&D experience, design experience. The
latter tells me he has production, QA, customer relations, even
possible technical sales and support experiences.
Grant it, with today smarter tools, IDEs, etc, the many traditional
disciplines have merged. That was the intent - not only to increase
productivity, but to lower the cost of expertise requirements,
increase output without increasing staff. If a developer wants to say
he is Software Engineer because he uses these tools, even created
tools, has experience with all the current languages, he might get
hired, but not a SE pay scale. If he can put start a project from
start to finish, create functional specs, communicate with others to
fine tine it without writing a single line of code, then he/she may
deserve the pay, but then again he probably won't be looking at a
programming position. :-)
IMHO, if he thinks he can take a project from start to finish, create
functional specs, communicate with others and define completion dates
without writing a single line of code, he's a danger to the project.