PHP'ers:
Ben Ramsey
Brandon Savage
Cal Evans
Chris Shiflett
Eli White
Elizabeth Naramore
Joe LeBlanc
Justin Thorp
Mike Naberezny
Rasmus Lerdorf
Tony Bibbs
Zend Blogs
Zend DevZone
DC Social Media:
Aaron Brazell
Geoff Livingston
Jessie X
Ken Yeung
New Media Jim
Shashi B
Social Times
Technologists:
Jimmy Gardner
O'Reilly Radar
Scott Berkun
Steve McConnell
Business/mISV:
Bob Walsh
Eric Sink
Gavin Bowman
Guy Kawasaki
Joel Spolsky
Micah Baldwin
Paul Graham
Planet mISV
Past Projects:
CodeSnipers
HOBY
Judicial Watch
mobile Fox Affiliates
mobile FoxNews.com
MyDearJohnLetter
NRTW
techRepublican
Great Tools I use:
BaseCamp
Drupal
getClicky
Highrise
phpUnit
Qcodo
Subversion
web2Project
Zend Framework
This is not the home of dotProject. It is the home of CaseySoftware, LLC. Any dotProject support questions should be referred to their support forums.
This space is usually politics-free. Today I take a diversion from that course to make an argument about a political background from a technical perspective.
One of the best principles of software development is the idea of defensive code. That we build code (and systems) that expect certain inputs, validate those inputs, process those inputs, and return the expected results. When we get inputs that don't fit with the expections, our systems have to fail gracefully, limit the damage to other systems, and land in a stable state.
In many ways, a straight democratic process could work. It's not hard to collect votes nationally, to provide some form of real-time reporting, and announce results in realtime. The problem with this is the sheer number of vulnerable points. It means that anyone can inject bad data into the system anywhere - Chicago, perhaps? - and cause changes in the system as a whole... aka changing the overall election results.
In steps the Electoral College...
Recent comments
3 days 19 hours ago
3 days 23 hours ago
5 days 22 hours ago
6 days 16 hours ago
1 week 3 days ago
1 week 4 days ago
1 week 5 days ago
2 weeks 19 hours ago
2 weeks 3 days ago
4 weeks 4 days ago