2 ms·
As a former JavaScript developer the problem is poor training and poor candidate selection. Many people, perhaps most, writing JavaScript professionally cannot
by austin-cheney 3y ago
As a former JavaScript developer the problem is poor training and poor candidate selection. Many people, perhaps most, writing JavaScript professionally cannot do their jobs without advanced considerable assistance, fear (as in phobia) writing original software, and cannot communicate at a professional level.
What would happen if things like Angular or React suddenly went away. Would these developers be able to write new applications. Likely not. What if a developer could no longer use jQuery or equivalent helper libraries? Could they continue to deliver work? Almost certainly not.
When most of the work force is only interested in their own narcissism the industry has failed on multiple levels. This is experienced when the first, second, and third priorities are only in the developer’s own self interest such as needing things to be easy. That is why software is bloated, because when the self-interest of the developer is all that matters performance and efficiency become absurdly irrelevant.
The solution to this problem is to set high standards. Not high compared to other professions but astonishingly high compared to software today. If current developers cannot achieve such lofty professional standards do not hire them as senior developers. It may mean it’s in the best interest for employers to train people off the street who are not yet corrupted by poor habits. Eventually the solution will become economic: what is cheaper for the employer. Will it be cheaper to employ large staffs that deliver bad products slowly in their own self-interest or start anew with well trained teams that deliver excellence rapidly at great training or certification expense.
Until the industry figures this out I will never write JavaScript professionally again. Currently, children run the daycare.
- whstl 3y agoYou had been downvoted, but I share the same experience. It has become very difficult to have some discussions with less experienced developers, because they have a problem accepting that there are alternatives they're not familiar about. Just this week I had a discussion with a recent hire that claimed it was impossible to use GraphQL without a dedicated client library. The claim that our team built our current product with just fetch was met with "there must be some security issue, or you had to rebuild from scratch something that is as complex as Apollo".