After reading CrazyBob's article
about sudo closures in java some time ago I made it a point to familiarize myself
with this particular idiom as well as others that are often talked about but rarely
used within the java community. Unfortunately some time passed and as most things
this todo slipped my mind until I stumbled upon this article.
In my current project, there are several new solutions to some old patterns and there are also several new patterns, which were created to provide better performance and efficiency for the system. In this blog, I will attempt to provide you with information regarding each of the following patterns. Later blogs may include the details of why they were chosen, how they were put together, any problems that were encountered, and how those problems were solved.
The best book I readed concerning Patterns.
Component Frameworks have a lot to offer, but they need to encourage simple mapping between user requirements and the implementation of the requirements. Business Form oriented input validation can help.
I had an impressive Swiss Army knife when I was a kid, but I never did use all the blades.
How does the situation affect the nature of the software you build?
Architecture, reuse, declarative programming, etc. -- it's all about the language.
Using a mock JNDI context for testing is a great idea, but what happens when you're not responsible for creating the context?
A neat office for programmers
Later this month there are two conferences worthy of attention, and neither is mainstream.
My name's Dick Gabriel. Sun's stance toward Java has always been complex, but don't confuse intentions with execution.