21 Dezember 2006

During a project there are often discussions about maintainability. Often between people that never maintained any application in their hole life!They speak about loosly coupled systems with high cohesion. They do wired things such as converting an object at every interface boundry. (How should one find the usage of this object?)The only thing to get an maintainable application is to keep it simple an DRY!

If you can use Ruby on Rails it's easy. But if you have to use Java don't overdesign your application with abstract classes or interfaces. Don't use transfer objects or other usless stuff!All you normaly want to do is to present the data from the database to the user. So why should you create an integration, a business, a service and a client layer?

Try to come back to nicely designed object oriented applications with as few code as possible!

15 Dezember 2006

Open-jACOB is a RAD Tool that generates web applications.Anybody how's familiar with Access will be able to use it immediately.It's very simple to use and generates a war-file to deploy to tomcat (or others).Once deployed one can update the application.

I think for RAD it's a great tool and it's also very agile because one can create the forms directly with the customer.

28 Oktober 2006

25 Oktober 2006

Yesterday I started a new Ruby on Rails project at RubyForge called rPlan.

rPlan is a project task planning tool that can be used for every project. It is independent of the project model (RUP, XP, Scrum etc). Tasks can be assigned to developers and they can report their work.

09 Oktober 2006

When you take a closer look at the new Application-Frameworks such as Ruby on Rails or JBoss Seam you will notice a change to previous architectures:

The domainmodel is no longer a pure datacontainer, but it contains the businesslogic as in the early years of OO.

For many datadriven applications there will be an advantage that you can ommit an unnecessairy layering. Thus the logic for one entity will be in this entity and you can avoid codeduplication. Your will be more DRY (don't repeat yourself).

I'm wondering how you think about this trend and if anybody has allready implemented any bigger project in this meaning.