Technical documents

The key strategy to writing important technical specifications for the benefit for implementers far and wide is as follows...

- Make sure you don't tell anyone about it until about 6 years later.
- Try to distribute your information to as many stoned HTML jockeys as possible.
- Spam Google with hundreds of keyword entries that have absolutely NO bearing on your topic.
- Make sure that any Wikipedia entries pertaining to said technology all have broken links to parked homepages belonging to jaundiced, sociopathic Mactards.
- Delete every 7th vital fact from your document.
- Put the word "Federal" on the front cover.

I take it you didn't have the best of days in the office?

I think he's just been introduced to the world of open source.

Bah! OpenSource needs no introduction, just explanation. A lot of explanation... A LOT.

Question. Should a programmer be allowed to call his program open source if the code is freaking illegible? Comment.

Quote:

---

Originally Posted by max

Comment.

---

Code:

---

// Question. Should a programmer be allowed to call his program open source if the code is freaking illegible?

---

I aspire to freaking illegibility.