Forums
Some terrible code arises out of terrible business rules which no one truly understands. Some terrible code arises from laziness, sloppiness, or the need to just get it done now.
But there’s a special class of awful code that arises for a complete misunderstanding of how the language is supposed to work. That gives us things like the loop Rasmus found:
Exceptions are a great source of stress and suffering. Each exception thrown by our application must be caught handled before the user sees it. Failing to do disturbs the balance of our application. We can use a generic exception handler, but we never can be truly certain we’ve found the true exception. So often the Truth is hidden within an inner exception. It may also be hidden within that exception’s inner exception .
To find truth, how deep must we go?
The tension in the conference room was thicker than black pudding and twice as vile. Marc and his boss, Greg, sat on one side of the table. Across from them were the Consultancy Drones, each in a grey suit with a Bluetooth ear-piece pinned to their ears. At the head of the table sat Judy, the project sponsor. Projected on the wall behind her were Gantt charts and dashboards and metrics.
Much of what was on the screen glowed a baleful red.
Managing a long supply chain involves keeping thousands of moving parts in lock-step. From purchasing to order management, demand planning to operations, even the smallest hiccup in the chain can have massive impacts.
So when lowly IT drone Tony got a phone call from the VP of Global Purchasing, he knew there was one hell of a hiccup. “We can’t find records for a thousand product codes in the system!” the VP shrieked down the phone. “We can’t place orders if we don’t know what we need! We’re trying to plan our vendor projects for the next quarter and-”
Jan 13