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.

Posted by Steven

One of my favorite concepts of self development is mentoring. My current mentor started mentoring me two years ago and has two mentees in total. One of the reasons why our mentoring is so successful is the proactivity of the people involved. Everybody is expected to bring new ideas and topics into the group so that we can learn together and from each other. In this short article, I want to elaborate a recent event that probably prevented me from making a fool of myself in front of a lot of people.

Posted by Steven

One of my weak spots as a developer are estimations. I simply cannot estimate how long a software developing task will take. In this article, I write about how I came up with an estimation to a bundle of tasks, how accurate it was and what I took away from it.

Posted by Steven

Recently, a good friend of mine blogged about Degraph. Degraph is a tool to visualize dependencies between packages. Not only are these dependencies shown in a graph, but the nodes of the graph can be expanded so that dependencies can be traced into packages.

Posted by Steven

In one of my recent articles, I wrote about my experiences in generating an Excel report with Apache POI. I want to  complete my thoughts by summarizing my experiences with the framework.

Working in the zone

02 Mar 2013
Posted by Steven

As you might have noticed, my posts haven’t been as regular as usual in the last time. The reason for that is a new project that needs a lot of caretaking. My first weeks in that project needed some special mental work mode that I will describe in this article.

Posted by Steven

One of my recent assignments included writing an Excel report with Apache POI. This report has nine worksheets that cover different aspects of one business concept. In other words, each sheet gives another view of the business case. After finishing my work on the report, I noticed I made a huge mistake: I didn't optimize local algorithms, which was a good decision. But I also didn't optimize the whole approach on the problem. That turned out to be bad.

Pages