You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ To break the boredom, use a thesaurus to look up as much alternate vocabulary as
61
61
62
62
####Use Plural Forms From Other Languages
63
63
64
-
A VMS script kept track of the "statii" returned from various "Vaxen". Esperanto ,[Klingon](http://www.kli.org/) and[Hobbitese](http://www.chriswetherell.com/hobbit/default.asp target=) qualify as languages for these purposes. For pseudo-Esperanto pluraloj, add oj. You will be doing your part toward world peace.
64
+
A VMS script kept track of the "statii" returned from various "Vaxen". Esperanto ,[Klingon](http://www.kli.org/) and[Hobbitese](http://www.chriswetherell.com/hobbit) qualify as languages for these purposes. For pseudo-Esperanto pluraloj, add oj. You will be doing your part toward world peace.
65
65
66
66
####CapiTaliSaTion
67
67
@@ -131,7 +131,7 @@ Never use `i` for the innermost loop variable. Use anything but. Use `i` liberal
131
131
####Conventions Schmentions
132
132
133
133
134
-
Ignore the[Sun Java Coding Conventions](http://java.sun.com/docs/codeconv/), after all, Sun does. Fortunately, the compiler won't tattle when you violate them. The goal is to come up with names that differ subtlely only in case. If you are forced to use the capitalisation conventions, you can still subvert wherever the choice is ambigous, e.g. use*both*_input**F**ile**n**ame_ and_input**f**ile**N**ame_. Invent your own hopelessly complex naming conventions, then berate everyone else for not following them.
134
+
Ignore the[Sun Java Coding Conventions](http://web.archive.org/web/20091003224540/http://java.sun.com/docs/codeconv/), after all, Sun does. Fortunately, the compiler won't tattle when you violate them. The goal is to come up with names that differ subtlely only in case. If you are forced to use the capitalisation conventions, you can still subvert wherever the choice is ambigous, e.g. use*both*_input**F**ile**n**ame_ and_input**f**ile**N**ame_. Invent your own hopelessly complex naming conventions, then berate everyone else for not following them.