If you can read this text, your browser is not interpreting this page as the designers intended. This may be because you are using an obsolete, non-standards compliant browser or you have Cascading Style Sheets disabled. Read more about Web Standards at Reactive.

text size: A- A+

The Digital Bottom Line

Start up Guide Smart Co Awards Smart co blogs
Govt assist Govt assist Links Our Partners New Products

Email Alert

Sign up to receive an email each weekday alerting you to the latest news, tips, blogs, trends and big issues

More information
RSS feeds Podcasts

Last will and testament.exe

Wednesday, 23 May 2007

Last will and testament.exe

My wife and I are at the lawyers, going through our will. The previous lawyer had made a number of mistakes, and then promptly left the firm, so it is up to the principal to fix our issues. The Maserati in his carport tells me this guy is either good at his job or good at charging.

So we go through this list of scenarios, some of which need to be changed, some deleted and some simply moved around in the document to make it easier to understand.

I notice that the lawyer renumbers each paragraph as he moves sequentially along, sometimes having to change the number again as he works his edits into the document. I think this is a very disciplined approach and must have been part of his lawyer training.

However, my wife and I have a large number of additions to make, to cover different situations. The lawyer is surprised we could generate so many additions, but we are allowing for situations he has not considered. It is only afterwards I realise what has happened.

Just as the lawyer relied on his training to move through the document and make edits, I relied on my IT training, which made me approach the document in a totally different way. It wasn’t a computer problem, a software engineering approach made sense. I used a basic programming construction, which probably now has a fancy name, but I call it the IF THEN ELSE decision. Virtually all programming languages have a version.

This construction is used in the following way:

IF condition exists (Say my wife is already dead when I die)
THEN carry out an action (Give everything to the kids)
ELSE carry out an alternative action (Give everything to the wife)

Now the lovely thing about this construction is that one IF THEN ELSE decision can be nested inside another. Programmers then indent the bits of text to make it easier to read. For instance:

IF my wife is already dead when I die
THEN
   IF my children are all over 18
     THEN give everything to the kids
        ELSE give everything to my executor
ELSE Give everything to the wife

What a wonderful thing, software engineering converges into drafting my will. Software constructions can jump straight out of the computer and help me better order thoughts to get a logical outcome. Technical training can benefit the non-technical person.

Now I just have to figure out how to make a DO WHILE loop get me a Maserati.

To read more Brendan Lewis blogs, click here.

Add your comment

Name:
Email:
Comments:


More: The Digital Bottom Line

View > Changing tools, the easy way
Wednesday, 8 October 2008 We sometimes are wedded to certain business solutions by dint of the daunting task changing them presents. It needn’t be that way. BRENDAN LEWIS
View > Living online
Wednesday, 1 October 2008 Smartphones have shown us that we can do so much more online, but they are not the only tools that can help. BRENDAN LEWIS
View > Good advice, easy
Wednesday, 24 September 2008 Advisory boards are an incredibly useful tool that are often overlooked. BRENDAN LEWIS
View > Persuasion plan
Wednesday, 17 September 2008 Is your gain proportional to your pain? BRENDAN LEWIS
View > Eight dark clouds on the horizon
Wednesday, 10 September 2008 I have learnt some heavy lessons from downturns. Here’s eight that might save you. BRENDAN LEWIS
TOP OF PAGE