23 ms·
The "traditional understanding" of getting an applicant to your job that is over qualified is that they are just trying to get a paycheck while they look for so
by ChuckMcM 9y ago
The "traditional understanding" of getting an applicant to your job that is over qualified is that they are just trying to get a paycheck while they look for something better.
I put that in quotes because yes, I've seen it also result in an age bias and as I went from one side of the equation to the other, I spent some time evaluating what was and was not important to me as an employee.
About 15 years ago I came to the conclusion that "over qualified" was never a legitimate disqualifying disposition of a candidate. Simply put, if you are applying for a job that needs less skills than you bring and are willing to take the salary that is offered, how far 'beyond' the requirements you go is irrelevant. I asked a hiring manager at Google once if they would tell a sales guy "No I don't want the Ferrari at the same price as this Mazda Miata, its more sports car than I need to get around." Even if you never expect to challenge the top end of the sports car you probably won't turn it down. Similarly with employees, if you are up front with them about what the job entails and they are ok with it, who are you to say they will be "bored" or "twiddling their thumbs all day" ?
Answer is, you aren't. Hire them and get get a discount on skilz they are offering you. Your company will be better for it.
- trhway 9y ago>"No I don't want the Ferrari at the same price as this Mazda Miata, its more sports car than I need to get around." Even if you never expect to challenge the top end of the sports car you probably won't turn it down. Ferrari comes with very high maintenance costs, well beyond what regular Miata buyer can comfortably afford. (note: age/experience wise i'm probably close to the "Ferrari" myself :)
- ChuckMcM 9y agoThat is true with the analogy. I personally haven't seen a correlation between qualification fit and maintenance challenges for employees but it sounds like enraged_camel has had different experiences. What I'm trying to tease apart are which are issues the manager causes and which are ones an over qualified employee would cause.
- madmulita 9y agoIn that case, the problem is not overqualification, the problem is that the person is high maintenance.
- jeremyt 9y agoNot if it takes 6 months to get a new developer up and running on the codebase, and then they leave just when they are getting productive.
- ChuckMcM 9y agoIn my experience, when someones applicable experience is more than what is stipulated by the job requirements, they come up to speed much faster. I hired a brilliant engineer who did the new hire on-boarding exercises we reserved a couple of weeks for in about 6 hours. I say applicable because having a PhD in Chemistry is not being "over qualified" for entry level programming. But having 10 writing code could be interpreted as having more qualification than the job merits.
- carlmr 9y agoEven if it's somewhat applicable (like coding in a different language), it's still much quicker than onboarding a college grad. Someone who knows C++ and C# can probably learn Java in a week or two, to the level where he can contribute at least as well as your moderately skilled employees.
- le-mark 9y agoThese is also the appeal of developing in a well popular langguage/framework like .net or java. The hordes of experience devs available. Sure, you may not want to use these heavy weights when your discovering your product/market, but when you've got a fit and need to hire talent, it's nothing for a 15 year java dev to come in and be productive on day one using Spring, maven, intellij, etc.
- rconti 9y agoRight, but we know there are all kinds of reasons people quit jobs quickly. The question is probably whether someone legitimately "overqualified" is any more likely than anyone else to leave in a particular timeframe.
- humanrebar 9y ago
- salqadri 9y agoNot if the person feels demotivated by the fact that the job is not taking advantage of their skills or experience. People want to feel respected and appreciated for what they bring to the table. Without that, they may lose motivation and thus be less productive than a fresh person with a strong desire to learn and grow.
- toomuchtodo 9y agoSometimes having your mortgage paid and getting to eat trumps self actualization. You pay me, I'll do what the job calls for and we're square. Motivation is a weasel word. I'm either meeting your (hopefully reasonable) performance requirements or I'm not.
- TheSpiceIsLife 9y agoThat's right. Isn't the young energetic person who is eager to learn and grow at least as likely to leave after they've learned-and-grown as a person who is more skilled and gets bored. I'm 36 now, with a mortgage, and have stayed in the job I am in now longer than any job I've had before.
- carlmr 9y agoA friend of mine pretty much only hires ex cons (ok, not for programming jobs). Because he says they're the most loyal and hard working employees he can find, and they usually don't ask for more money. You can always use other peoples prejudice to get market rate discounts.
- salqadri 9y agoYea but that is a high risk to take. Imagine you are the manager, and you have been given just one head count. Who would you choose? Would you risk your head count on an over-qualified person?
- toomuchtodo 9y agoHaving been a hiring manager previously, I will usually take the person with more experience. The odds are lower that they'll leave than someone with less experience needing more time to become senior. There is no substitute for experience. EDIT: To expound on this, as a manager, I will look out for the company, but also for you. If you have limited experience and want to climb the ladder, I will help find you a path internally and if one is unavailable (happens all the time), I will introduce you to opportunities outside the org to get you into higher roles and pay grades. Same deal if you're a senior person with "too much skill" for the role: tell me your goals, and I will help you get there. No one sticks around forever, and its unrealistic to ask people to do so. This is, in my opinion, what a good manager is. Not someone who can code well, not someone who is a technical wizard, but someone who manages away problems outside of the team while helping individual contributors maximize their potential.
- perl4ever 9y agoI think the analogy is more illuminating than you meant it to be - what if you can't afford the upkeep of the Ferrari? I mean, there are a lot of originally high end cars available for low prices due to depreciation, and people do reject them for more practical cars that cost the same.
- Clubber 9y agoSo are you saying overqualified developers have a higher maintenance cost, or are you trying to show that the original analogy isn't a complete 100% point to point analogy? If the former how so?
- perl4ever 9y agoI think that when one is called "overqualified" it's best to take it not as a criticism of what one is but of how one is marketing oneself. It's hard to humble oneself, but it's necessary to face the fact that you can't have it both ways - if you really want/need a job that doesn't require your education and experience, then you can't brag about your education and experience that is irrelevant. Pretending this is a matter of honesty, as people sometimes do, is a way to avoid admitting you can't control your ego.
- Retra 9y agoYes, but that assumes you're not competing with anybody. If you are, then why shouldn't you put your incidental "extra-curricular" credentials up front?
- SystemOut 9y agoHow did you get to bragging about one's education/experience? Or that someone needs to control their ego?
- Clubber 9y agoA couple of things: 1. I don't see how that applies to the analogy of higher maintenance costs. >if you really want/need a job that doesn't require your education and experience, then you can't brag about your education and experience that is irrelevant. 2. That is a double edge sword. If one removes expertise to pretend to be junior, then they are vulnerable to a junior who inflates their resume to appear more competent. 3. Also, putting your past experience isn't bragging, it's, as you said, honesty. It's good business to (all other things being equal) hire the best person you can find at the price you can afford. To do anything otherwise is nonsensical. I can't think of a good business reason not to. Having said all of that, I'm so glad I haven't had to use a recruiter in nearly 20 years. It sounds like a cluster out there.
- Buttons840 9y agoIt seems like many employers are quite worried about hiring someone who is under qualified, even though they can legally fire them for any (for certain values of any) or no reason where I live. Given that, it doesn't seem like the worse problem in the world to hire someone who is over qualified, and if they get real unhappy, they give a professional 2-weeks notice and then leave. I think we're all probably ignoring the real reason this happens though, those hiring are intimidated by the over qualified candidate. "A's hire A's and B's hire C's" as they say.
- enraged_camel 9y agoNah. The problem with overqualified people is that they will get bored very quickly and either underperform or leave. They can also cause a lot of friction because their higher level of knowledge and experience can make them refuse to follow established processes and procedures, even when there are very good contextual and historical reasons for why those processes and procedures exist at that particular organization. This can cause a lot of resentment among their coworkers. Personally, I have never worked with an overqualified person who didn't quickly develop what is commonly referred to as an "attitude problem". That's of course just my own experience.
- ChuckMcM 9y agoCan you say a bit more, how did the "attitude" manifest itself? And was it something the manager was unable to see? I ask because I would like to understand the dynamic a bit better. How might you address an 'attitude' problem with one of your co-workers regardless of how the attitude originated?
- enraged_camel 9y agoMostly arrogance that stemmed from the belief (unfounded or otherwise) that they knew more than others and therefore can refuse to do certain (usually unpleasant) tasks or order people around. For example we had an analyst join the business intelligence team recently, and unlike everyone else on the team she has a masters in finance as well as many many years of experience. She refuses to run financial forecast reports for the executive team because she thinks such tasks are below her, and that others should run them instead. Really nice girl otherwise, but just terrible to work with.
- KGIII 9y agoThe conversation would go a bit like this: "Run the reports." "No." "This is your verbal warning. The next step is a written warning. Run the reports." "No." "I am going to my office to write a written warning, of which you can accumulate two." Et cetera...
- lr4444lr 9y agoIf the Ferrari could any day start up and tell you that it would drive away if you could not pay the price difference down the line and leave you with no car because it found someone else who would pay market value, I think you might in fact think twice about buying it at discount.
- pan69 9y agoAll cars do this, not just Ferrari's. An increase in salary would be the no. 1 reason people change jobs. Instead, while you have the Ferrari, make use of it.
- DINKDINK 9y ago>The "traditional understanding" of getting an applicant to your job that is over qualified is that they are just trying to get a paycheck while they look for something better. Is the solution here to bias the "overqualified" candidate's compensation in equity rather than salary? If the company thinks that salary x is too low and may tempt the person to leave, put the employees skin in the game to stay with more equity. This seems like a potential solution.
- jjjensen90 9y agoOverqualified candidates are probably more likely to see that in a vast, vast majority of outcomes equity is worthless and never worth trading for cold, hard cash :)
- firebird84 9y agoIf it's publicly tradable equity in a stable company it's worth SOMETHING, but only as much you as a hypothetical buy and hold investor would give it over the cliff period. It obviously also comes with some risk so I'd give a public equity offer with a future vesting date a considerable discount vs cash now.
- neves 9y ago> The "traditional understanding" of getting an applicant to your job that is over qualified is that they are just trying to get a paycheck while they look for something better. With the current lack of bonds between employer and employee, you must consider that all your employees are in this condition.
- kgwgk 9y agoThat's the point: the over qualified are more likely to find something better. [Edit: that's the employer's logic. Right now I'm on the wrong side of that equation, but I can understand their concern. Even if it's true that you really want the job and not that "better" job that might not even exist or you may not really consider "better".]
- itsdrewmiller 9y agoBut they don’t. https://hbr.org/2010/12/the-myth-of-the-overqualified-worker https://hbr.org/2010/12/the-myth-of-the-overqualified-worker
- icebraining 9y agoYou don't see the huge selection bias in that study? They're interviewing people that were hired despite the discrimination that already exists. It's like trying to see if alcohol leads to more crashes by only interviewing people in intact cars. It may be that overqualified workers don't in fact leave sooner - or it may be that the hiring manager correctly identified those who would and wouldn't, and only hired the latter. By studying only the people already hired, it's impossible to tell.
- phaemon 9y agoEdit: original response was too harsh. I'm just grumpy I guess. The study was done properly. Have a read of: http://today.uconn.edu/2010/08/over-qualified-not-really/ http://today.uconn.edu/2010/08/over-qualified-not-really/ which provides better detail.
- StephenConnell 9y agoIt could be a deal, it could be a steal, or it could be too good to be true. In either case it's a red flag that should be carefuly evaluated.
- gozur88 9y ago>About 15 years ago I came to the conclusion that "over qualified" was never a legitimate disqualifying disposition of a candidate. Which is about the same time I decided the opposite, having been burned a couple times. You're neglecting the amount of time and effort other people in the group put in to make a new employee productive. Where I work it takes an absolute minimum of about three months to understand how all the moving pieces of the business data flow fit together, and maybe another three before the new person is truly independent. And during that time other people in the group are spending time on the new guy instead of doing work themselves. If I hire someone and then he quits in six months, all that effort is wasted.
- marktangotango 9y agoThis "time on the new guy" ought to only happen once, document the on boarding process. Personally I've never seen a 15 or 20 year guy (yes it's always men at this tenure) take more than a couple of weeks to get productive, 6 months to mastery. That's been my experience at least.
- gxs 9y agoYour experience is probably atypical. Documentation is one of those concepts that can be the answer to any problem, but seldom is. I've yet to work at an organization where everything is documented, the documentation is up to date, and the documentation is of high quality. There are always gaps somewhere in the documentation and in the end it does take time to ramp people up. Now, if you work on project based work and it's always on something different, that's a different story.
- le-mark 9y agoWell yeah, the gp specifically said document the on boarding process. A high level architecture overview is all the system documentation required. Personally I ignore all that crap anyway, the truth is in the code and deployments. I don't know how many times I've had to tell the senior, long time employees how their system works.
- 9y ago
- Waterluvian 9y agoSounds like the interviewee's job is to convince the interviewer that it's not just a temp job. Explain your rationale for what appears to be an illogical career move.
- phkahler 9y ago>> The "traditional understanding" of getting an applicant to your job that is over qualified is that they are just trying to get a paycheck while they look for something better. I'm getting to the age where I wonder about these kinds of things. And yet I've interviewed older highly qualified people and thought exactly that. I will use this discussion as a reference point and adjust my attitude. I could be in that guys position any day/year now, what will I want? I'm beyond the point of caring about certain things that seem to matter to younger people who think they're going to change the world. I just want to do solid work and get paid my rate. It makes sense that those I interview want the same.
- pfarnsworth 9y agoI'm a big fan of yours ChuckMcM, but your analogy is wrong, but very pertinent. You would not want to buy a Ferrari at the same price as a Miata, because if you want to change the oil, it will cost $1000, instead of $50. You get 8 mpg, instead of 30 mpg. If you don't drive the car properly, you will wear down the clutch and it will cost you $30,000 to replace. Initially, it will seem like a great deal to get a Ferrari for the cheap price, but if you actually intend to use it, there are very practical reasons why it will cause a lot more problems simply having it, than having a Miata. If you can't afford to use the Ferrari properly, it will end up costing you more. In the same vein, hiring an overqualified candidate WILL cost you more money and opportunity because they will leave quickly, and you could have spent the time training a more properly qualified candidate. I've been in the business 25+ years and I've seen this mistake time and time again. Maybe soon I'll be the one who is overqualified as well, who knows, but it is a legitimate reason to not hire someone.
- ChuckMcM 9y agoThe discussion of the analogy has been very interesting! I'm not sure I'm convinced that overqualified candidates either higher maintenance or more likely to quit. That hasn't been been my experience and I know my experience is limited, the HBR article cited however seems to back up my personal experience for what that is worth. The variables around why someone works somewhere and whether or not they quit has, again in my experience, been more very strongly correlated with how well they like their job. And it is the factors that they "like" or "dislike" about there job rarely relate to how experienced they are or are not, and are much more likely to be based on whether or not they feel they are respected for their work, if they like or dislike their peers, like or dislike the day to day of their job, and like or dislike their office configuration (environment). That is the basis for my belief if "over qualified" is the single factor left over then it doesn't seem to correlate how successful they will be in the job. All that said, and specifically addressing the analogy, the things that I find make for 'high maintenance' employees are an inability to hear constructive criticism (so poor self awareness), a lack of curiosity (so unable to see the questions that need to be asked), and a lack of respect for their work (so they aren't really trying to improve at all). Does that make them Ferraris or Jaguars ? :-) Sometimes the more expensive car (like the Model S) has a lower total cost of ownership, sometimes it doesn't. But it has been really interesting thinking about the "maintenance" cost of employees from that perspective.
- hindsightbias 9y agoFor older applicants, they've probably have only had one or a couple of jobs - they're the last people anyone should worry about chasing changing jobs every 12 months for higher pay. Most 40- or 50-somethings in tech would be happy just having medical and getting to retirement w/o having to sell their house or raid their 401K.
- stuaxo 9y agoAs someone a year off 40 doing contracting, that sounds incredibly depressing. It also doesn't fit other software devs I know who are similarly old.
- quickben 9y agoDepends on what you are stuck in. In Toronto, I've worked with 60+ years olds getting paid six figures as 'c++ developer'. I've also worked with 40 year olds hired as 'frontend engineers' unable to get more than $35k. So yea, maybe your statement is true if you are only after job, but if you treat this as a career, there are no limit to opportunities.
- deleted 9y ago[deleted]
- ci5er 9y agoHuh? Might I suggest that you might not know enough 40- to 50-somethings to sling around that word "most"? Sure, as an old fart, I don't like the new culture of the young snots that change jobs every 18 months before they've started to add value, or even really learned anything, but that's about as much time as you'd get from an overqualified person looking to bide his time before he moved on anyway.
- muzani 9y agoI've heard people refer to them as performance drugs, good for short term gain, but possible side effects. They can challenge authority. They can get work done twice as fast, and you'd get a good deal if they show up only 80% of the time. The star players can also be divas, challenge bosses. Some cultures have more difficulty dealing with it and sometimes it comes with drama. They tend to be a little stubborn. I met one senior with almost 10 years experience who refused to use source control or log into Trello. Project management for that project fell apart because the key members were not on it.
- marcus_holmes 9y agoThere's stubborn and stubborn. Are they being stubborn because they've seen this before and know it leads to a bad place? (probably not when they're objecting to Git or Trello) Or are they being stubborn because they don't want to learn new things? (which sounds more the case here) If the second one, then that's a problem. But it's got nothing to do with their age or experience. I've seen total newbie coders unwilling to learn Git because they don't think they need it (or it scares them, or whatever). It's easier to justify the mindset with age and experience, but it's not caused by age or experience. If, however, it's the first kind of stubborn, then that's gold. That's what you need. That's the thing that stops teams from repeating the same mistakes over again. Instead of dismissing it all as "stubborn", it might be worth checking the rationale behind the reluctance.
- muzani 9y agoYeah, that situation was a, "We've been perfectly fine managing bigger projects with Excel and emails for years." But that's an extreme case for example. Much of the time it's in a gray area. Is this guy refusing to use JS because it's a buggy language or because it threatens his 7 years of PHP experience? Is React Native really that bad or does it just threaten this guy's native iOS experience? Is it some expert instinct to put semicolons on JS code or just FUD? The true experts usually develop a kind of instinct for danger, so you probably want to trust them when it's FUD. It goes a lot deeper than just seeing this person have X years of experience. You have to filter them for quality years of experience. Is it a bad sign that this guy is willing to take a 30% pay cut from his qualifications? After all, the best people want to be challenged. Maybe he wants less workload so he can focus on a side project. Or it could just be that he has no intent of actually improving, just wanting a good enough job to pay the bills.
- rdtsc 9y ago> who are you to say they will be "bored" or "twiddling their thumbs all day" ? But that's not the real reason. The reason is they are afraid because the experienced person can see through bullshit better. They are harder to fool and brainwash to work for free. With stuff like "There won't be a paycheck next month, but don't worry we are turning corner, once we exit you'll all drive Ferraris!", "We are changing the world, just need to finalize this feature by next week, so let's all work a little harder (and by all I mean you all)". Someone with experience will say something "Thanks but no thanks, I've heard this before" a new college graduate will say "Yay! Let's do it, I'll impress everyone with how little sleep I can get each night". And I am not being too hyperbolic here. I've heard from owners before confessing that hey love hiring college grads because they can drive them hard, they are full of enthusiasm and are not "tainted" by other corporations. Another friend from another startup, confessed that they like those take-home interview problems. Stuff like "Implement a distributed database over the weekend and show us the code on Monday during the interview". The reason is because they can get the really desperate and dedicated people willing to invest that much time into projects. As when crunch time comes, they'll need those "skills".
- on_and_off 9y agoInteresting, as a candidate I prefer the take home project because then I don't have to cram largely irrelevant knowledge.
- intended 9y agoWell apparently you have expendable weekends :)
- pc86 9y agoSo do you - it's just that your priorities are different. Which is totally fine, but let's not pretend there is a class of people who cannot possibly take 2-3 hours out of the next 48 to do something. With rare exception, they're just making the (completely reasonable, completely okay) choice not to. I am obviously only referring to programmers, knowledge workers etc.
- Iv 9y agoI clicked on the comment section assuming I misunderstood something. No. Apparently "over-qualified" is a thing in Silicon Valley. Wow. I am torn between thinking this is just bullshit to not say to someone "you are too old" or believing that people really think that additional skills are a bad thing. Just wow.
- brooklyn_ashey 9y ago>I clicked on the comment section assuming I misunderstood something. No. Apparently "over-qualified" is a thing in Silicon Valley. Wow. Yes. And it isn't just Silicon Valley. I started getting "you are overqualified" in my former profession at age 35, when I was at the top of my former field. Many of my similarly experienced colleagues got the same treatment. So I switched to software hearing that qualified developers were in short supply only to find that this same lame "overqualified" argument was being used for over 35 year olds I came to know in my new profession. There doesn't seem to be a place for anyone who isn't already securely positioned at 35 in any profession these days. Career changes after 30 are becoming impossible in many fields.
- dpweb 9y agoAge discrimination is a crime in the US. We don’t tell bank robbers, its not a nice thing to rob banks, and in this industry we’re all part of the bank robbing problem. We need to look at our attitudes in calling out bank robbing as a bad thing. Crimes have legal consequences, more than a morality lesson is needed.
- turk184 9y agoLots of things are crimes in the US, but if you're part of the "special" class, you will not be prosecuted for them, e.g. Hillary Clinton. As far as ageism goes, companies know exactly how to get away with it without undue legal exposure. Same as it ever was. Note to all developers: YOU WILL GET OLD! Your mental faculties and physical abilities will fail you. Plan accordingly. You have a very fixed set of time to make the bulk of your income in life and there is a very steep tail off at the end unless you are extremely lucky, which most people who are unprepared will not be. You need to consider a backup career, something you can do if "knowledge work" can't happen for you for whatever reason. I'm sure plenty of developers can work on into their 60s, but it's simply not realistic. Figure age 50-55 and out, or perhaps slide into a non-development role by leveraging your contacts and reputation. Otherwise, find the $10-15/hr. part-time job of your choice. That's how it is.
- AnimalMuppet 9y agoMy experience is a bit different. The real problem with me being overqualified is that I want to be paid for the qualifications I bring, and they don't want to pay that much. They aren't afraid that I'll move on soon. They just have sticker shock. Now, if I take their low-ball offer, if they pay me as if I had 5 years of experience when I really have 30 and for whatever reason I have to take that job, then yes, I'm out of there as soon as I find someone who will pay me what I'm worth. I like the work, but I do this to make money, not just for entertainment. And why am I worth more money than someone with 5 years of experience? I don't even work as hard as those people; why am I worth more? Because I get more done, and it's done better when I do it. I don't write the bugs those people write, so I (or somebody else) doesn't have to spend the time finding and fixing them. I don't design the bad architectures that they design. And so on.
- shostack 9y agoYour experience might be worth that much to a company who needs it, but if they are hiring for a junior role (and I mean they truly just need someone junior, not playing games), they may not value what that role will be working on enough to justify paying for your extra experience. Nothing wrong with that... It just likely isn't a good fit.
- humanrebar 9y ago> ...just need someone junior... What does this mean? It sounds like expectations around pay and responsibility. If someone says, "Yes, I'll take your marching orders for 30k per year," why not hire them and let them do that? You might have something with more responsibility open up in the next year or so and have an immediate (and usually harder to find) candidate for that job.
- shostack 9y agoMy point is that some roles may not have much upward mobility, or they may want to bring in someone with less experience and train them up (a good thing). Someone with a mountain of experience coming in has to work against the suspicion that they are taking the role for the wrong reasons, namely that they will bounce as soon as they find something more in line with their actual experience. It goes beyond expectations of pay and responsibility. If you take someone with a ton of experience who says they will do the job for $30k/year, their growth expectations are quite likely different than that of a junior person. As such, there's a greater likelihood they will leave sooner if they find something more senior. And the hard part of this is, they might genuinely be interested in the role. But enough managers get burned by taking in someone with too much experience for a lower level role that leave in under a year, and they tend to avoid that type of candidate.
- jules 9y ago> I asked a hiring manager at Google once if they would tell a sales guy "No I don't want the Ferrari at the same price as this Mazda Miata, its more sports car than I need to get around." A car doesn't leave after 2 months, but you would worry about it being a stolen car, wouldn't you?
- carlmr 9y agoDepends on your city. In my city there are plenty of high end cars parked on the street, but at the same time I couldn't afford the cost to maintain a Ferrari, and the fuel consumption isn't light either.
- walshemj 9y agoActually you can run a classic car 11 or some older feraris) on a relatively low budget and you have the massive deprecation you do with a new car.
- yellowapple 9y ago"No I don't want the Ferrari at the same price as this Mazda Miata, its more sports car than I need to get around." Personally, I'd be worried that the Ferrari would still end up having a higher TCO due to the elevated maintenance and insurance costs.
- ScottBurson 9y agoInclined to agree. I think a resistance to hiring "overqualified" people probably reflects a lack of imagination. There may be lots of ways this person could make your team better, and you haven't even stopped to think about what those could be. I suppose people who are at risk of being considered overqualified should learn to make exactly that kind of case for themselves.
- alfredallan 9y agoMinor point: a rational person who can afford only a Mazda Miata oughtn't take a Ferrari for the same price for the simple reason they can ill afford it's running costs (fuel, maintenance, etc.).
- walshemj 9y agoIs not every one "trying to get a paycheck while they look for something better"
- bradknowles 9y agoWith respect, when it comes to vehicles, I think I would actually refuse the Ferrari. It’s too expensive to get insurance or to have work done on it. Parking it at my house makes it an attractive nuisance and increases the likelihood that my home may be burglarized. Most importantly, I am old enough to know that my personality is such that I would be strongly tempted to drive that vehicle too fast and in an unsafe manner. There’s a whole host of things wrong with this analogy.