Failure rate in IT projects are reasonably high & companies are paying the price of missed deadlines, inferior quality that does not scale well, does not meet the SLAs, stability issues requiring constant rework, etc
The reason why certain software engineers get paid highly is because software skills in generally not a commodity. Software skills is an art, and the good ones are artists...
Well said Henry. Writing a software is not only an art as Henry said, but also highly complex (lots of moving parts, lots of rules, need to liaise with multi-disciplinary teams, lots of cordination & scheduling efforts, etc). One needs to have good analytical, problem solving skills, and other soft skills to thrive in the industry.
It requires technical and business expertise to devolep software, which are skills aquired through practice and investment of time and are getting paid on demand, Its not an instant or common skill which can be found in every one though they can aquire by proper training.
Wouldn't it have been easier if you just responded in the original topic, instead of starting a new one, and bringing everyone up to speed, including quoting many people from the original topic?
In this context,I want to know is there any facts or opinion which gives us the percentage of skilled force in the industry?
I do believe that it won't cross 20%.
As one of the principle states "20% of the causes effects 80% of the results"
I do believe that due to these 20 people 80 people are getting salaries,recognition(in society & in workplace),benefits(PF,onsite opportunity) which is not proportional to their skill,experience & talent.
I do want to know whether this 20% is lesser or greater.
As usual your candid,bold & honest opinions are appreciated.
Regards.
Cheers!
RSR
Originally posted by ramya narayanan:
Is it true that the percentage of skilled force is very very less even in these downtrodden economic situation?
Also I want other's opinion on how they construe a skilled force?
Regards.
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
I do believe that due to these 20 people 80 people are getting salaries,recognition(in society & in workplace),benefits(PF,onsite opportunity) which is not proportional to their skill,experience & talent.
everyone should be paid for the value they create.
For a hard working, sincere person it's difficult to see slackers getting same recognition and/or compensation. Get over it...if somebody does not rise above average his/her future is also average.
Do you think that someone with twice the experience should be paid twice the salary? Or someone with twice the number of skill sets should be paid twice the salary? ... Well, if you are a code monkey, with one or two years, then maybe yes.
Answers are about the past , abilities are about the future
A great manager will recognize the "intangibles", and there is no price limit on it.
Well, if you are a code monkey, with one or two years, then maybe yes.
Personally, I do have a very high opinion on Henry Wong. I didn't expect him to use this offensive against me.
As an ardent student of the game, I want to know what are the intangibles you mention?
Most of the programming problems can't be solved because you don't know what the exact problem is.
Defining your problem correctly leads you to the right solution.
Many years ago (over 10 years), I recommend one of my friends for a project. He is one that I would say have those "intangibles" skills.
So, what are the intangible features? I have no idea, except he gets results, even when it seems impossible.
Cheers!
RSR
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
1) There are "slackers" (which I take to mean people you consider unqualified)
2) These unqualified people are getting paid and should not be
3) The reason they get jobs is because interviewers are "searching for the answers not about the person's ability."
Oh my God!! I m a slacker too !googling something or discussin g with others.
Cheers!
RSR
Atleast in Indian scenario that's what the situation is.
I don't find interviewers checking the programming ability of the candidate or checking the candidates foundation on the technology for which they're recruited.
Bingo!Employers prefer balanced candidates, not just techies or Java gurus.
Cheers!
RSR
Most of the programming problems can't be solved because you don't know what the exact problem is.
Defining your problem correctly leads you to the right solution.
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
Do you have a specific solution for how to fix this or are you simply noting your frustration?
Originally posted by ramya narayanan:
How about having this model of interview?
Innovative Interview
Originally posted by ramya narayanan:
How about having this model of interview?
Innovative Interview
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
Originally posted by ramya narayanan:
When this sort of pair programming interview is undertaken & made as a standard for interviews, people would atleast bother about improving their practical knowledge, ability on the technology rather than vomitting what they had read.
Also this will give an idea to the employer about the ability of the guy to work in real situations.
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
Through out this post I'm talking about the former & solutions on how to find out them earlier in inverview process itself so that company can save time & costs.
I'm not worried about working with latter slackers because they can made to work through a better manager.
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Consider Paul's rocket mass heater. |