Development highlights

Last Thursday I finally finished a feature in our product which I've been working on for two weeks.

It was a bit frustrating because the automatic testcases for the product had to be corrected for the new situation but when I fixed the testdata for one case another test freaked out. Back and forward all the time; change data, compile, run 390+ tests (~12 minutes), evaluate error messages and back to the beginning...

But finally I finished it somehow and for my own surprise I only had to adapt the testcases; my implementation of the feature had worked all the time.

Next thing on friday was that I implemented another feature, which I approximated to need five days to develop, full featured (including testcases) before noon. Four hours instead five days. I was very surprised again when I found out that it worked and nothing was left to do for it.

These two things increased my personal motivation quite a bit.

Another thing last week: I saw that several of our quality assurance people had a long talk with our development manager. I have no idea what exactly was talked about but I have a good feeling because recently I often talked to them about our development processes, structure and quality measures. We all quite agree that the current structure and processes are not suitable for development. Our alignment on projects instead of products constrains us more than it aids us.

Along with that thoughts I found a project called GForge which is like the Sourceforge environment. GForge is based on an earlier CVS snapshot of Sourceforge but has been development independly since that time. I thought about if this could assist us in our development and played around a bit with a test-install of GForge, but I'm still unsure... Have to talk to our Quality Assurance people about that. It surely would be neccessary to integrate our installations of TaskZilla and TWiki with it.


Similar entries

These entries are similar to this posting (as of 2017-02-06):