I'm normally not the type of person to dis articles, but I just read nearly 900 words and learned nothing. The tl;dr is obvious to any professional programmer:

I'm normally not the type of person to dis articles, but I just read nearly 900 words and learned nothing. The tl;dr is obvious to any professional programmer: there are short-term costs but long-term rewards to code maintainability. Unfortunately, he doesn't argue this point at all (I want to see data or an least an anecdote), or even tell what is healthy code. Instead, he opts for an extended analogy to a factually questionable "healthy eating continuum".