Wednesday, 20 April 2011

Drive me to the moon - in your Audi A6

I was just picked up from Malaga  airport by the usual taxi driver, is his Audi A6 estate- I've been travelling with him for years and asked how his car was holding up - I remember him getting it new a few years ago.  It still is spotlessly clean, and drives silently on the motorway.  I was amazed to learn the car has driven over 567,000 kilimeters - thats more than the distance from the earth to the moon! It's never had a problem and only ever needed its regular services and expected consumables.  

Even more amazing, his previous A6 was traded in with more than a million kilometers on the clock!

Vorsprung durch technic indeed!

Posted via email from markfaithfull's posterous

Friday, 18 December 2009

10 Commandments of Email (Improving your Outlook)

Improve your Outlook: How to use Email

or

The Ten Commandments of e-mail

Our business is awash with email, but we don’t communicate very well.  There is a difference between providing data which is meaningless and useful information that can be acted upon.  Consider these Ten Commandments for email, and improve the way we communicate:

1.       I trust you to do your job, you don’t need to copy me in every time you ask someone else to do something.  I trust my team to do their job too- don’t cc me when you ask them to do something- I won’t chase it for you; that’s between you and the person you contacted.

2.       If you want me or my team to do something, ask directly in the email, don’t just copy me on a message relating to the subject and expect me to work out what you want.

3.       Use the @NAME convention when you want different people to pick up actions from an email. Eg Customer X has reported a problem with the system, @FRED can you call them and find out exactly what it is @BILL can you check our logs to see if we can see a problem at our end.

4.       An escalation is a direct email describing the problem and actions to be taken; it is not sending an email to someone else and cc-ing the world. You are managing the situation so you need to think it through and email your analysis as a status update- I don’t need to know every action you are taking. Like I said, I trust you to do your job.

5.       For quick updates and messages use only the subject line and prefix it with ‘1:’ to show its a one line message that doesn’t need to be opened

6.       I will assume that I am required to take no action when cc on an email; cc means For Information Only, and it should be used sparingly.  Don’t expect me to react when cc on an email.

7.       Minutes and actions live in formal documents and stored in the project folder on the file server and must never be in the body of an email- attach the document to the email or (even better) put links to the document in the email.

8.       A blind cc (BCC) is almost always the wrong thing to do- deal with the situation a better way

9.       Categorise your email before sending: If you require action from the recipient, prefix the subject with ‘ACT:’ making it easy to identify those emails that require action. If the message really is just for information, prefix the subject line with ‘INF:’

10.   Pick up the phone more often and speak to me

Posted via web from markfaithfull's posterous

Thursday, 17 September 2009

iPod Nano is Harry Potter's Camera

Apple changes the world again, but this time no-one appears to have noticed.

When apple released the first all in one imac, personal computers
changed forever - legacy interconnects died and USB took over the
world. And, how a computer looked became important- allowing the home
pc to move out of the study into the living room and bed room.

The iPhone turned phones into pocket computers in a way psion only dreamed of.

The iPod nano has a camera - millions of teens and young adults will
get a nano for christmas and have a decent (enough) camera in their
pocket every day - better than many phones and penetrating further
into the population than the high end phones with decent cameras (like
the ones made by sony).

The iPod nano has a camera that only takes moving video.

The iPod nano has a camera that does not take still images.

Now given that to make a movie you have to take still photos at about
24 times per second - the reason why the nano doesn't take stills is
because Steve said he didn't want it to.  What does he know that we
don't.

This christmas millions of homes will record christmas on their IPod
nano not as a series of stills but as moving pictures - long and
short.

Will next years photo album look like Harry Potters with all the
images being a 2 or 3 second moving image on a loop?

Steve thinks so.

Posted via email from markfaithfull's posterous

Wednesday, 26 August 2009

Posterous - a neat tool

So Posterous (www.posterous.com) looks like being a really neat tool - I've sent an email to post@posterous.com and this update will show up on on twitter, facebook and my blog- and if a photo was attached it would also go to my flickr account.  It also require zero setup to start using, the only work is if you want to start syndicating your content out to other social sites like I am - you could just use it as a blogging platform.

Still trying to decide exactly how cool and useful this is- but it definitely has potential!

Posted via email from markfaithfull's posterous

Monday, 24 August 2009

A meme to far

A recent trending topic on twitter was #songsincode and the best I saw was the immortal:

zzymyn if (false) { giveUp(you); letDown(you); runAround(you); desert(you); makeCry(you); sayGoodbye(you); lieTo(you); hurt(you); } from user zzymyn on twitter

For more of this madness, go to: http://songsincodedb.com/

Sunday, 9 March 2008

