The Web Development Skills Crisis
snydeq writes "Fatal Exception's Neil McAllister raises questions regarding Web development skills in an era of constant innovation. Sure, low barriers to entry give underdog technologies ample opportunity to thrive without the backing of name-brand vendors. But doesn't this fragmentation of the Web development market put undue pressure on developers to specialize? Choosing one tool to be your bread and butter from a field this broad is one thing, McAllister writes. Recruiting talent for a Web project when your technology requirements eliminate most of the applicants is another. The result is a crisis, McAllister concludes, one in which maintaining a marketable skill set gets more and more difficult as the so-called state of the art changes on an almost daily basis."
My organization just started a unique online system, which was custom written by a vendor. The software is all PHP with a Linux/MySQL backend, and uses OSS software throughout. I took the reins to get the system up and running, but now, for the first time, we started looking for a dedicated web developer to publish works to this site, work on troubleshooting, and work with the vendor to design modifications to it. We went through over a dozen interviews over the past few weeks. It was bloody awful.
My (admittedly high) goals was a web developer that new PHP, could work with Linux (SSH), and had very basic client-side programming (C, Perl, whatever) to develop more tools for us down the road. Oh, and someone that could do some graphic art work would be a definite value-add.
Every single person that came in was an mainly ASP or ASP.NET programmer. Only two had Linux experience. Three or four had Photoshop experience. As a programmer myself, I ventured to the hopeful candidates on what languages they would like to learn next, or what skills they want to improve upon. Across the board, they were all happy staying with ASP, didn't want to learn PHP, and some inquired into when we would want to move from PHP to ASP. I had intentionally kept the field open to non-PHP people to try and find a true programmer that just didn't have those letters on their resume, but the majority were sticking themselves to a single language.
When all was said and done, we hired someone. He didn't know Linux, and didn't know PHP, but he was a definite "Active Learner". He was self-taught in nearly everything he knew, and was willing to learn any language we needed him to learn. He was one of the two candidates that had expressively mentioned that programming was just picking up a language and using it; all the rest were ASP specialists and thought that using another language wasn't worth their investment.
You're obviously joking, but I've had it happen to me. I actually had an incident in which the employer was requesting, for a mid level position, 2 years more experience in Java than were possible except for its creators: the JDK had been out for about 4 years at the time and they were asking for 6. I decided it was a simple error on their part and applied anyway. To my shock, I got an angry call from their HR department, who were actually calling to chew me out for applying even though I was "unqualified" for not having the required 6 years of experience. At first I thought it was a joke and laughed, but it became clear they were serious. I tried to explain to them that there were perhaps 7 people on earth with what they were asking for because the JDK had only been out for 4 years, but they were having none of it, and with some parting insults, hung up on me.
In all I'm glad I don't work for them, any company that stupid and unprofessional would not be good for my reputation to have on my resume.
I'm glad my company (Japanese) doesn't have this problem. My last job had about a week of actual training that wasn't very useful. My new company is sending me to external training ($$$) for about 30 days. Then I get about 12 weeks of company training in Japan. And then 5 weeks of on the job training, and back to Japan for another 4 weeks. Its about 6 months of me doing nothing productive, just training heavilly. The company is making a serious investment in me, and from what I have seen from it in the last month, I will hopefully be sticking with them for a long time.
Don't skimp on the training. Its exactly what makes your employees experts in their areas and want to stick around. We also have casual Friday every day, and that doesn't hurt either.
Even those who arrange and design shrubberies are under considerable economic stress at this period in history.
You're right, but that flies in the face of contemporary management theory.
The way companies do it now is they "buy" the skills they want: they demand outrageous skill combinations, and don't settle until they get them. Then they offer the person the bare minimum they think they'll take, and plan to never promote them. At a management job I had a few years ago, I got told by senior management that my staff would never get promotions, because that would cost money, and that the employer didn't care if they left because of it, because we'd just replace them. (I started looking for a new job the next day. I didn't want a promotion, but I figured if they're that stupid I didn't want to be there.) I told them I preferred to hire junior people, who were cheaper and more malleable, train them up and them promote them to mid-level. They basically told me I was amusing.
Meanwhile, these employers who don't care if their people leave and will lay them off at the drop of a poor earnings report are the first to complain about "lack of company loyalty" among their employees. I've reached the point that if an employer complains to me about lack of company loyalty, I tell them outright that I have no more loyalty to them than they have to me, and explain to them that I base that assessment on how I've seen them treat their other people, and give examples.
Surprisingly, they've actually tried to keep me after that.