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:

Rust Project for Web Services LogRocket Article

The best way to structure Rust web services

Learn how to structure Rust web services with clean architecture, Cargo workspaces, and modular crates for scalable, maintainable backends.

Jude Miracle
Oct 2, 2025 ⋅ 2 min read
andrew evans headshot

A spec-first workflow for building with agentic AI

Andrew Evans gives his take on agentic AI and walks through a step-by-step method to build a spec-first workflow using Claude Code.

Andrew Evans
Oct 1, 2025 ⋅ 18 min read

How to use TanStack DB to build reactive, offline-ready React apps

This tutorial shows how to use TanStack DB to build a task manager with live queries, optimistic updates, and offline support, delivering a fast, resilient UX with less boilerplate than traditional React state management.

Emmanuel John
Oct 1, 2025 ⋅ 12 min read
how to build a full-stack application with Tanstack Start

A step-by-step guide to building a full-stack app with TanStack Start

Follow this step-by-step guide to building a full-stack recipe application with TanStack Start, the new full-stack React framework.

David Omotayo
Sep 30, 2025 ⋅ 27 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