Garrett Smith did a talk on Writing Quality Code in Erlang[1] which highlights this priciple of separating intention from implementation. He starts with a 20 li

Garrett Smith did a talk on Writing Quality Code in Erlang[1] which highlights this priciple of separating intention from implementation. He starts with a 20 line function and refactors it into 16 separate functions. The result is much more verbose but it's much easier to read, understand and change. I think terseness rarely does programmers any favours in the long-run. [1] https://www.youtube.com/watch?v=CQyt9Vlkbis https://www.youtube.com/watch?v=CQyt9Vlkbis