Mojo Old Bank is my local, and Matt and the team there make an absolutely fantasic cup of coffee. If you live in or are visiting Wellington, you must stop by Old Bank and give it a try.

According to the Mojo Coffee website, I count 16 cafe locations in NZ, however I know that Mojo have recently taken over the catering at Wellington Zoo, and news on the Wellington Zoo website states there are 20 Mojo locations nationwide. I’m just waiting on Mojo to confirm all the locations for me, and below is the offical list I will be working off, which I will add too as needed. Thanks to James from Mojo for providing the updated list of locations below. I will update if any new locations open as well. James also tells me a new Mojo website is on the way. Cool!

I will take a photo of myself at each location, hopefully I can get the staff to oblidge and get them in there too.

Auckland
National Bank Towers Lobby, 205-209 Queen Street [ Done 14/04/10 ]

Palmerston North
Shop 109 The Plaza, 84 The Square, Palmerston North [ ]

Wellington
Factory, 23 Kent Terrace [ ]
Bond, 18a Bond Street [ ]
Invincible, 161 Willis Street [ ]
Old Bank Arcade, Lambton Quay [ Done officially 26/03/10. Unofficially most days ]
State Insurance Tower, 1 Willis Street [ ]
Summit, 184 Molseworth Street [ ]
Wakefield, 182 Wakefield Street [ ]
Kumutoto Plaza, Wellington Waterfront [ ]
Gilmer, EDS House, 8 Gilmer Tce [ Done 24/03/10 ]
Wellington Airport, Level One, Main Terminal [ ]
Wellington Airport Lounge, Level Two Main Terminal
Terrace, 119 The Terrace [ ]
Wellington Zoo, 200 Daniell St, Newtown (plus there’s the Tuck Shop inside the Zoo) [ ]
Coffee Central, Shed 13, 37 Customhouse Quay [ ]

Christchurch
Oxford, 137 Armagh Street [ ]

Dunedin
Princes, 329 Princes Street [ ]
Wall Street Mall, 209 George Street [ ]
Wall Street Mall Kiosk, 209 George St [ ]

So I decided to make my own in Adobe Illustrator and provide it free for anyone to download and use, for any purpose whatsoever, and for free.

Use this as you wish, all I ask is that you do not pass this off as your own work or charge anyone for the use of this file. It is distributed freely.

New Zealand Map Vector Shape (.ai Format – For Adobe Illustrator)

New Zealand Map Vector Shape (.pdf Format – For whatever, in Vector  based)

This post applies to New Zealand systems only, as the recommendations are based on the current New Zealand Number Administration Deed

Recommendation – Dial ‘7′ for internal

I have found that ‘7′ seems to be the least common start digit for local NZ Number (The exceptions being a couple of regions in the 03 and 06 calling ranges – see caveat below)

It is my suggestion that you use ‘7′ to lead all of your internal number on your system. The reason for this is with nothing else in this range external to your organisation, it is an easy way for you to destinguish internal and external calls at the dialplan level, speeding up dialing at the endpoint, and eliminating the need for a number to access an ‘outside line’.

Use ‘7′ for all of your internal destinations, not just extension numbering, but any other dialable numbers like ring groups, hunt groups, PBX Features like Voicemail, Directory etc., IVRs and anything else dialable. Plan your numbering in advance and keep it Consistant (Same number of digits).

As a guide, assume that you may need up to 2x the numbering space as you expect to have users. This includes remote users or users who share desks. Use headcount rather than desk count here. Plan ahead – Don’t create extension space for 50 users if you know (Or even imagine) the organisation could have 500, or even 5000 users some time in the future. You don’t want to have to re-number every extension in the organisation at some point in the future.

The below table should give you an idea of the lenth you should make your numbering ranges, based on how many users you expect at peak

