Skip to main content

Robbie to Dorie: Lt Col John Robertson's letters from Malaya 1941–42

Interesting book for those engaged in Australian and World War 2 history.


Lt Colonel John Robertson of the 2/29th Battalion AIF, a decorated veteran of the First World War, was killed in action in Malaya on 17 January 1942, the first day of his Battalion’s encounter with Japanese forces.
His death devastated his men but they continued to revere Robbie as they endured more than three years of captivity. By contrast, some historians have described him as too old and hide-bound for command, as having lost the confidence of General Gordon Bennett, and as having imperilled his troops by refusing to co-operate with the battery from the 4th Anti-Tank Regiment. Grandson Andrew Warland asks whether the evidence supports such views.

Reproducing the letters Robbie wrote home to his family in 1940–42, he presents a fascinating study of a man who left his family and his business, and ultimately gave his life, to make (in his own words) ‘a better world for us all’.

http://www.scholarly.info/book/393/

Comments

Popular posts from this blog

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

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...

Mastering The Multitasking

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...