Procedure names should reflect what they do; function names should reflect what they return

Such is modern computing: everything simple is made too complicated because it's easy to fiddle with; everything complicated stays complicated because it's hard to fix.

Data dominates. If you've chosen the right data structures and organized things well, the algorithms will almost always be self-evident. Data structures, not algorithms, are central to programming.

Sockets are the X windows of IO interfaces.

Why would you have a language that is not theoretically exciting? Because it's very useful.

Procedure names should reflect what they do; function names should reflect what they return

Eventually, I decided that thinking was not getting me very far and it was time to try building.