Caveat: If you are in one of the few local calling area where there are local numbers starting with 7 you will need to modify this strategy. My recommendation would be to either A) Require area code dialing on all calls, local included or B) Modify your dial plan to allow for the additional digits required to have local and extension numbers in the same rule. This would mean, depending on your setup, you may need a timeout to start dialing on the shorter extension numbers, or if your device allows it, press # or ‘Dial’ to proceed the call.

Most of what I found was solutions of how to integrate feeds of tweets of followers (Like what you see yourself when logged into Twitter) or the latest public tweets from everyone on Twitter. What I ended up using was kind of a mashup of what I found on various websites, tweeked to display what I wanted.

Below is a quick guide to get you up and running with the same sort of things I had (This new WP Theme has a Twitter module so the page was no longer needed in my case) which is a list of my 10 most recent Tweets, in Descending order.

I don’t claim to know alot about exactly how the code works, but I gather that it uses the PHP CURL Library to parse XML data from an RSS feed of my latest Tweets.

1) Set your Timezone. This is so that the time displayed under the Tweets matches your locale.

<?php date_default_timezone_set(“Pacific/Auckland”);

2) Copy and Paste the following code somewhere above where you want to display the tweets. This block pulls the RSS feed and extracts the XML data into an array (I think)

//Get Twitter Info
$login = “<TWITTER_USERNAME>:<TWITTER_PASSWORD>”;

$tweets = “http://twitter.com/statuses/user_timeline.xml?count=10″;

$tw = curl_init();

curl_setopt($tw, CURLOPT_URL, $tweets);

curl_setopt($tw, CURLOPT_USERPWD, $login);

curl_setopt($tw, CURLOPT_RETURNTRANSFER, TRUE);

$twi = curl_exec($tw);

$tweeters = new SimpleXMLElement($twi);

$latesttweets = count($tweeters);

?>

3) The following block of code diplays the Twitter logo (Get a copy for yourself) and also your current Twitter Avatar. The CSS I used isn’t included here but you will probably want to workout your own layout anyway.

<br />
<br />
<div class=”TwitterHeaderRight”><a href=”http://twitter.com/<TWITTER_USERNAME>”><img src=”<?php echo $tweeters->status->user->profile_image_url;?>” width=”48″ height=”48″ class=”NoImageBorder” longdesc=”http://twitter.com/<TWITTER_USERNAME>” /><img src=”images/twitter-logo.png” alt=”Twitter Logo” width=”210″ height=”49″ class=”NoImageBorder” longdesc=”http://twitter.com” /></a><br />
&nbsp;<TWITTER_USERNAME>&nbsp;&nbsp; <a href=”http://twitter.com/<TWITTER_USERNAME>”>Follow Me on Twitter</a></div>
<div class=”TwitterHeaderLeft”>

4) This last block of code is a loop which echo’s your last 1o Tweets. Tweek as needed.

