If any associate engineers out there would like to see an example of a well-commented, concise approach for something where the seemingly simple approach becomes too verbose, here it is.

This is careful result of several iterations, and it’s still not “finished”. https://twitter.com/jamiedixon/status/1249722032327217154

Reminds me of a trite, tongue-in-cheek question I often ask my engineers: what is the first thing that an engineer does when they find a solution to a problem?

They stop looking.

Be more @jamiedixon. Find a solution. Iterate. Take a peek, to see if there’s a different way.

The more solutions to a problem you find, the more you’ll understand the problem, and the better placed you’ll be to understand the solution.

After all, if you’ve only got one solution, how do you know it’s the “right” solution? It’ll also help you to understand where other engineers might be approaching it from, which aids collaboration through empathy.

From a practical standpoint it’ll aid code reviews on two fronts: first, your code will look like it’s already been refined and iterated. Secondly, there’s a good chance that you may have already explored your reviewers suggestions, so it’ll help them to understand your choices.

I don’t have a soundcloud, but as this thread will only be seen by four people and a tired cat, I’m not sure it matters.