> Write code that is obvious, clearly readable by future programmers maintaining the code I agree, with the caveat that does not mean low-level/unabstracted/ve

> Write code that is obvious, clearly readable by future programmers maintaining the code I agree, with the caveat that does not mean low-level/unabstracted/verbose code. Whilst each line of such code might be "obvious" on its own, the big-picture behaviour and inter-dependencies can be difficult to follow across multiple pages. As an extreme example, machine code is completely "obvious" (e.g. "increment register RAX"), whilst being notoriously hard to follow (often requiring disassemblers, etc.)