Schematics HAVE TO define which components are in the circuit and how they are connected (unless you really want to write net lists).
Schematics SHOULD help readers to understand what a circuit does.
Especially in, let's say, "prosumer" boards (like boards designed by small companies for hobbyists) I keep seeing schematics that are designed to make it easy for the dev to get them done and NOT to communicate the circuit theory.
It's exactly like writing code without any formatting or comments. As far as I'm concerned connecting components by net name is as bad or worse than a GOTO.
Schematics SHOULD help readers to understand what a circuit does.
Especially in, let's say, "prosumer" boards (like boards designed by small companies for hobbyists) I keep seeing schematics that are designed to make it easy for the dev to get them done and NOT to communicate the circuit theory.
It's exactly like writing code without any formatting or comments. As far as I'm concerned connecting components by net name is as bad or worse than a GOTO.
\rant