- 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
"Storing Terabytes of dross data does not mean that information useful to the business is being retained."
I had this argument with a developer a few days ago. Says me "I'm not going to keep buying more disks for you. Its time to clean up. You don't need to have a local copy of everything data set from the file servers, everything you've ever downloaded and all the software from the repositories."
He says "But I don't have a whole day to spend on cleaning up."
Me "Arrgggg".
Admin
It could be a 1:1 replication of live data, as it is easier to sync testing and production from production backups than it is to build testing from a blank slate.
Admin
Gee, I guess tblProducts.IsCurrent could be a true/false value and make everyone happy
inb4 someone not being happy
Admin
So give him a whole day to do it. I vote for Sunday.
Admin
I'm gonna legally change my name to "Name Redacted", and then sue the hell out of everyone involved for slander, defamation of character, libel, and any other powerful sounding legal phrases I can come up with. Then, I'll be Rich!
Hey! It could happen!
Wow. Captcha. Hope it's not prophetic! "damnurn"
Admin
You mean
Admin
You never know who may be looking for a product from 1993. For example:
http://www.cdwg.com/shop/products/default.aspx?edc=21878
Admin
If you're unit tests are interacting with the DB then they aren't unit tests. Integration tests are more like it.