Coded Geekery

Clean Code Javascript

February 14, 2017

Ryan Mcdermott:

Software engineering principles, from Robert C. Martin’s book Clean Code, adapted for JavaScript. This is not a style guide. It’s a guide to producing readable, reusable, and refactorable software in JavaScript.

Not every principle herein has to be strictly followed, and even fewer will be universally agreed upon. These are guidelines and nothing more, but they are ones codified over many years of collective experience by the authors of Clean Code.

Our craft of software engineering is just a bit over 50 years old, and we are still learning a lot. When software architecture is as old as architecture itself, maybe then we will have harder rules to follow. For now, let these guidelines serve as a touchstone by which to assess the quality of the JavaScript code that you and your team produce.

One more thing: knowing these won’t immediately make you a better software developer, and working with them for many years doesn’t mean you won’t make mistakes. Every piece of code starts as a first draft, like wet clay getting shaped into its final form. Finally, we chisel away the imperfections when we review it with our peers. Don’t beat yourself up for first drafts that need improvement. Beat up the code instead!

You need to go and read Ryan’s manifesto on Clean Code for Javascript right now.

I’ve followed Clean Code practices for years, and it’s nice to see people taking it and making use of it.

Here’s an example:


Use meaningful and pronounceable variable names


const yyyymmdstr = moment().format('YYYY/MM/DD');


const currentDate = moment().format('YYYY/MM/DD');

Use the same vocabulary for the same type of variable





You can get the rest from his post.

Source: Clean Code for Javascript

Roger Stringer

Written by Roger Stringer, Coded Geekery is a blog designed to give me a forum to talk and think. You should follow me on Twitter