3 ms·
I think this is a key insight; experience demands compensation. The question I have is; when is the experience really necessary? I took a job once, I was recom
by marktangotango 11y ago
I think this is a key insight; experience demands compensation. The question I have is; when is the experience really necessary? I took a job once, I was recommended by a former colleague to the dev maanger of a fast growing company. I was one of the best developers this person had ever known (I found out later this is how I was sold). I even flubbed a couple of the technical interview questions, but was still hired at my required salary.
My work at this company consisted of maintaining an application written in framework X (where X had long since fallen out of favor). The idea was to rewrite, but due to business requirements this never happened. Had they done the rewrite, my salary and experience would have been justified, but doing maintenance on an old app? They could've gotten a green or junior dev to do that for half the price.
- matwood 11y agoWhat lazyjones was alluding to is that time != experience. A 25 year dev veteran who has just done the same code over and over has very little experience. I've seen this while interviewing people. Person has 5 years experience on their resume, but it turns out they really have about 3 mos. experience. They got the job, learned it in about 3 mos. and just repeated it over over and with minor tweaks. Part of the blame is the company for no growth path and part is on the employee. To the original point. Where I work now only 2 of the 7 devs are under 30, and they will both be 30 soon. Having this level of experience lets us build things very quickly. It also lets the business side trust the dev team to usually make the right decisions on the fly.
- pluma 11y agoAs they[who?] say: Sometimes "20 years of experience" turns out to be just "one year of experience, 20 times over".
- deleted 11y ago[deleted]