Spiegel und Springer kehren zurück zur alten Rechtschreibung und es entsteht schwupp-die-wupp eine breite Ablehnungswelle gegen die neue Rechtschreibung. Und das alles kurz vor Ende der Übergangsfrist.
Das scheint geradezu symptomatisch für unsere generelle Reform-Unfähigkeit. Vielleicht sollte ich lieber auswandern. Kennt jemand einen Ort, der nah am Wasser liegt, wo das ganze Jahr über Sonne und Wind (mind. 4 Bft.) herrschen und wo man als Informatiker einen Job findet?
When searching for techniques to create Java enterprise applications without buying and using heavyweight products one should take a look at C-JDBC. C-JDBC is an open-source product that supports the RAIDb concept (Redundant Array of Inexpensive Databases): C-JDBC encapsulates several database instances behind a regular JDBC api. To introduce C-JDBC into a project existing code needn’t be modified as long as all database access is handled via JDBC.
Most OO systems claim to be modular but very few really are. Normally OO systems have cycles between they modules. Even if there are no cycles the dependencies between the so called modules are chaotic and inflexible. A typical result is that developers can’t instantiate a small set of classes for unit testing without having the rest of the system.
PicoContainer is an open-source project that provides a IoC-Container (IoC = Inversion of Control) that is very useful for defining and managing the dependencies between modules.
I collegue asked me once when I would PicoContainer into a project:
- Right from the beginning?
- Even for prototyping?
- When the system exceeds a certain size?
I think that projects should use PicoContainer right from the beginning and even for prototypes. Even for very small prototypes PicoContainer pays off measured in Lines of Code and it adds very small overhead to the project.
Adding PicoContainer later to a project results in refactoring and will therefore often not done.
Ganz gute Windsurf-Tipps gibt es hier. Überhaupt ist Alacati ein netter Spot für Ein- und Aufsteiger.
There is an funny and interesting article about EJB out there, called “Don’t Make me Eat the Elephant Again“. The autor argues that for most project EJB ist just too big and suggests some lightweight approaches to building Java Enterprise Applications.
I like the article very much since I know the suffer the author describes from my programming and consulting experience. It is the time for a change!
There is a very interesting book about the topic: Bruce Tate, Justin Gehtland: “Better, Faster, Lighter Java”.
I participated the SCRUM Master training in Karlsruhe held by Joseph Pelrine. That was fun and now I’m a certified SCRUM Master.
BTW: A collegue of mine said that “SCRUM Master” sounds like something evil. I try to be not too evil 🙂
Its always a highlight when profession meets fun. A very funny and striking description of Java’s GridBagLayout is available as an interactive weblog.
I released the first version of JMigrator at Source-Forge as an Eclipse 3 plugin.
If anybody is interested in participating at the further development, please contact me.
Application specific frameworks often degenerate and become Trascan Frameworks. I have written my thoughts in a short article “Trashcan Frameworks“.
Martin Lippert and I held a lalk about Refactorings in large Projects at the Java Forum Stuttgart. The slides are here (german). I submitted a presentation about aceptance testing with Fitnesse. This was accepted as a failover presentation. Since no other presentation was cancelled, the presentation wasn’t held. But the slides are here for download although (german).