line-by-line

At the line-by-line level, purely functional code also takes more effort to edit, once written, than imperative code.

You don't parse ls line-by-line because you can't make the assumption that filenames will map to lines.

You can read it line-by-line with the English and toki pona texts alternating.

You could then write that line-by-line or in a spiral or something.

> At the line-by-line level, purely functional code also takes more effort to edit, once written, than imperative code.

You can't just zoom in from a package-level view to an interface-level and then keep zooming until you are eventually shown line-by-line implementation of a specific function.

The best interview I've ever had gave me a take-home programming assignment by email, then when I came in the lead programmer asked me to explain the program line-by-line and justify various decisions I made.

Yes it takes discipline to go through code line-by-line, and at times may seem pointless or like its "not sticking".

The "line-by-line" level has nothing to do with global mutable state.