Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (64)

Strategic activity mapping for software architects May 25, 2025 On the role of Distinguished Engineer and CTO Mindset Apr 27, 2025 The future is bright Mar 30, 2025 2024 Reflections Dec 31, 2024 My giant follows me wherever I go Sep 20, 2024 Are developer jobs truly in decline? Jun 29, 2024 Some thoughts on recent RTO announcements Jun 22, 2023 One size does not fit all: neither cloud nor on-prem Apr 10, 2023 Should today’s developers worry about AI code generators taking their jobs? Dec 11, 2022 Working from home works as well as any distributed team Nov 25, 2022 Why you should question the “database per service” pattern Oct 5, 2022 Good developers can pick up new programming languages Jun 3, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Peloton could monetize these ideas if they only listen May 15, 2022 Good idea fairy strikes when you least expect it May 2, 2022 Best practices for building a microservice architecture Apr 25, 2022 TypeScript is a productivity problem in and of itself Apr 20, 2022 In most cases, there is no need for NoSQL Apr 18, 2022 A year of COVID taught us all how to work remotely Feb 10, 2021 Making the best of remote work - Coronavirus blues Mar 16, 2020 TDWI 2019: Architecting Modern Big Data API Ecosystems May 30, 2019 Using Markov Chain Generator to create Donald Trump's state of union speech Jan 20, 2019 The religion of JavaScript Nov 26, 2018 Let’s talk cloud neutrality Sep 17, 2018 Fixing the Information Marketplace Aug 26, 2018 What does a Chief Software Architect do? Jun 23, 2018 I downloaded my Facebook data. Nothing there surprised me. Apr 14, 2018 Nobody wants your app Aug 2, 2017 Node.js is a perfect enterprise application platform Jul 30, 2017 Design patterns in TypeScript: Chain of Responsibility Jul 22, 2017 Singletons in TypeScript Jul 16, 2017 Rather than innovating Walmart bullies their tech vendors to leave AWS Jun 27, 2017 Architecting API ecosystems: my interview with Anthony Brovchenko of R. Culturi Jun 5, 2017 TDWI 2017, Chicago, IL: Architecting Modern Big Data API Ecosystems May 30, 2017 Collaborative work in the cloud: what I learned teaching my daughter how to code Dec 10, 2016 Don't trust your cloud service until you've read the terms Sep 27, 2016 In search for the mythical neutrality among top-tier public cloud providers Jun 18, 2016 What can we learn from the last week's salesforce.com outage ? May 15, 2016 Why it makes perfect sense for Dropbox to leave AWS May 7, 2016 JavaScript as the language of the cloud Feb 20, 2016 OAuth 2.0: the protocol at the center of the universe Jan 1, 2016 Our civilization has a single point of failure Dec 16, 2015 IT departments must transform in the face of the cloud revolution Nov 9, 2015 What Every College Computer Science Freshman Should Know Aug 14, 2015 Ten Questions to Consider Before Choosing Cassandra Aug 8, 2015 On Maintaining Personal Brand as a Software Engineer Aug 2, 2015 The Three Myths About JavaScript Simplicity Jul 10, 2015 Book Review: "Shop Class As Soulcraft" By Matthew B. Crawford Jul 5, 2015 Attracting STEM Graduates to Traditional Enterprise IT Jul 4, 2015 Your IT Department's Kodak Moment Jun 17, 2015 The longer the chain of responsibility the less likely there is anyone in the hierarchy who can actually accept it Jun 7, 2015 Big Data is not all about Hadoop May 30, 2015 Smart IT Departments Own Their Business API and Take Ownership of Data Governance May 13, 2015 The Clarkson School Class of 2015 Commencement speech May 5, 2015 Building a Supercomputer in AWS: Is it even worth it ? Apr 13, 2015 Ordered Sets and Logs in Cassandra vs SQL Apr 8, 2015 What can Evernote Teach Us About Enterprise App Architecture Apr 2, 2015 Microsoft and Apple Have Everything to Lose if Chromebooks Succeed Mar 31, 2015 Software Engineering and Domain Area Expertise Nov 7, 2014 Wall St. wakes up to underinvestment in OMS Aug 21, 2014 Software Engineers Are Not Doctors Aug 3, 2014 Cassandra: Lessons Learned Jun 6, 2014 Java, Linux and UNIX: How much things have progressed Dec 7, 2010 Eminence Grise: A trusted advisor May 13, 2009

The Three Myths About JavaScript Simplicity

July 10, 2015

Pondering
There is a perception among many in the software industry that JavaScript is simpler to learn and use than, say, Java. I've even heard some say that JavaScript developers are easier to recruit.
While there are many myths about JavaScript that detractors cite as reasons not to use it, there are also at least as many myths propagated by advocates of this technology. These are the most common ones I've heard over the years.

1) JavaScript Developers are Easier to Recruit

That only holds true if you are trying to hire a 17 year old who built simple websites out of his mother's basement. Yes, he knows JavaScript, and yes he'll take you up on that low ball offer that no experienced developer will accept. Will you get a timely professional result ?

Lisa Eadicicco writing for Business Insider shows that average JavaScript developer salary is right up there along with C++ and Java:


  1. JavaScript - $91,461

  2. C++ - $93,502

  3. JAVA - $94,908


A cursory search of LinkedIn reveals almost 5 million people listing Java as their skill, and less than 3 million who list JavaScript as their skill. By this statistics alone, one is almost twice as likely to recruit a Java developer than they are a JavaScript developer.

2) JavaScript is Easy to Learn

By the law of Turing Equivalency most programming languages are equivalent and if you know one you can learn any other. The complexity is never in the language itself - it is in the frameworks and libraries.

I am writing this post in 2015 and JavaScript has been powering web apps for at least 20 years. One would think that by now handling HTTP and building MVC apps would be part of the platform. Yet, JavaScript leaves much to be desired.

JavaScript, for example, has multiple libraries for HTTP REST requests. In Node.js it is not uncommon to use one library on the server and a totally different one on the client. Consider the multitude of single-page app MVC frameworks - each one has a drastically different philosophy of using it.

The difference between null and undefined and between == and === as well as lack of type safety leave much to be desired. The developer has to constantly keep those nuances in mind, as if they have nothing better to do.

3) Non-Developers Can Learn to Use JavaScript

This argument usually goes along with myth #2. The only advantage JavaScript has over other languages is that the most one needs to get started writing in it is a text editor and a web browser. That is not something to be overlooked -- JavaScript really is an easy language to get started in because of that.

More often than not developers will learn the business domain of their apps long before business users will learn how to program. There are languages that business users may be more comfortable writing code in -- SQL comes to mind, for instance, and perhaps the data and reporting APIs can and should be built by the business analysts.

So Why JavaScript ?

The points above should not be a reason not to use JavaScript. Reality is that when it comes to building dynamic webapps and microservices there is no choice other than to use it. It is a great tool for rapid prototyping and for building backend services using platforms like AWS Lambda. Despite what I said, it is a great language and has many useful applications -- but make no mistake, it is a programming language like any other.