javascript vision thing

Simon Blackwell syblackwell at anywhichway.com
Sat Sep 22 09:54:57 UTC 2018


This has little to do with Javascript ... I started coding in 1985 and
managing (while still coding) in 1990. I have managed teams of up to 200
working on multiple products at the same time and delivered products in
8086 Assembler, Lisp, Prolog, C++, and Javascript. The only language in
which I did not see this issue was Assembler. So, from my perspective, the
problem has been around for over 25 years and probably goes beyond the
software development realm.

In my experience, during an interview, close to 100 percent of developers
will rate themselves as a 7 or an 8 out of 10 (with 10 being best).

On Sat, Sep 22, 2018, 1:14 AM kai zhu <kaizhu256 at gmail.com> wrote:

> a problem i've observed in industry is that many es6 language-features
> have the unintended-consequence of incentivising incompetent
> javascript-developers at the expense of competent-ones.  its generally
> difficult for many employers (even those knowledgeable in general-purpose
> programming), to discern between:
>
> a) a competent javascript employee/contractor who can get things done and
> ship products (albeit with legitimate delays), and
> b) an incompetent-one who can easily hide themselves in non-productive es6
> busywork, and continually pushback product-integration (again with
> “legitimate” delays, until its too late).
>
> its gotten bad enough that many industry-employers no longer trust
> general-purpose-programming technical-interviews when recruiting js-devs,
> and rely almost exclusively on either a) an applicant's reputation /
> word-of-mouth for getting things done, or b) their ability to complete a
> time-consuming tech-challenge, where they must demonstrate ability to ship
> a mini-product.  both methods are not scalable to meet the demand in
> industry for qualified js-devs in product-development.
>
> the only solution i can think of to this industry-problem is to hold-back
> on introducing new disruptive/unproven javascript design-patterns, and
> figuring out how to educate the industry with tightened javascript
> style-guides and existing design-patterns proven to work (more is less);
> generally, ways to enhance the current, woefully inadequate “bullsh*t
> detector” of employers so they can better identify and
> mentor/train/weed-out unqualified js-devs.
>
> kai zhu
> kaizhu256 at gmail.com
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180922/cf7b34d7/attachment.html>


More information about the es-discuss mailing list