- 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
Why kill the spider when you can cut off one of its legs and sell it for $10000?
Admin
Admin
This type of thing happens all the time. Since the consultants that initially consulted with the client were from the crystal citadel, the client agreed to crystal citadel hourly rates, and (reasonably) expected a deliverable worthy of a crystal citadel. What has always happened, and will always happen, is that the CotCCs turn around and give the work to consultants of, say, the mud huts. This way, the CotCCs keep their hefty margin between their crystal receivables and their mud hut expenses. Unfortunately, the client also gets a mud hut deliverable, but by then it's too late. Sure, the client could sue, but that crystal citadel also houses a lot of lawyers...
Admin
This seems reasonable. Copy entire catalog is failure but I can fix that. Just make sure each item in the catalog has an id (primary key), create an Orders table with FK and PK, yeah. I can build a proper database around this no problem, and fix their poor implementation. I'd scrap that "Copy entire catalog" thing in favor of creating a session and storing the necessary information on the client, or perhaps even as an order and have the order's "state" i.e. incomplete stored as well, so you could go somewhere else and log in and "hey you still have this cart."
What's the problem here? It needs some tweaks.