Ben & Roz Zander in SA next year!

Hi all-

I just received this via email. I saw Ben and Roz when they were here in August, and it was the most uplifting and amazing experience. If you can get to see them I highly recommend that you attend.

I will post more details closer to the time.

Craig

————————–

Ben & Roz Zander have agreed in principle to return to

South Africa

during August 2008. I am currently working with them to finalise dates and an itinerary.

They are particularly keen to do work within organizations (and with leadership teams). If you would be interested to have them work with you, your management team or other people within your organization, please let me know ASAP. My personal recommendation would be to plan a session with Ben & Roz as part of the leadership development programme in your organization.

Please have a look at www.benjaminzander.com ? you will enjoy the blogs about their 2007 trip to

South Africa

!

We are also talking to Ben about working with our local orchestras. There may therefore be sponsorship opportunities associated with this trip ? please let me know if you are interested (or if you know someone else who may be interested)

Please forward this note to anybody who may be interested in this amazing opportunity!

Warm wishes

Louise

[email protected]

Is lack of communication killing us?

A few days ago a colleague of mine committed suicide. It was completely out of the blue, leaving many people very shaken at what happened. He had a good job, a nice house, a brand new car, and seemed to have so much going for him.

I find it really difficult to understand why somebody who was doing so well for himself decided to end it all. What was happening? Did he have nobody to turn to? Of all his friends, family and associates, was there nobody that he felt he could speak to, to share his problems with?

There must have been things going on in his head that were not showing on the outside. Things that he was bottling inside of him, until he could no longer take the pressure, and exploded in a very tragic manner.

I wonder what would have happened if he had somebody ? just one person ? that he could share his worries with. Would he still be here, or would we still be saying goodbye?

I find it very sad that in this modern world of instant messaging, emails, cell phones and sms we still are failing to communicate with each other. Is it that we are forgetting how to communicate to such an extent that when we really need it, we are unable to do so. Is the modern technology and modern lifestyle making it easier to communicate, or are we forgetting how to communicate to such an extent that when we need to, we simply cannot?

This is one of the reasons that I am so passionate about helping people to communicate ? because we are forgetting how to do so when we most need to be to do so.

Speaking at Big Idea Conference

I have two speaking commitments coming up, both at the annual series of conferences of the Big Idea. The first is on 8 May in Stellenbosch. The second is the very next day, in Claremont at Kelvin Grove. I have the 12 to 1 timeslot on both programmes.

The Big Idea focuses on entrepreneurial skills, and is run by SA Business Hub, so it looks to be a good event.

So, if you want to hear my slant on the benefit of communication and leadership skills for the entrepreneur, you know where to go!

You can find out more and register at http://www.thebigidea.co.za/.

Craig

The 10 Lies Software Developers Tell

Program_code1) My code is better that yours. Writing code is very much like writing a song or painting a picture. Artists and song-writers have different styles of painting or song writing. Writing code is similar, different software engineers have different coding styles. So, unless your code is really badly written, my code is no better than yours, it is simply different to yours. If my code works and does not require any enhancements, leave it alone, no matter how different to yours it is.

2) It works on my machine…well, if it works on your machine and not mine, then clearly it is not a robust application, or your installation procedure does not work very well. Remember that you wrote it on your machine, so of course it works on your machine. Now get it to work everywhere else.

3) I’ll comment the code at the end. The end of any development cycle is always chaotic, that is a simple fact of software engineering. So, if you have not got time to comment your code while you are writing it, how are you going to have the time at the end? Besides, if it is a large project with a long development time, are you going to remember what some of the earlier written (uncommented) code does!

4) I’ll add the error handing at the end. Error-handling is part of the basic design of a system, not something you slap on at the end when you have time.

5) The programme is complete – but I just need to quickly finish off…..This is a very common one. The development is not complete until you have finished writing all of the code. If you have a single line of code to write, it is not complete, and not ready for testing.

6) It is a small bug – it will only take 5 minutes to fix. By the time you have load the development environment, identified the bug, fixed, tested and rolled out the change to production, it will be much longer that 5 minutes. There is no such thing as a 5 minute to fix bug.

7) I only have to change one line of code to fix the bug. To the customer, it does not matter weather it is one line of code, or one hundred lines of  code. All the customer cares about is that the application is not working. Fix it!

8) It’s not my problem. If your application is not working – it is your problem. It does not matter if RightFax is down and you cannot print faxes, or you cannot connect to the FTP server. The fact is that if your application is not doing what it should be doing, you had better find out what the cause is, and resolve it.  While different people may have ownership of different portions of a software system, you are ALL responsible to ensure that everything is working.

9) The application works fine with my test data. Yes it might, work with the test data, but the live system does not run on test data. It runs on live data. Best you get your application to work with live data.

10) It’s a user error. If the user is clever (or stupid) enough to break your application, it is not robust enough. You need to anticipate all user inputs, and cater for them. If at a later stage you find another user error, modify your code and test cases to check for it.

And a bonus lie…

11) Of course I test my own code. Do you? Really? Promise? Ok, then let me try to break your application.

Radio Shack Employees laid-offs by email

EmailfiredAccording to Manager Tools, Radio Shack recently laid off 400 employees via email. Is this a sign that we live in a time that it is acceptable to terminate employment via email, or is it a case of poor judgment?

I think the latter. How can you possibly justify such weak leadership and lack of integrity? Were they too afraid to face 400 employees and tell them that their services were no longer required, or were they too afraid to deal with the issue face-to-face?

I am sure that the author of the above cartoon was being tongue-in-cheek about our modern world, and how email has become core to our ability to communicate, but how sad it is that the author was so close to the truth.

Imagine arriving at work, switching your PC on and checking your email, only to find an email effectively telling you to clear your desk. Being laid off is a frightening experience for many people, but it does very little for your ego that they didn’t even bother saying so face to face.

I  have to ask what sort of example you are setting for the employees that remain behind. What sort of respect or faith will they have in their managers (or dare I say it, leaders).

Radio Shack have broken several of the key rules of leadership, namely to act with honesty, respect and integrity towards your employees.

Be honest as to what is happening.

Treat the employees with respect, and like human beings. It is a very difficult time for them, and they need to be treated respectfully and with dignity. Explain what is happening and why. Give them an opportunity to respond, and explain what the future options are.

According to Encarta, integrity means "the quality of possessing and steadfastly adhering to high moral principles or professional standards". In other words, act professionally and treat everybody like people, and not machines.

I hope that this is a once-off occurrence, and is not an indication of things to come.

In closing, I have to wonder what poor management decisions from the past have led to Radio Shack having to lay off the employees in the first place.