I do not need patterns in my career as Java developer because I think I mastered Java before the patterns book became available. But I am not hate patterns and think they have their place where they are needed. That said many manager to not share my view of patterns and think I am some sort of weirdo but I think they should rather take the time to view developers as a whole rather than queeze them into a check list of skills they think they need.
Mike Clark's blogs and presentations made me start wring code with test driven development. This is the report of my first attempt to use TDD professionally and I succeeded.
Is a scenario with SLSB -> SFSB meaningless or is the a valid use case? I will show a scenario that hopefully does make sense.
An permanent failure in an J2EE application can cribble the server or at least drain the system resources but it also makes it very difficult for the administrator to find the source of the problem because there is no talk back by the Bean reporting problems to the server.