I have made this [letter] longer because I did not have the leisure to make it shorter
- Exceptional Strategies
Microsoft's C# language does not include an equivalent of Java's checked exceptions. Does this encourage lazy and error-prone code or is it an astute recognition that Java's checked exceptions are more trouble than they are worth?
- Evaluating Technology for Enterprise Systems
Technology should always be selected on its merits; what advantages/disadvantages are there in using a particular technology. To put it another way; what risk does a specific technology introduce/mitigate in a project?
- Of Splash Screens and Tips of the Day
If I ruled the world, which admittedly is probably not a good idea, software whose splash screens worked like this would be banned and its developers made to serve several months of community service as an apology.
- Resolving Mutual Dependencies with Interfaces
Even in modern langauges such as Java and C#, mutual compile-time dependencies between classes can cause build problems when they cross package, namespace or component boundaries. While not the only solution to this particular problem, Java-style interfaces provide a means of reversing the direction of compile-time dependencies.
- Can/Check Operations in Problem Domain Classes
There is a simple coding convention that can be adopted by PD developers that makes enabling/disabling controls in the UI easier.