LINKBLOG for July 18, 2007
- *** A Day in the Life of an Information Security Investigator
Maybe you know the guy, maybe not. Anyway, SecurityMonkey has been around for a couple years delivering a huge amount of case files on Computer Forensics. Really reads like a thriller or detective! Like it, and spend half a weekend browsing around, consuming all the cases. Although not programming related, I still find very valuable lessons there, from which every PC-savvy person can learn.
And by the way, he is so popular that last week the ITTToolbox Blogs to a grinding halt: writing Im In Your Leenucks Box Changing Your Password and generating 150,000 pageviews on that article by being digg'ed, redditt'ed etc. was just too much apparently :-)
- Tools I use as a .Net Developer - Derik Whittaker
- Note to Software Vendors, the World is Collaborative and Loosely Coupled - Dare Obasanjo
' This change was crashing the applications that were invoking our service because they weren’t expecting us to return bananas. '
- Utility Methods - Are They The Devil? - Palermo4
Via Jeffrey Palermo (see below)
- Utility methods, utility classes, common classes - a blob is not an abstraction - Jeffrey Palermo
Somehow posts like these always attract me on a certain level. But I haven't adopted the underling principles of TDD/DDD and what have you, so it's something else toput it into use in my own situation.
- 101 Ways To Know Your Software Project Is Doomed
- The Waterfall Manifesto for Realistic Software Development
The Waterfall guys strike back:' While the principles of the Manifesto for Agile Software Development may look appealing for inexperienced developers, serious professionals know that the real world is not similar to the "Little House on the Prairie" '
Take that :-)
- 19 Eponymous Laws Of Software Development - Haacked
In which you learn the meaning of...eponymous (didn't have a clue!)
- Where did my MSDN go? - telerik blogs
One of those seemingly completely unrelated issues making software development so hard.
- Vesting - Joel on Software
Release your software AEAP (as-early-as-possible) or only after some good old bugfixing: it depends.