3 ms·
>It's a mixture of incompetence, laziness, and poor management. Don't forget the constant, unrelenting pressure to keep up with trends or you'll get summarily
by Novashi 8y ago
>It's a mixture of incompetence, laziness, and poor management.
Don't forget the constant, unrelenting pressure to keep up with trends or you'll get summarily banned from ever having a developer job again. SPAs got trendy, so naturally everyone had to jump in on it when normal MVC applications work perfectly fine. There's a bit of hyperbole in my previous sentences, but please don't write off the endless articles and forum posts telling people to keep up with X technology because it does influence people.
Like seriously, we're constantly prodding devs into technologies they don't want to get comfortable with, then we're suddenly surprised at the lack of competence.
- Aeolun 8y agoAny dev worth his salt can be productive in any language (sooner or later). It’s when they’re hiring for technology instead of skill that I get antsy.
- eksemplar 8y agoThe rate of which you get there matters though. Because the most expensive resource is your workforce. I think modern JS is reasonably productive, and I think getting there is too. But we recently build a Blazor.net app, and even though it’s new tech, the production time was a lot lower than it would have been, had we used our standard graphql Apollo + Vue approach. I think something like django might be even more productive, but good luck hiring for that.