"Change this application, so a customer can have more than one order"
They'd written version one for a land grab, didn't need multiple orders all they wanted was the first one, to prove the concept.
All the way through the design, order and customer a 1 to 1 relationship, in real terms there was no such thing as order or customer, it was some unholy confabulation.
It gets better though, they gave the intial go to one of your newbie clueless types, in fact worse straight out of academia, nice and cheap.
It was a telecomms application, it had no concept of provisioning, the second order some customers wanted was to change their address.....
On top of that the UI design was a multi tab single window, designed from the worksheet they collected the data on, in the same order, which I can assure you was not suffering from any sort of logical organisation.
Better still the guy had obviously missed the class on coupling and cohesion, If you referenced the "customer" module, you had to linlk to another 89 modules for it to build. There were only two more in the entire solution.
Just to cap it off, these pratts did a link to their billing system for producing the entire one invoice for the entire one order, by customer surname...
So come again?
Would you like to here about a highly succssful american business that tried to go multi-national and hired the R&D managers's mate who'd never written a serious piece of software in his life, never used the chosen language , knew nothing about databases, or client server, had two development teams seperated by the atlantic, who weren't allowed to talk to each other, to come up with a system that communicated via xml documents through a flat file only aware mailbox system, that hadn't figured out that we don't routinely use dolloars over here and that america and the UK are different countries?
I've been dealing with this crap since 1987, that's just two examples, glaring ones I'll admit, so still not having it.
Don't tell me my contention is ridiculous by comparing me to people you don't have any respect for either. Go ask them if they think design and implementaton quality have a higher prioity than the colour of the buttons or getting it done yesterday, I'm guessing you won't like what they tell you.
Whether it should have a bit more consideration, that;s a different question, in fact it's the entire reasn behind this thread, something which quite obviously went right over your head.
Go back and read what technical debt is,pay attention to the responses where denying that it exists, doesn't really help much.
Start being part of the solution.
Keep Up with TechRepublic