Looking back...
As I look back at code I wrote a decade ago as an undergrad, I often find lots of little things that can be done better. For instance, in one file I found that reversing the order in which two functions were called would have eliminated a half dozen conditionals from one of the functions and would have resulted in the same expected behavior, but with fewer lines of code and a lower cyclomatic complexity.

[/code] [permanent link]

1396881317
Gear Tip: Dry Out Soggy Sneakers | Runner's World http://www.runnersworld.com/running-shoes/gear-tip-dry-out-soggy-sneakers?cm_mmc=F

==================================================================
This mobile text message is brought to you by AT&T

[/mobile] [permanent link]

... On man pages, a mini-rant
I really despise the linux man pages. They're useless at best and wrong at worst.

From the man page for setsockopt: "The include file <sys/socket.h> contains definitions for socket level options, described below."

1) The options are not "described below."
2) No, that file actually doesn't contain those definitions.

On the other hand... The FreeBSD man page for setsockopt does actually describe the options and under FreeBSD the <sys/socket.h> file does indeed contain the definitions.

[/unix] [permanent link]