2019-05-07
1970
#vanilla javascript
Lukas Gisder-Dubé
1731
May 7, 2019 ⋅ 7 min read

12 tips for writing clean and scalable JavaScript

Lukas Gisder-Dubé Passionate about technology, design, startups and personal development. Bringing ideas to life at dube.io.

Recent posts:

Stop writing REST APIs from scratch in 2025

Writing REST APIs by hand is a thing of the past. Frameworks like tRPC, Fastify, and Hono eliminate boilerplate with schema-driven design, improving speed and safety.

Ikeh Akinyemi
Oct 14, 2025 ⋅ 3 min read
good dx is not enough component libraries featured image

Good DX isn’t enough: Why your component library still fails your team

Great developer experience feels amazing, until your design system starts breaking down. Here’s why good DX isn’t enough and what makes teams scale successfully.

Peter Aideloje
Oct 14, 2025 ⋅ 9 min read
react 19.2 what is new and what to expect

React 19.2 is here: Activity API, useEffectEvent, and more

Discover what’s new in React 19.2, which features long-awaited features like the Activity API and the useEffectEvent Hook.

David Omotayo
Oct 13, 2025 ⋅ 7 min read
ai dev tool power rankings

AI dev tool power rankings & comparison [Oct 2025]

Compare the top AI development tools and models of October September 2025. View updated rankings, feature breakdowns, and find the best fit for you.

Chizaram Ken
Oct 13, 2025 ⋅ 9 min read
View all posts

7 Replies to "12 tips for writing clean and scalable JavaScript"

  1. Great tips, thanks! I disagree with No 3 though. I’ve found that passing arguments as destructured objects greatly improves readibility, when declaring the function AND when calling it, ie. displayUser({ firstName, lastName, age}).

  2. Better yet, just use a Style Guide that’s much more in-depth and consistent than this blog post:

    https://github.com/airbnb/javascript

    Please delete the extra line break between the two function calls in #4.

    #3 is not a good recommendation, and #4 is a perfect example of when you should pass an object to a method or function.

    Always use spaces in conditionals:

    “`
    if(foo) // BAD

    if (foo) // GOOD
    “`

    Why not use an arrow function in #9 when everything else in the post is ES6?

    “`
    cities.forEach((city) => {

    })
    “`

    Why are there no async/await code samples in #10 that show their cleaner syntax in contrast to messy nested callbacks?

    Lastly, nearly all JS Style Guides recommend the use of semicolons, particularly in cases where indentation can get odd with switch statements and method chaining.

    A for effort, but this post should really be targeted at beginners.

  3. I agree worh most of it, except for one thing.

    Drop the console.

    So web development world and each person contributing to development created this amazing tool to debug or code and you suggest dropping it, because of selling your product.

    I find logrocket very valuable in production, but i would never lustened to this.

  4. Third point is not right in all scenarios, you can manage to declare the function argument as false in the declaration, but anyhow the sequence of passing the argument matters. It is not scalable in any of the ways.

Leave a Reply