Thoughts for programmers that came to mind as I waded through cryptic output and documentation all afternoon:
- At least four semesters of writing classes, preferably technical, should be mandatory to get a Computer Science degree.
- Someone in the open source movement needs to publish a style guide. Failure to use and follow the style guide should be public shaming and shaving.
- If your output is so cryptic that I have to write PERL scripts to be able to read it at all, your software is about worthless.
- Related elements should not be in three separate areas of your output. There’s a reason surgeons like to line things up in the order they will be using them, and the same goes for computer people.
- “I gave up on calculating really small numbers, so I just rounded down to 0” is a cop-out. Some of us are extremely interested in the really small numbers
- A screen of text that amounts to “Hey, I wrote this, and this is crazy, but here’s a link to my webpage, so read that maybe” is not what I want to see when I input “man opensourceegotrip”. Yes, “man” has a manpage.
- Snarky emails in reply to polite questions about a confusing line in your documentation do nothing for my mood or my motivation to recommend your work to anyone.
- Days like this are why I agree that Unix SysAds are like ancient shaman. We both like to cover ourselves in scars to show how tough we are.