Failure is not an option - part II

In the previous post, I shared some of the story of Gene Kranz, NASA Flight Director for the Apollo 13 mission (Houston we have a problem, and all that).

For the mission specialists and engineers working to save those astronauts, failure simply as not an option.

Have you ever considered that Failure is not an option for Christians either?  Not that we have to work hard to avoid it- but rather that failure is not one of the options God will permit for us.

Look at some scriptures:

the LORD was with him [Joseph] and that the LORD gave him success in everything he did Gen 39:3 NIV


Carefully follow the terms of this covenant, so that you may prosper in everything you do. [said Moses] Deut 29:9 NIV


Then you will have success if you are careful to observe the decrees and laws that the LORD gave Moses for Israel. Be strong and courageous. Do not be afraid or discouraged. [Said David to his son Solomon] 1 Ch 22:13 NIV


As long as he [Uzziah King of Judah] sought the LORD, God gave him success. 2 Ch 26:5 NIV


This is what Hezekiah did throughout Judah, doing what was good and right and faithful before the LORD his God. 21 In everything that he undertook in the service of God's temple and in obedience to the law and the commands, he sought his God and worked wholeheartedly. And so he prospered. 2 Ch 31:20 NIV


 2 But his delight is in the law of the LORD,
       and on his law he meditates day and night.

 3 He is like a tree planted by streams of water,
       which yields its fruit in season
       and whose leaf does not wither.
       Whatever he does prospers. PS 1 NIV


So you can see from these examples, God promises success and the histories in the Bible demonstrate success for God's people.  But don't miss that condition in many of these scriptures, success comes at a price - whole hearted pursuit of God.  This really is Seek first the kingdom in action.  

Sunday, 10 February 2008

Failure is not an option

In 2002 a star struck young Trekkie by the name of Mark Faithfull had the honour of meeting and interviewing Gene Kranz, NASA flight director for the Apollo 13 mission.  This is his story...

MF: The catch phrase: “Failure is not an option.” really strikes a chord.  I remember it distinctly from the film [Apollo 13], and it’s also the title of your book.  Where did it come from?

GK: Actually it was not a phrase that I originated.  I use it nowadays but as we were finishing up our work in the mission control centre, this is about three hours after the explosion, I had formed up my Tiger Team, and I gave them a brief speech but it basically said: “We’ve never lost an American in space and we sure as hell aren’t going to lose one now.  When you leave this room you have got to believe, your team has to believe, that we are bringing this crew home.  Now go make it happen!” And this was apparently too long for the people who did the script for the movie so they translated that very long statement into a single catch phrase of: “Failure is not an option.”  

MF: Reading your book, which I enjoyed very much, you often talk about people who inspired you personally or who mentored you.  Do you think that’s very important for technical and professional people to have a mentor within their working life?

GK: I think that as an individual, as a team member, and as a leader, they need mentors.  But mentors really exist all over.  If you read between the lines in my book, you’ll find that the first boss I ever worked for in flight test, a gentleman by the name of Harry Carroll, taught me enthusiasm.  The man who taught me to fly taught me trust.  Ralph Saylor, who was my boss at Hollomon Air Force Base, taught me about accountability and responsibility. Chris Kraft taught me to accept risk.  So basically mentors exist all over.  It can be your co-workers.  It can be teachers in school.  It can be people that you read about, and what you have to do is you have to form an open mind that allows you to accept this lesson from this broad range of people.  I think most people think of mentors as somebody who is going to simply be a godfather to them.  They’re going to carve out their role in technical and professional life, but what they have to do is they have to just be like a sponge.  They have to listen, listen, listen, and they’ll start getting these lessons in mentoring from the people around them.  

MF: Thinking about what Kennedy said when launching the Apollo program, “we choose to go to the moon.”  That gave you and your entire team a very clear mission, a very clear goal and objective for the program.  Do you think it is an important thing for large projects to have a very clear - even inspirational - goal?

GK: Well yeah.  And there’s no question that it was not only an inspirational goal, it did several things.  First of all it really set what I would say impossible dreams out in front of us.  This is the Camelot kind of a goal that says: gee whiz in our lifetime we are the ones lucky enough to be chosen to work this program that’s going to take us to the moon.  It also set a deadline that said, within this decade.  And Kennedy also used the term, “We’re doing this not because it is easy but it’s because it is hard,” and he recognized the difficulty that we faced, and then he followed on by saying, “because this goal will then cause the best of our abilities to move forward.”   

This post is an extract from an article by the author previously published in 2002 in The Connection, the journal of ITUG the independent user group for HP NonStop Servers.

You can buy Gene Kranz's excellent autobiography Failure is not an option from amazon here