I am a software engineer not an electronics engineer; believe me I am under no illusion that my schematic looks as if it had been done by someone who actually knew what he was doing. That said, I do this to learn. If you have something you feel are good examples of schematics, I'll go right ahead and read them.
Thank you for the feedback!
@xliijoe, I wasn't trying to put you down, I commend your efforts here.
But starting out on a new thing, it's often important that someone stops you going off in the wrong direction from the start (otherwise it quickly gets inborn).
Everyone has her/his own style when doing schematic artwork (yes, it's really artwork, just as PCB layout is artwork). This can be symbol styles, adding colours or shading etc. But the main goal is to make the circuit understandable to yourself and to other people.
There are a few basic rules that should be followed:
The main signal path runs from left to right through the schematic. Input: left, output: right.
Supply voltages are stacked from top to bottom, most positive voltage at the top.
Symbols are connected using connecting lines (and buses), NOT using labels.
Feedback paths usually run right to left. This simplifies routing and is immediately understandable.
Symbols are drawn as shapes with signals belonging together also being grouped together (sequentially, if indicated). Symbols are NOT drawn as a DIP/SO-16 or PLCC-44 packages with pins 1...16/44 (or whatever).
Global labels are used to get signals into and out of the schematic, not for internal connections (there are exceptions, but they are rare).
I attach two examples, one analog and one digital. These are the "rough-and-tumble" type of schematics I draw to get the best functional overview. Power flags etc. are missing, but can be added as needed when it moves on to ERC, simulation etc.
The point is, that placing/moving the symbols make for best routing, readability, and understanding.