3 ms·
> difficulty of finding trained programmers This one in particular always really annoys me. I get shot down all the time for this reason and I really don't rec
by grayrest 17y ago
> difficulty of finding trained programmers
This one in particular always really annoys me. I get shot down all the time for this reason and I really don't recommend anything a competent developer couldn't pick up in a week. That means no FP and no 'interesting' architectures because programming methodologies and different architectural approaches can't be picked up without real effort. That's fine, I'm okay with that and I don't lobby for it even if I do think it'd reduce the code base by 60%.
Shooting me down for hireabilty because I want to use yui3 instead of jQuery? Forbidding the use of SASS instead of CSS? If they can't pick it up, YOU DON'T WANT TO HIRE THEM.
- Alex63 17y agoHonestly, I do sympathize with you. There have been many times during my career when I felt there were clear benefits to using a new/less widely used technology. At one time that meant using C instead of COBOL. Unfortunately, my arguments have rarely survived the "what if you get hit by a bus" counter-argument. If you develop something using a whiz-bang technology, and then suddenly you are not there (you get a great job offer based on what you have created), who is going to support/maintain your creation while "they" find another wizard? The ancients solved the problem by laming their smiths.