The number of tools has increased, but I think JS development has actually been simplified in some cases. This is largely due to the rise in popularity of rich clients talking to simple backend APIs. In older web projects JS always felt like an afterthought. Dependencies were managed totally by hand and your scripts were scattered throughout the backend templates. If you needed to do anything at all with your front-end code at build time, you had no choice but to glue some hacky solution onto the existing build process. Client and server were all mixed together, and it was painful.
Starting a project today, I can build a client in Javascript, hook it up to an API, and I'm done. NPM and Browserify make dependency management and builds a breeze. There's very little friction in the development workflow because the front-end build process it totally separate from the server. I make a change, save it, reload the page and I see my changes live without even running a server locally. Even PHP's deployment story isn't that simple.
It's true that the initial setup is more complicated than simply downloading jQuery and plopping it into an existing project, but if you have the option of separating your client and server code, it really simplifies things overall.
Everyone is guilty of this. You, me, and everyone else on earth. Ignorance of your own ignorance is what buoys overconfidence in the first place.
From the article:
"The American author and aphorist William Feather once wrote that being educated means “being able to differentiate between what you know and what you don’t.” As it turns out, this simple ideal is extremely hard to achieve. Although what we know is often perceptible to us, even the broad outlines of what we don’t know are all too often completely invisible. To a great degree, we fail to recognize the frequency and scope of our ignorance."
Not to the same degree. I made a choice nearly 2 decades ago to say 'I don't know' more often - I was doing on-site networking and tech support for a living, and I was tired of trying to produce on-the-spot explanations for why computers were misbehaving in order to soothe clients, so I stopped doing it. This led to some pushback at first - clients would say 'well what I am I paying you for if you don't know?!' and suchlike, but by explaining that I had a diagnostic process and a fallback position if it didn't work (provide a replacement for a piece of hardware or back up and reinstall the OS or whatever), I could usually get people to agree that an ounce of patience was preferable to a pound of bullshit. This turned out to be a good strategy and I adopted it as a habit in other parts of life, makinh conversation much easier and more interesting - eg if I met someone interesting at a party, instead of trying to maintain intellectual parity I'd say 'I'm ignorant of [your field], could you explain [some basic principle]?' and so on. At the same time I developed a habit of trying to fact-check everything before making positive statements, or if I was conversing in person, citing my sources or qualifying my remarks.
This isn't to say I'm immune to ignorance, as I have assumptions and misapprehensions like everyone else, not to mention being forgetful, so I have approximate knowledge of many things.* But assuming it as the default in both personal learning and social contexts I've saved myself an awful lot of grief. Unfortunately this sometimes leads to equally fallacious overestimates of general competence, which is also part of the Dunning-Krueger effect :-/
Starting a project today, I can build a client in Javascript, hook it up to an API, and I'm done. NPM and Browserify make dependency management and builds a breeze. There's very little friction in the development workflow because the front-end build process it totally separate from the server. I make a change, save it, reload the page and I see my changes live without even running a server locally. Even PHP's deployment story isn't that simple.
It's true that the initial setup is more complicated than simply downloading jQuery and plopping it into an existing project, but if you have the option of separating your client and server code, it really simplifies things overall.