While developing complex systems lots of failure situations require handling and without proper planning chaos can conquer your code.
A number of simple principles can create order and reduce complexity. And the result can be real software quality.
Good exception handling doesn’t happen by chance. It is designed and planned and when done properly it is one of the main roads to the software “Holy Grail” - quality and reliability.
But leave it to chance and soon all hell breaks loose.
UML lost the programmers. There is no doubt about it… in my mind. And when a software design technology loses the programmers it fades away no matter what the academia thinks. This happened because UML was pushed in a direction that most code writers don’t like: it started to look a lot like bureaucratic paper [...]
The fact that I find flaws in the design of the Java exceptions class hierarchy doesn’t mean I think there is no value in the whole system. Checked exceptions have a positive impact in development. The positive comes from the proactive nature of checked exceptions. They demand attention! And I think this is as much [...]
As I said before, I am a supporter of checked exceptions in Java. I think they are a great idea that supports serious software development in the real world. I also think Java’s huge success can be attributed in part to checked exceptions.
But this doesn’t mean I like everything
|
|
|
|
|
|
|