<h1><em>My Latest Tweets</em></h1>
</div>
<div>
<?php
foreach ($tweeters->status as $twit1) {

$description = $twit1->text;

$description = preg_replace(“#(^|[\n ])@([^ \"\t\n\r<]*)#ise”, “‘\\1<a href=\”http://www.twitter.com/\\2\” >@\\2</a>’”, $description);
$description = preg_replace(“#(^|[\n ])([\w]+?://[\w]+[^ \"\n\r\t<]*)#ise”, “‘\\1<a href=\”\\2\” >\\2</a>’”, $description);
$description = preg_replace(“#(^|[\n ])((www|ftp)\.[^ \"\t\n\r<]*)#ise”, “‘\\1<a href=\”http://\\2\” >\\2</a>’”, $description);

echo “<br /><div class=’TweetText’>” . $description  . “</div>”;
echo “<div class=’TweetFooter’>” . date(“M d Y H:i”, strtotime($twit1->created_at)). ” ” . “NZST from “, $twit1->source;
if($twit1->in_reply_to_screen_name != “”) echo ” in reply to <a href=’http://twitter.com/” . $twit1->in_reply_to_screen_name . “‘>” . $twit1->in_reply_to_screen_name . “</a>”;
echo “</div><br /><hr class=’TweetHR’/>
“;
}

curl_close($tw);
?>

<a href=”http://twitter.com/<TWITTER_USERNAME>/”>More of my Tweets Here</a>

You can of course customise any of this to your own needs, and even use some of the different Twitter feeds the API provides depending on your needs.

The Full Code:

<?php date_default_timezone_set(“Pacific/Auckland”);

//Get Twitter Info
$login = “<TWITTER_USERNAME>:<TWITTER_PASSWORD>”;

$tweets = “http://twitter.com/statuses/user_timeline.xml?count=10″;

$tw = curl_init();

curl_setopt($tw, CURLOPT_URL, $tweets);

curl_setopt($tw, CURLOPT_USERPWD, $login);

curl_setopt($tw, CURLOPT_RETURNTRANSFER, TRUE);

$twi = curl_exec($tw);

$tweeters = new SimpleXMLElement($twi);

$latesttweets = count($tweeters);

?>
<br />
<br />
<div class=”TwitterHeaderRight”><a href=”http://twitter.com/<TWITTER_USERNAME>”><img src=”<?php echo $tweeters->status->user->profile_image_url;?>” width=”48″ height=”48″ class=”NoImageBorder” longdesc=”http://twitter.com/<TWITTER_USERNAME>” /><img src=”images/twitter-logo.png” alt=”Twitter Logo” width=”210″ height=”49″ class=”NoImageBorder” longdesc=”http://twitter.com” /></a><br />
&nbsp;<TWITTER_USERNAME>&nbsp;&nbsp; <a href=”http://twitter.com/<TWITTER_USERNAME>”>Follow Me on Twitter</a></div>
<div class=”TwitterHeaderLeft”>
<h1><em>My Latest Tweets</em></h1>
</div>
<div>
<?php
foreach ($tweeters->status as $twit1) {

$description = $twit1->text;

$description = preg_replace(“#(^|[\n ])@([^ \"\t\n\r<]*)#ise”, “‘\\1<a href=\”http://www.twitter.com/\\2\” >@\\2</a>’”, $description);
$description = preg_replace(“#(^|[\n ])([\w]+?://[\w]+[^ \"\n\r\t<]*)#ise”, “‘\\1<a href=\”\\2\” >\\2</a>’”, $description);
$description = preg_replace(“#(^|[\n ])((www|ftp)\.[^ \"\t\n\r<]*)#ise”, “‘\\1<a href=\”http://\\2\” >\\2</a>’”, $description);

echo “<br /><div class=’TweetText’>” . $description  . “</div>”;
echo “<div class=’TweetFooter’>” . date(“M d Y H:i”, strtotime($twit1->created_at)). ” ” . “NZST from “, $twit1->source;
if($twit1->in_reply_to_screen_name != “”) echo ” in reply to <a href=’http://twitter.com/” . $twit1->in_reply_to_screen_name . “‘>” . $twit1->in_reply_to_screen_name . “</a>”;
echo “</div><br /><hr class=’TweetHR’/>
“;
}

curl_close($tw);
?>

<a href=”http://twitter.com/<TWITTER_USERNAME>/”>More of my Tweets Here</a>

The study is published on the Blackberry website (here) so should probably be taken with a grain of salt for obvious reasons, however I find it’s results quite interesting.

The report suggests that “typical (median) end user converts 60 minutes of downtime into productive time per day” – That is one hour per day that the average user would be being paid for where they are not not productive into productive time – And the survey states they have taken a conservative approach.

For a person on a $40,000 salary, this equates to $5,000 per year of recovered productivity!

There are issues that the analysis does not cover, such as the social impacts of a constant connection to work, but from a business point of view the numbers sure do seem to stack up.

The survey puts the TCO at about $1,325 PA, so if the number are correct, that is a huge benifit to business.

I don’t use a Blackberry myself, any out of office email I do for work is done on a Laptop over a VPN connection. For those of you who DO use one, do you agree with the finding above?