Battles and Management

Lev Tolstoy in a rare color photo

Have you ever read War and Peace by Lev Tolstoy? It's a great book with many stories wrapped up with History. It is based in Russia during the Napoleon era and, of course, it also tells about battles.

There is one thing in the Tolstoy's point of view that caused me some thinking. More or less, this is the reasoning of the author: most of the times, battles are not decided by generals or strategists but by single episodes of bravery or dastardliness in the troops.

Of course there is a part of truth in this but, as usual, life is slightly more complicated. A good commander should be able to understand if its soldiers are motivated, which are their strengths and their weaknesses. And a good commander always has an ace in the hole.

Victory and Fortune

Many great commanders in the past were undoubtedly lucky and often luck is considered an essential attribute of good strategist and I'm sure you have already heard that fortune favors the bold. But a commander that points everything on its luck is doomed to lose.

This is why, really great commanders always have some troops reserved for difficult moments (for example Napoleon had the Old Guard) and they know when engage a battle and when retire their troops.

For a manager it works the same. If he plans the team at one hundred percent of the time, there will no room for contingencies. If he accepts every job proposed by the salesmen, the risk is to provide a poor job or to miss deadlines. He can put its subordinates under pressure for some weeks but not forever.

Sometimes managers have to take some risk and they can be lucky, but fortune doesn't lasts forever.

books, history, management Sunday, July 06, 2014 No comments

Tab War

Some years ago I've downloaded the ebook "C++ Manuale di Stile" (C++ Style Manual) written by +Carlo Pescio and in these days I'm reading (again) some of its chapters. One of them is devoted to tabs:

[...] in a big project in which I participated, "the length of the tab" was cause of severe tensions, with threats of layoffs and endless discussions. Even in this case, the basic problem was the lack of a standard accepted by all: some programmers defined the tab as eight spaces, other two, other three. In addition, some used only tabs, others used both tabs and spaces.

[...] it's necessary that an internal convention is established and it's respected by every developer. It's better to resolve disputes at the beginning of a project than being in the middle of a civil war when development is in progress.

From pages 56 and 57 - Translation by me

I've already written about the need of a common coding style but, as ancient Romans used to say, repetita juvant.

books, Cpp, style Monday, May 12, 2014 No comments