That’s a large topic that I’m going to write about in the near future. But to give a short answer: the code tells “HOW” a solution works but falls short explaining WHAT is the problem and WHY there is a problem on the first place. There are different types of doc: Architectural Decision Records, Technical Design Documents, API docs, event diagrams and even good tests can be regarded as documentation.

The juice of the tip is: write great code, but don’t stop there.

--

--

Sr. Staff Engineer @volvocars, Knowledge Worker, MSc Systems Engineering, Tech Lead, Web Developer

Love podcasts or audiobooks? Learn on the go with our new app.

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
Alex Ewerlöf

Alex Ewerlöf

Sr. Staff Engineer @volvocars, Knowledge Worker, MSc Systems Engineering, Tech Lead, Web Developer

More from Medium

A Practical Guide to Tackling Alert Fatigue

zoomed in photo of computer with code written on the screen

Malt Tech Days, product and tech culture on steroids

Fact vs. Fiction: The reality of using Applicant Tracking Systems

Sprint 2: Making Sense of “Here” and “Now”