Glitches in Massive Government Databases?
HBergeron asks: "Rather then post this as another YRO in the litany of new government datamarts there is a more fundamental question for all the coding Slashdot readers out there. This story, in Government Executive magazine, outlines the range of programming glitches in what is a relatively simple database. As a matter of public policy (and taxpayer money) is this level of non-functionality to be expected in these sorts of projects? Is the contractor just ripping off the taxpayers with bad code? How hard is it to write software like this that works?" The article focuses on the SEVIS database, but have others noticed similar trend in other government information systems?
Fuck you and your shitty on-topic post. God, how I hate you idiot geeks. Someone makes up a boring topic and 100 people post obvious shit (yeah, I've seen your nickname) and get modded up for it (read: circle jerk together).
There's always someone who will point out that option x is used because it's cheaper than option y. There's always someone who will point out that "the average user/manager just wants to do his stuff and doesn't care about technology" and there's always the loser who will point out how open source software would have done all this better for less money.
God, how I hate you geeks. Anyway, it's kinda rewarding to see you all losing your jobs and start shaking freedom fries at McDonalds.
If you're just a fucking worthless hobbyist then why the FUCK are you posting here! This is a place for real open anus^H^H^H^Hsource advocates!
This wouldn't happen if the Government would exclusively use open source products.
Of course, that will never happen, since open source developers don't have the money to make the "campaign contributions" required to get government contracts.
ouch!