tag:blogger.com,1999:blog-85140682702453709582011-09-16T11:42:55.189+02:00about java, spring, testing and more!Mathiashttp://www.blogger.com/profile/14427765559424337534noreply@blogger.comBlogger31100tag:blogger.com,1999:blog-8514068270245370958.post-83577230645527882342009-04-01T12:07:00.001+02:002009-04-01T12:09:00.874+02:00

Endlich läuft auch mein ubuntu mit der Geforce 8800 GTS richtig schnell:Installing nVidia 180.29 Drivers in Intrepid | Adam Michael Roach

Mathiashttp://www.blogger.com/profile/14427765559424337534noreply@blogger.com0tag:blogger.com,1999:blog-8514068270245370958.post-69165193366056919652008-04-04T17:28:00.012+02:002008-04-05T11:58:39.046+02:00

Writing unit tests can be a boring and time consuming task. Especially for beginners it is sometimes impossible to see the light at the horizon when they start to write tests. The problem is that only a small set of third party libs where really implemented by using TDD. Those libs which do not have a sufficient test coverage are by definition "Legacy Code". The same is true for the code which

Mathiashttp://www.blogger.com/profile/14427765559424337534noreply@blogger.com1tag:blogger.com,1999:blog-8514068270245370958.post-42537898891431146842007-11-16T22:51:00.000+01:002007-11-24T16:16:20.323+01:00

There is no secret that programming java in object oriented style is much easer with the Spring Framework.But what about writing templates for the various rendering issues we have? Right now it is quite complicated to write a JSP template without violating dry. In fact the structure of jsp templates looks more like programming in a procedural way. There are frameworks available which reduces the

Mathiashttp://www.blogger.com/profile/14427765559424337534noreply@blogger.com1