I was listening to a podcast about writing quality code recently, and since we just announced the Reliable Web Summit, this topic has been on my mind.

Is code an asset or a liability? I think this is a question that not all developers have pondered, and a fundamental understanding or even just an opinion on this, can radically change your view on writing code.

There’s lots of ways to define assets & liabilities, but we’ll use the following question as a way to judge if something is an asset or a liability. Is having more of it a desirable…

Joe Eames

Mormon, Christian, Father, CEO of Thinkster.io, Organizer of @ngconf, @frameworksummit, React Conf. Front end developer, and Software Craftsmanship Evangelist.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store