Skip to content

Instantly share code, notes, and snippets.

@sebs
Last active August 29, 2015 14:07
Show Gist options
  • Select an option

  • Save sebs/37d626d5e969b2203ecf to your computer and use it in GitHub Desktop.

Select an option

Save sebs/37d626d5e969b2203ecf to your computer and use it in GitHub Desktop.

Surviving large scale Javascript projects

After a bunch of projects beyond the size of 500k loc in more than one decade, there is a bunch of good practices that we, the developers of 2014 can employ from from day1 in our projects to keep code maintainable after a while. The development landscape for javascript has changed drastically and this could be reflected in daily practices. I want to highlight some of the practices we can employ in 2014 with a modern development stack, such as

  • Splitting front- and backend for faster development cycles
  • Using static code analysis to keep code clean
  • Automate processes and procedures to ensure the same level of quality
  • use component and module systems to keep your code lean and mean
  • Write tests - to avoid repeating errors and allow for cooler designs
  • CI/CD all the stuff for early feedback
  • Documentation for the win
  • Code reuse - To avoid reinventing the wheel
  • Pair Pair Pair! - to avoid the bus factor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment