4 ms·
I think you mean "easy to hire"-technology. One time it was Java, then it was PHP, now it's becoming node.js and angular. Maybe it's a bit soon, but it's far fr
by mackwic 12y ago
I think you mean "easy to hire"-technology. One time it was Java, then it was PHP, now it's becoming node.js and angular. Maybe it's a bit soon, but it's far from insane to bet on these technologies nowadays.
- Iftheshoefits 12y agoYes, that is one very big reason to go "oldschool:" there are more developers who have more experience. It is nuts to follow fad driven development on a tight budget and hard time deadlines without significant understanding of the technologies involved. I'd argue that it is nuts in general to go with fad driven development. Choosing a technology structure based on fads is a dumb idea. One should choose a structure that makes sense for the project and team.
- mercer 12y agoTrue, but it might not actually be a bad idea to hire based on an 'easy to hire' technology and actually use a technology that the developers are more experienced in. For example, I've worked in a number of environments that hired for node.js, but where the devs were actually recent RoR converts who were moderately proficient in node.js and its ecosystem. In the case of getting an MVP out quick, it might still be better to use RoR.