Chuck Norris Programmer Facts – part 1
When Chuck Norris throws exceptions, it’s across the room.
When Chuck Norris point to NULL, Null scares.
When Chuck Norris declares arrays, they are all of infinite size, because Chuck Norris knows no bounds.
Chuck Norris doesn’t have disk latency because the hard drive knows to hurry the hell up.
Chuck Norris does not need to know about class factory pattern. He can instantiate interfaces.
Every SQL statement that Chuck Norris codes has an implicit “COMMIT” in its end.
Chuck Norris writes code that optimizes itself.
Chuck Norris doesn’t need to use AJAX because pages are too afraid to postback.
Chuck Norris never gets a syntax error. Instead, the language gets an DoesNotConformToChuck error.
Chuck Norris doesn’t program with a keyboard. He stares the computer down until it does what he wants.
Parent is the child of Chuck Norris.
Chuck Norris can access the DB from the UI.
Chuck Norris can binary search unsorted data.
The programs that Chuck Norris writes don’t have version numbers because he only writes them once. If a user reports a bug or has a feature request, he doesn’t live to see the sun set.
Chuck Norris never gets compiler errors, the language changes itself to accommodate Chuck Norris.
Chuck Norris does not code in cycles, he codes in strikes.
Chuck Norris can’t test for equality because he has no equal.
Chuck Norris can read all encrypted data, because nothing can hide from Chuck Norris.
Chuck Norris hosting is 105% uptime guaranteed.
Chuck Norris doesn’t need the cloud to scale his applications, he uses his laptop.
Chuck Norris doesn’t need a password to access your system, the system simply gives him access.
Chuck Norris doesn’t need garbage collection because he doesn’t call .Dispose(), he calls .DropKick().
Chuck Norris’ Internet connection is faster upstream than downstream because even data has more incentive to run from him than to him.