Programming …

This weekend I took some work home with me. I am working on an implementation of a code library for research prototypes. However, during the week I can hardly make any progress. There to many different tasks for me to do (e-mails, meetings, funding proposals, reports, etc.).

Yesterday, I literally took the existing source code apart and started rewriting the internals. Why is it, that you always need to write 60% of a program, before you understand how to do it correctly? Year, I know the software engineering drill. I am an experienced software engineer myself and I know how to develop good code. But nevertheless it does not work. At least it does not work if the program is to complex, or gets to complex because I want to be ready for(already known) future uses. It feels like a special version of Hofstadter’s law: A software design has always problems, even if you consider all problems you know. It really would be a lot easier if software could stink. Then you would know when something goes into the wrong direction.