4 ms·
> “There’s no evidence of any way, shape, or form that there’s a shortage in the conventional sense,” says Hal Salzman, a professor of planning and public polic
by philwelch 12y ago
> “There’s no evidence of any way, shape, or form that there’s a shortage in the conventional sense,” says Hal Salzman, a professor of planning and public policy at Rutgers University. “They may not be able to find them at the price they want. But I’m not sure that qualifies as a shortage, any more than my not being able to find a half-priced TV.”
I'm not sure how many developers Hal Salzman has tried to hire, but I find a lot more of them are weeded out at the "seeing if they can code their way out of a wet paper bag" stage than at the "salary negotiation" stage.
- Iftheshoefits 12y agoGiven the ridiculous technical and interview "requirements" that have been part of tech for the last several years I'm inclined to have as much sympathy for your statement as I do for companies complaining about tech worker shortage. Companies want ridiculous breadth of expertise (the ubiquitous "alphabet soup" listing of technologies), graduate level understanding of often irrelevant and unrelated algorithms and data structures, and a host of other absurdities for things like putting together a damn online shopping cart or, worse, a to-do list.
- ef4 12y agoMost people can't FizzBuzz. That's not ridiculous breadth of expertise. My basic filter question was always this: in any language you know, write a function that reverses a string. No tricks, no gotchas. Any reasonable solution will be discussed briefly and then we'll move on to discuss other things. But a shocking fraction of people -- even ones with CS degrees from fancy schools -- would spend 30 minutes stuck trying to write that function. That's what I think of when I hear "can't code their way out of a wet paper bag".
- nradov 12y agoWell what did you expect? CS education is usually mostly theoretical and not about practical code construction. Would you interview a Physics graduate and then complain that she didn't know how to design a bridge? In the early days of computing IBM hired candidates with the right aptitude but zero programming skills and then trained them. It Worked out fine.
- philwelch 12y agoWriting code to reverse a string is more like asking a Physics graduate to calculate how long it takes an object to fall 20 meters once it's dropped. In the year 2014 there's no excuse for having "zero programming skills" if you're looking for a job programming computers. We all have computers, it's not like you can't practice on your own time before expecting someone to pay you for it.
- nradov 12y agoMy point was that there is little correlation between practical code construction skills and possessing a CS degree from a fancy school. If that's what you're looking at then you're focusing on the wrong market signal. And we do have existence proofs that businesses can succeed by hiring candidates with the right aptitude but no programming skills and then training them. For example see IBM a few decades ago or Zoho today. If you don't want to do that then you have no right to complain about the market supply of skilled developers.
- philwelch 12y agoDo you think hash tables and linked lists are "irrelevant" and "unrelated"? Have you ever tried to hire developers?
- Iftheshoefits 12y ago"Irrelevant and unrelated" to what? They can be, in certain circumstances. I'm not arguing that there are no people trying to get developer jobs who have no business doing it, or that it's always inappropriate to ask algorithms or data structures questions. I'm arguing that there is an overemphasis on trivialities, minutiae, and irrelevant details.
- philwelch 12y agoAnd that's irrelevant to my point, which is that before you can even get to trivialities and minutiae, the candidate has to be able to code their way out of a wet paper bag, and a surprising number of them can't.
- Iftheshoefits 12y agoThat "a surprising number of them can't [code their way out of a paper bag]" does not imply there is a shortage of tech workers, nor does it reveal anything particularly interesting about what you consider a "wet paper bag" to be. What is interesting is that based on your prior comment you believe certain things are universally useful and pertinent in a programming job, which is contentious and unsubstantiated at best. And that was rather my point.
- philwelch 12y agoI think the ability to write code is universally useful and pertinent in a programming job. A shocking number of people fail FizzBuzz. That's what I mean by "wet paper bag".
- deleted 12y ago[deleted]
- douche 12y agoIt's really startling (as a mostly self-taught software engineer, with a bachelor's in history and a minor in Computer Science) how few people with computer science degrees are actually capable to code anything that would compile and run correctly. I've interviewed software engineering applicants that couldn't figure out how to implement a recursive fibonacci number generator... And regretfully, we hired one of them, and in two years, he has progressed so little in skill that I've reached the point of just trying to shunt him into work that doesn't matter, since experience has shown that he takes weeks to produce broken, badly performant code, that I can fix/implement from scratch in a couple of hours and a handful of google searches.
- philwelch 12y agoAnd even that is a level of quality below what some more demanding employers will ask for. In my experience interviewing, if you implement a recursive fibonacci number generator, you better memoize it because the recursive fibonacci by itself is one of the worst algorithms. I favor the iterative (and also, that question is such a cliche I haven't ever actually seen it seriously asked).
- douche 12y agoAnd that's precisely why I asked it... If you can't recall one of the cliched, stock examples that is always trotted out to explain the concept of recursion, then I have to flip on the bozo bit.
- cableshaft 12y agoAnd why would I want to store in my head a terrible solution to a problem that I'm literally only had to think about once every eight years or so in a random interview and the first time I was taught it 14 years ago in college? It's something I've never had to use at work, and I've put together dozens of full applications over the years. That being said, I could probably still come up with it, but I encounter this problem when I interview sometimes. People will ask me to recall something we covered for ten minutes back in college that I've never used since and could easily Google in five minutes if I ever did need to use it, and then they go... "ooooh, he must not be very good..." when I can't instantly spout out the solution from memory in thirty seconds, and might not be able to picture it clearly in my head without writing it out or spending a few minutes thinking about it, possibly even writing some quick code to see what happens, like I get to do whenever I'm actually working and on the job. Most recently I got that with a combinatorial function (write a function to come up with all possible combinations for blah). I was having a hard time picturing how it would show every combination in my head, including in a jumbled order. I could figure it out if I could hack away at the code for an hour, and I remembered going over it briefly in college, but I've never needed to do it in my personal or professional projects since, and so it wasn't fresh in my head. The feedback I got was they were passing on me because I got that one question wrong. I'm perfectly competent and could easily handle the job, but because I didn't study every possible algorithmic and non-algorithmic question I could possibly be asked in the three days notice I had before the interview, tough. I'm more a fan of seeing the results of people's work than asking them trivia over a field whose sphere of knowledge keeps doubling every five years that they can't possibly store every single thing in their heads at all times.