more info ⬇

@amattn

SW engineering, engineering management and the business of software

subscribe for more
stuff like this:

2017 01 10

`go fmt` is the best part of go

Imagine a traveler. This traveler has a unique constraint. He can only take a step if he juggles balls that match the color of the landscape around him. In some places, like a barren desert, this isn’t a large number. But it other places, like city or a fruit garden, it’s a tremendous number of balls and colors that require coordination and focus. Just to take a single step.

Like our hypothetical traveler, Engineers are constantly keeping track of multiple high and low level concepts during any given coding session. Examples include product requirements, testability, scale, bugs, security concerns, performance requirements, and many more.

Standardized, tool enforced formatting is one less ball to track.



you may also be interested in some of the greatest hits of amattn.com:

〜 Empathy as a Core Engineering Requirement

〜 Venture Capital Math 101

〜 You Should Foster a Culture of Readability

〜 The Customer's Semi-Lucid Trance State

〜 ARC Best Practices




the fine print:
aboutarchive@amattn
© matt nunogawa 2010 - 2019 / all rights reserved
back ⬆