- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
I went through it in my last job. I won't disturb you with the details because they would. But the important thing is that I protested one of our projects to no avail, watched in horror as my predictions came true, and had to support it when it finally reached production and was losing our client's data on a daily basis.
As you say, I should have left before getting so deep. But the job market sucked at the time, so I wasn't able to land a job elsewhere until about 8 months later.
Admin
All smart cards are buggy to a lesser or greater degree, and if the vendor had to cover all the ones that get killed through fiendishly clever attacks like, oh, to pick a random example that isn't in any way related to what one global vendor's high-security JavaCards do, writing to a negative offset in an array, then they'd go bankrupt replacing all the bricked cards.
Admin
Admin
Holly shit, the style these articles are written in is so fucking hard to read. Simple sentences, dude - especially if you're not proof-reading them.
Admin
And the PIN just HAD to be 1 2 3 4 5!!!
Admin
No, read the story again. In the first meeting, he appears as a meaty hand with five pink sausage-like fingers. Wait, no - that was just his hand. But it was the only bit about him that was described in that scene.
Admin
I call bullshit on the majority of your story. No large company would be stupid enough to sign a contract that didn't state the technology to be implemented. The client wouldn't be able to "withhold payment" just because something better had come out in the meantime.