5 ms·
I Am Unhireable
- arvinsim 7y agoI have learned to become wary of companies asking for passion. More often than not, it is usually a buzzword exploited by some companies to make you do more work for less pay.
- CyberFonic 7y agoYup! Passionate, inexperienced programmers are more impressive. They will write 10,000 lines of complicated code using a dozen frameworks and libraries. The experienced old timer will get the same done with 2000-3000 lines and only 1-2 libraries. A further problem is that the impressive code becomes difficult to debug and extend as the requirements evolve. And of course with 2-3 years at a job, the original developer has long skipped to another job, leaving another junior developer befuddled with the "legacy".
- joker3 7y agoHighly relevant: https://news.ycombinator.com/item?id=19962936 https://news.ycombinator.com/item?id=19962936
- pvaldes 7y agoIs a clear red flag to trick the candidate into thinking that the work is more relevant that it really is, and must be put in the same level as a love relationship. Emotional blackmail starts soon. Nobody asks for a passionate butcher, a passionate window cleaner or a passionate secretary on the other hand.
- solarkraft 7y agoI'm not a fan of click bait titles. You're very hireable.
- HelloNurse 7y agoEven better, hireable in the right workplaces. Effortlessly driving away a certain wide class of potential employers is great.
- Rainymood 7y agoNo one is, but the matter of fact is that you still clicked. We are fickle animals.
- solarkraft 7y agoThis is true. Had I been warned I wouldn't have clicked. I try to do that for others (althogh this was arguably a bad attempt, since it doesn't answer what the article says).
- marcodave 7y agoIMHO it all boils down to "unhireable... where?". Of course you're hireable, there are plenty of places for people in their 40s with plenty of experience. There is a bias of course in Hacker News towards young fast&furious companies in Silicon Valley where it appears that if you're not a ninja bro coder you're out, but it's just a fraction of the cake.
- L_226 7y agoIn my experience (granted; anecdotal, limited, etc.) people who enter a job that is mostly coding (job title notwithstanding) and who come from an academic background often tend to write seriously unmaintanable, borderline illegible code. I think this is because they are not used to having other people read and work with their code, especially if they have just graduated and never worked in industry. This is potentially justifiable in an academic setting where stream-of-consciousness type programming is acceptable for a barebones proof of concept, but attempting to work with 1000+ LOC functions with non-descriptive variable names etc. is not only not acceptable in modern software, it is ungracious to your coworkers. Unfortunately this can sometimes be coupled with a good dose of hubris ("I have a PhD and you don't!"), and efforts to provide constructive criticism are often met with anger/apathy/belittling/ignorance. Their pride, which may be well be deserved within the narrow field of their academic work, unfortunately doesn't mean that they automatically know how to write maintainable software and also potentially hinders them learning how to. This is perhaps why there is a trend to dismiss "academic candidates". That being said, some of the best software engineers I have ever worked with hold doctorates - and people worth working with will usually admit their limitations anyway. This is not limited to those with an academic background in general, as accepting our faults is the first step in adressing them.
- perl4ever 7y agoI'm prejudiced against people with a scientific background mainly because of the code I've seen written by astronomers. When I was in high school, I was interested in VSOP87, and found the sample code to be in obfuscated Fortran, and I also remember how Sky & Telescope insisted in publishing all programs as stone-age style BASIC, with line numbers, on the basis that anything more readable and structured would not be compatible with everyone's computers.
- kls 7y agoTwo of the best programmers I have worked with, and who I credit myself to becoming a "real" programmer, where PHD's, one was a tenured professor at MIT who founded a computer learning start-up. I learned the elegance of simple black-boxed code from both of them and they both seemed to have a strong focus on that. I was young and a hot shot programmer at the time and they where both older patient men, who saw raw unfocused talent in me. I am a better person for having learned under them and for them having endured me, but I would absolutely place them hands down as two of the best and most productive programmers I have ever worked with. I am thankful I did not have hiring responsibilities in my 20's, as I would have been one of "those" pricks and would have a lot of regrets for the way I treated people now.
- nickthemagicman 7y agoAll these criteria make sense except for the PhD. That seems like one of those humble brags.
- jarofgreen 7y agoI've heard companies express wariness of people with PHD's. It's a stupid reason to reject someone - as are all the points he makes - but yeah, I've heard that.
- zaphod12 7y agoI am personally wary of folks with PhDs. It's certainly not a reason to reject an application, but I don't really consider a positive, either (for a general software engineer - if I need a systems engineer and you've been doing systems engineering research, then different story). It's just a completely different way of thinking about problems and I have had trouble with folks who weren't able to change their mode of thinking. If I was hiring a researcher, I wouldn't consider 5 years of coding at tiny startups to be an advantage. It's really the same thing - demonstrated skills at a related, but somewhat different enterprise.