User contributions
From WikiContent
(Newest | Oldest) View (Newer 50) (Older 50) (20 | 50 | 100 | 250 | 500)
- 08:32, 28 July 2009 (hist) (diff) Two Wrongs Can Make a Right (and Are Difficult to Fix) (top)
- 17:44, 23 July 2009 (hist) (diff) Two Wrongs Can Make a Right (and Are Difficult to Fix)
- 10:12, 15 July 2009 (hist) (diff) Check Your Code First before Looking to Blame Others
- 14:19, 1 February 2009 (hist) (diff) Two Wrongs Can Make a Right (and Are Difficult to Fix)
- 14:14, 1 February 2009 (hist) (diff) Check Your Code First before Looking to Blame Others
- 14:14, 1 February 2009 (hist) (diff) Two Wrongs Can Make a Right (and Are Difficult to Fix)
- 13:02, 1 February 2009 (hist) (diff) 97 Things Every Programmer Should Know (→In Progress)
- 13:01, 1 February 2009 (hist) (diff) Check Your Code First before Looking to Blame Others (New page: Developers — all of us! — often have trouble believing our own code is broken. It is just so improbable that, for once, it must be the compiler that's broken. Yet in truth it is very ...)
- 13:00, 1 February 2009 (hist) (diff) 97 Things Every Programmer Should Know (→In Progress)
- 12:56, 1 February 2009 (hist) (diff) Don't blame the compiler (New page: Developers — all of us! — often have trouble believing our own code is broken. It is just so improbable that, for once, it must be the compiler that's broken. Yet in truth it is very ...) (top)
- 12:55, 1 February 2009 (hist) (diff) 97 Things Every Programmer Should Know (→In Progress)
- 12:55, 1 February 2009 (hist) (diff) The Compiler Isn't Broken (top)
- 12:51, 1 February 2009 (hist) (diff) The Compiler Isn't Broken
- 17:38, 29 December 2008 (hist) (diff) 97 Things Every Programmer Should Know (→Completed)
- 17:38, 29 December 2008 (hist) (diff) 97 Things Every Programmer Should Know (→In Progress)
- 17:38, 29 December 2008 (hist) (diff) Two Wrongs Can Make a Right (and Are Difficult to Fix)
- 17:35, 29 December 2008 (hist) (diff) The Compiler Isn't Broken
- 10:59, 21 December 2008 (hist) (diff) 97 Things Every Programmer Should Know (→In Progress)
- 16:57, 6 December 2008 (hist) (diff) The Hallmark of good code is extensibility (New page: The late John Vlissides wrote: "A hallmark - if not the hallmark - of good object oriented design is that you can modify and extend a system by adding code rather than hacking it.... In s...) (top)
- 16:45, 6 December 2008 (hist) (diff) 97 Things Every Programmer Should Know (→In Progress)
- 18:21, 5 December 2008 (hist) (diff) The Compiler Isn't Broken
- 18:44, 29 November 2008 (hist) (diff) Programming is a team sport (New page: Once upon a time, in a land far far away, programmers could lock themselves in a room (often a bed room), with a great idea, a Z80, a few kilobytes of ram and a lot of Coke-Cola. A few da...) (top)
- 18:38, 29 November 2008 (hist) (diff) The Hallmark of good OO code is extendibility (New page: The late John Vlissides wrote: "A hallmark - if not the hallmark - of good object oriented design is that you can modify and extend a system by adding code rather than hacking it.... In s...) (top)
- 18:37, 29 November 2008 (hist) (diff) 97 Things Every Programmer Should Know (→In Progress)
- 18:24, 29 November 2008 (hist) (diff) The Compiler Isn't Broken (New page: It is really really really unusual that code is broken by a bug in the compiler, or interpreter, or the OS, the app-server, the database, the memory manager or any other piece of system so...)
- 18:22, 29 November 2008 (hist) (diff) Two Wrongs Can Make a Right (and Are Difficult to Fix)
- 18:17, 29 November 2008 (hist) (diff) 97 Things Every Programmer Should Know (→In Progress)
- 18:17, 29 November 2008 (hist) (diff) 97 Things Every Programmer Should Know (→Not Started)
- 12:46, 30 October 2008 (hist) (diff) The chances of the bug being in the compiler, interpreter, OS, AppServer, memory manager, etc. really is small (New page: Once in 10 years I had a genuine problem with a compiler bug optimising away a loop variable. But I imagined my compiler or OS had a bug every few months. And I wasted a lot of my time, ...) (top)
- 12:44, 30 October 2008 (hist) (diff) 97 Things Every Programmer Should Know (→Not Started)
- 14:56, 29 October 2008 (hist) (diff) Two Wrongs Can Make a Right (and Are Difficult to Fix) (New page: Code never lies but it can contradict itself. Some contraditions lead to those "How can that possibly work?" moment. ((Need to give an example)) This leads to the most difficult bugs to...)
- 14:46, 29 October 2008 (hist) (diff) User:Allankelly (Replacing page with 'Goto Allan Kelly') (top)
- 14:46, 29 October 2008 (hist) (diff) Allan Kelly (New page: == Allan Kelly == == Bio == Allan helps companies improve their development activities. Usually this means delving into the Agile toolbox and selecting the right tools. With many years ...) (top)
- 14:41, 29 October 2008 (hist) (diff) 97 Things Every Programmer Should Know (→Not Started)
- 14:40, 29 October 2008 (hist) (diff) User:Allankelly (→Bio)
- 14:33, 29 October 2008 (hist) (diff) Image:Allankelly.jpg (uploaded a new version of "Image:Allankelly.jpg") (top)
- 21:03, 28 October 2008 (hist) (diff) User:Allankelly
- 21:02, 28 October 2008 (hist) (diff) Image:Allankelly.jpg (uploaded a new version of "Image:Allankelly.jpg")
- 21:00, 28 October 2008 (hist) (diff) Image:Allankelly.jpg
- 20:55, 28 October 2008 (hist) (diff) User:Allankelly
- 20:55, 28 October 2008 (hist) (diff) User:Allankelly (New page: == Allan Kelly ==)
- 20:53, 28 October 2008 (hist) (diff) User talk:Allankelly (New page: Full Name Allan Kelly [edit] Biography [edit] Contact Info mailto:allan@allankelly.net [edit] Image) (top)
(Newest | Oldest) View (Newer 50) (Older 50) (20 | 50 | 100 | 250 | 500)
