14 Sep 2002 sdodji   » (Master)

MlView Hacking. I am still busy with the isolatin1 edition support in MlView. There are many many small portions of code to modify and that can lead to many bugs if I don't care.

Question. I definitely hate working in a place were the management doesn't understand that people who write software should 1) maintain it 2)document it so that further maintenance can be made at least possible. Instead, the management only insist on the code production part which is actually the smallest part of the software lifecyle. The greater part of a software lifecycle actually being the maintenance and the evolution. But they totally ignore the good practises that will ease code maintenance and evolution in the future.

They went to an extend where they created some division where people do *only* maintenance.

Readers should keep in mind that there is *zero* code documentation ... so an incredible amount of energy is spend to fix the bugs ...

I do think that one day, the company will just collapse because of their being incapable to roll out new products beacause all the energy is spent on maintaining unmaintainable products. That is very bad.

And as time goes, things are getting worse and worse.

Does anyone share the same experience as me ? Does anyone know how to get out of this spiral ?

Latest blog entries     Older blog entries

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!