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:

Nesting web components in vanilla JavaScript

Nesting web components in vanilla JavaScript

Web components are underrated for the performance and ergonomic benefits they provide in vanilla JS. Learn how to nest them in this post.

Mark Conroy
Dec 5, 2023 ⋅ 10 min read
Using Defer In Angular 17 To Implement Lazy Loading

Using defer in Angular 17 to implement lazy loading

Angular’s new defer feature, introduced in Angular 17, can help us optimize the delivery of our apps to end users.

Lewis Cianci
Dec 4, 2023 ⋅ 10 min read

Using ElectricSQL to build a local-first application

ElectricSQL is a cool piece of software with immense potential. It gives developers the ability to build a true local-first application.

Rahul Padalkar
Dec 1, 2023 ⋅ 11 min read
Using Rust And Leptos To Build Beautiful Declarative User Interfaces

Using Rust and Leptos to build beautiful, declarative UIs

Leptos is an amazing Rust web frontend framework that makes it easier to build scalable, performant apps with beautiful, declarative UIs.

Eze Sunday
Nov 30, 2023 ⋅ 10 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