26. November 2013

There is more to C 2013 – slides

Slides available in formats: PDFSlideShare

20. October 2012

Observation of software system: Starting with idea

Idea. Idea is starting point for life of software system. Pure raw idea and vision of future able ignite spark of hope that new software could work.

First stages of system evolution are very vulnerable. Idea need to form protective shell from enthusiasts who are helping to grow it. Idea also needs power and resources to survive. Enthusiasts must form some form of protective structure. It could be startup.

Idea is safe for the time being. It starts growing and eating more and more resources.

Time is passing. Enthusiasm is depleting. Dwindling resources could barely support life of idea.

Key turning point. Idea must transform into system which is able to sustain next phases of its life. It must turn into the system which is able to acquire new resources. Sell or bankrupt.

Luck, serendipity or deus ex machina. Somehow it starts selling. Early adopters begin to emerge. They like new system. They sense that it could become something great.

Idea is adapting protective its shell. Startup is no longer viable solution, because original enthusiasts are nearly exhausted. They spent many many hours and sleepless nights to push this idea forward.

Idea is transforming startup shell into company shell. First it is small, but it is growing.

Transformation will take some time. Software system is growing and consuming more and more resources. Balance of income and consumption is critical for survival of idea.

Maintenance. Software system has been around for several years. Idea prospers. New things were introduced with blinding speed, but this is slowing down over the time.

New changes in software system are causing pain. Idea doesn’t like it.

Idea must protect itself and its system. New defensive processes will emerge. Idea is able to deflect all dangerous changes with carefully designed processes.

System continues to grow and attract more resources. It is obvious that everything is ok.

Unfortunately entropy in software is growing. Hidden. Protected. Old parts of system are becoming legacy.

System starts to deflect even good changes by making them hard to implement. Legacy became so big that there is no way around.

Even minor changes must be introduced with careful precision of surgeon. Adding just one line of code to the system could take several days.

Legacy became burden. Development processes are slowing down. Maintenance is burning tremendous amount of resources.

This is a deadly trap. There is no way out. For some companies it is true.

One approach could be to set aside very high amount of resources. Develop wast change and then deploy it in one BIG STEP. It seems to be right! Welcome to booby trap.

More reasonable approach is to diverge small amount of resources from maintenance furnace. Remove clutter and legacy by small steps in the time. Keep a steady flow.


26. February 2012

Rigid specification vs. anticipation in software development

Software engineers love exactness of computing machines.

Developers often ask for detail specification in order to implement feature according to customer expectation.

It’s impossible to create 100% correct requirements. Customer “moods” are changing and it affects requirements.

Developers are puzzled when requirements are changing every day.

Software engineers were implementing exactly what was written in requirements. The next day they have to adapt to new requirements and half of previous work is nonsense in the context of new day.

The question is: How to face change in requirements?

One way is to put everything into requirements, build protective walls from corporate processes and invoke bureaucratic machinery against any deviation from predefined path. Defend current status quo at all cost…

Then you better start swimming or you’ll sink like a stone
For the times they are a changing

What is the other way? Use anticipation and imagination. Build the software in adaptive fashion. Prepare it for change.


The first step is to admit that requirements are incomplete and that it does not mean that they’re bad.

The second step is to see a bigger picture and to find understanding for customer behavior.

Anticipate rather than react.


28. November 2011

28.11. 2011 – There is much more to C++ – slides

27. August 2011

Try to create aux.h file on Windows 7

Try it 🙂

I was playing with one package from Linux. I grab source code of package using Cygwin. This source code contained one funny file: aux.h.

Windows version of Vim refused to open this file with error message: Permission denied.

Even Notepad refused to open this file.

Finally Visual Studio gave me interesting hint about this aux.h file name:


I tried to zip this file by 7Zip and extract it back. Result was that 7Zip decompressed file as _aux.h.

Interesting issue. 🙂