Welcome!

... to the digital home of Steven Schwenke.

This site is supposed to be a showcase for my thoughts about software engineering, less a personal homepage. If you want to know more about me, invite me to a beer.

 

Global Setup Strategy

01 Dec 2012
Posted by Steven

Recently, I began reading Clean Code by Uncle Bob (again). In chapter 11 ("Systems"), he writes about a "Global Setup Strategy" of an application. As I understood it, it is the master plan for instantiation of objects and the references between them. Following such a strategy should separate the construction of a system from its usage.

Hibernate: "Missing column id"

27 Nov 2012
Posted by Steven

This article covers a problem I encountered using Hibernate 3.0 and Spring 2.5.6.

Yesterday, I spend one hour to debug the following error from the Hibernate Schema Validation:

Using Dependency Injection

18 Nov 2012
Posted by Steven

One topic of discussion I encountered in every project so far is the “right” usage of Springs Dependency Injection (DI). In this article, I want to describe how this controversial feature is used in my current project.

SVN blame vs comments in code

12 Nov 2012
Posted by Steven

The other day I had a discussion with a coworker about comments. Often he annotates the parts of the code that he writes with his name / SVN name like this:

  1. // EXBLUB1

The reasons for this are:

Cutting edge vs Legacy Systems

11 Nov 2012
Posted by Steven

Recently, a colleague asked me, if I still enjoy being in the new team. I immediately answered that with an honest “yes”, although we both agree that our project is far away from the cutting edge of new technology. My coworker said that it is understandable that young developers rather want to play with new frameworks and new languages instead of building a Swing application like we do. Additionally, our project also is not a green field. It has been around for years.

How I deal with TODO comments in code

04 Nov 2012
Posted by Steven

„TODOs are jobs that the programmer thinks should be done, but for some reason can’t do at the moment. It might be a reminder to delete a deprecated feature or a plea for someone else to look at a problem. It might be a request for someone else to think of a better name or a reminder to make a change that is dependent on a planned event. Whatever else a TODO might be, it is not an excuse to leave bad code in the system.”  - Robert C. Martin, “Clean Code – A Handbook of Agile Software Craftsmanship”.

Pages