4 ms·

Heh, I used to think web development was hard because you had to learn sql, python, html, css, and javascript. Apparently you really have to learn those, plus,

by krupan 14y ago

Heh, I used to think web development was hard because you had to learn sql, python, html, css, and javascript. Apparently you really have to learn those, plus, flask, backbone, coffescript, require.js, jquery, bootstrap, handlebars.js, stylus, mocha, zombie, etc., etc. Simple! :-)

sdfjkl 14y ago
And then people complain when they can't seem to hire anyone that knows their tech stack of the minute.
- heretohelp 14y ago
  Our company hires people who are simply interesting, intelligent, and willing to learn. We seriously consider non-coders for positions that will be primarily coding if they have a strong background in some interesting field (like statistics). Not all companies are just vomiting lists of reqs into the void while sitting on their hands for the perfect candidate to roll in.
  - pyre 14y ago
    I've always been under the impression that those "50 years of Java + .Net + COBOL" adverts are purposely made unattainable because they already have someone lined up for the job, but they need to 'advertise' the job for legal reasons.
    - heretohelp 14y ago
      Incompetence is a pretty common reason for it. Your case you outline is pretty rare.
- kosmikko 14y ago
  We don't hire people based on our tech stack, or at least knowing every part of is not a prerequisite. I know that great engineers can learn any stack quickly. If you have experience in writing similar (in this case frontend heavy JS) apps with any stack you can potentially work for us. Anyways, the stack is part of your app. You can either write it yourself or build on existing components. Sure you can build your stack on top of more traditional technology, and likely there will be more potential candidates but finding good developers will be just as hard.
almost 14y ago
Libraries are good, so instead of having to learn to implement all those things (or learn how the last guy implemented them) you can just learn the library :)
peacemaker 14y ago
My thoughts exactly! How many tools and tech does one website need?! :)
danneu 14y ago
I think you'll be hard pressed to find a peripheral tool that you can't confidently be productive in after a few hours to a few days. The list of buzzwords isn't so much evidence that you need to be proficient in a lot of random tools as it's evidence that you should feel unattached and comfortable learning new tools if you want to participate in the web space.

by krupan 14y ago

sdfjkl 14y ago

And then people complain when they can't seem to hire anyone that knows their tech stack of the minute.

heretohelp 14y ago
Our company hires people who are simply interesting, intelligent, and willing to learn. We seriously consider non-coders for positions that will be primarily coding if they have a strong background in some interesting field (like statistics). Not all companies are just vomiting lists of reqs into the void while sitting on their hands for the perfect candidate to roll in.
- pyre 14y ago
  I've always been under the impression that those "50 years of Java + .Net + COBOL" adverts are purposely made unattainable because they already have someone lined up for the job, but they need to 'advertise' the job for legal reasons.
  - heretohelp 14y ago
    Incompetence is a pretty common reason for it. Your case you outline is pretty rare.
kosmikko 14y ago
We don't hire people based on our tech stack, or at least knowing every part of is not a prerequisite. I know that great engineers can learn any stack quickly. If you have experience in writing similar (in this case frontend heavy JS) apps with any stack you can potentially work for us. Anyways, the stack is part of your app. You can either write it yourself or build on existing components. Sure you can build your stack on top of more traditional technology, and likely there will be more potential candidates but finding good developers will be just as hard.

almost 14y ago

Libraries are good, so instead of having to learn to implement all those things (or learn how the last guy implemented them) you can just learn the library :)

peacemaker 14y ago

My thoughts exactly! How many tools and tech does one website need?! :)

danneu 14y ago

I think you'll be hard pressed to find a peripheral tool that you can't confidently be productive in after a few hours to a few days. The list of buzzwords isn't so much evidence that you need to be proficient in a lot of random tools as it's evidence that you should feel unattached and comfortable learning new tools if you want to participate in the web space.