Travels etc.

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi...

It’s hard to underestimate importance of planning. It is (or should be) integral part of any conscious activity that requires more than 1 step and implies a target. Especially when we deal with complex processes of various kinds. Contemporary prejudice about planning is that it’s only relevant to big projects like construction, IT, space exploration, military operations, massive production etc. However any activity that involves setting up a goal and steps to achieve it requires planning. Why is it necessary? Because we need to: 1. Estimate approximate date/time to reach the goal 2. Understand what/who is required to achieve the goal 3. Measure success or failure 4. Review and adjust the plan if needed. So planning may help not only at work, but also in personal life which will in turn positively influence our so-called work-life balance. Planning should only serve one purpose – reaching as close as possible to the target. Very often this idea is being overlooked and burie...

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like...