June 2006

Disturbances

One of my professors once said:

"Disturbances have priority."

Even though the context was different I think it can be applied to (agile) development, too. How?
Development is a team effort and every programmer has to be creative - in the sense of "creating code" and "finding a simple solution". Everything that disturbs this individual and group effort has to be focused on and eliminated forever.
Example: If you find that the old static libs give you trouble (some search paths missing, lost headers, conflicts between version etc) build a framework once and put it under SCM. The trouble will vanish. Otherwise development time is spent on fighting those disturbances over and over again. Once they pop up find a solution that will work.

Book recommendations

I wrote some recommendations on books I like and find useful.

First Tuorial: Pifalls in C

As a first tutorial you will find a short description of possible pitfalls and trips in C in regard to Objective-C based on an article by Andrew König. Take a look at the tutorial.

Start of tutorials

These pages will be filled with lots of tutorials about development and some tips and tricks. This will naturally take some time - so please be patient. Any comments and ideas are welcome!