How an IT Director chooses a phone

I've got a new phone, but I thought you might be interested in how a chose my old phone:

 

Let's start with battery life - 10 days on standby, not bad at all.

User interface - apart from one quirk (the "go away" button for a reminder and the alarm isn't the same) it's pretty much perfect. The thing you most want to do is on the top left hand button. So once I've composed a text I can send it to my wife with just 5 clicks on that button (so long as she's first in my address book).

Security - it has no internet access, so it you can't get at my email or into our corporate network. It can't get viruses. As an IT director this is important, so that's a great strength. One flaw - memory isn't encrypted.

Price - This has to be the one thing that clinched it for me - my mum swapped it for my old phone so it didn't cost me anything.

Raspberry Pi - doing something useful

My second most popular post of 2012 was Raspberry Pi in real life and a tiny wireless access point. (The first was the ever popular Firebug equivalent for IE written back in 2007.) My analytics shows that people are searching for Raspberry Pi and access points.

Anyway, I thought I ought to write another Raspberry Pi post. When I got mine I had problems with booting from the SD card. For some reason it would only boot if you put in on an antistatic bag and then used your fingers to short the bag to some of the pins. I got a different card which has worked fine.

Over Christmas I had time to do some more stuff with it. I got the latest Raspbian image which thankfully includes wireless support from an icon on the desktop, rather than fiddling around with firmware and typing arcane commands. I added VNC support, enabled SSH and I was cooking on gas, as they say.

I wrote a script which would detect when the SD card from my camera was plugged in and copy photos from it to the PC where I archive them. When I discussed with someone my plans to do this they pointed out that I would probably spend more time developing it than I would save in doing it the old way (running a script on the PC). However, that's not the point! The interesting thing is finding out how to do it.

Although I've been using Unix for 24 years I don't use it regularly, so it took a bit of digging to find out that mount -t smb is now mount -t cifs. The script is now working, so I need to schedule it with cron and we're away.

Another Blackberry Playbook app

I've developed another Blackberry Playbook app in my spare time. My first one was a bit rubbish, but it got me a free Playbook. My second (GPS to Grid Ref) only did one thing. This one isn't fantastic, but it is a proper game.

I developed it using the Marmalade SDK which targets iOS, Android and the Playbook. There was a promotion where they gave away developer licenses for six months so you could develop apps and if you submitted one get (another) Playbook. The Marmalade tools are really good, making building, deploying and debugging pretty smooth. The SDK has all sorts of libraries which came out of Ideaworks3D Game studios game development.

The game is based upon one of the samples, where a square on the screen moves towards your finger when you tap or press on the screen. Two of my sons, with the Playbook between them, started trying to get the square to move towards them, and the idea was born. My wife gave it the name - Tap Tug of War - and all three sons playtested it. To stop you just holding your finger down I made it so that if you pressed for two long the square, which became a fuzzy blob for the final game, would move away from you. I put a state machine around the game play for the splash screen, game over and restart screens, created some graphics and the game was done.

What would an IT entrepreneur look like in a mission organisation?

A few years ago I was at the conference for IT people in Wycliffe worldwide. There was someone there who had written a really neat program that enabled you to produce a dictionary. (Stop me if you've heard this, but I can't find it elsewhere on my blog.) Someone else stood up and was conflicted by what he'd seen. Whilst tools that do one thing well are great in themselves, there's also a need for getting a group of people together to develop a series of integrated tools. I'm guessing the guy who stood up was somehow involved in, or had a stake in, the team developing integrated tools. I'm all for the consensus and teamwork approach, even though it's painful and slow. However if it's too painful or slow people just get on and develop their own system, like this entrepreneurial person.

I've just been in a meeting planning an IT event next year, and we touched on IT entrepreneurs. It got me thinking about what would a good IT entrepreneur look like in a Wycliffe context?

I can tell you what we don't want:

• We don't want people to come in and set up servers or systems and not leave any documentation behind.
• We don't want people to come in with loads of ideas, and not listen to why we think they won't work, and who give up and go away.

That's not to say that you can't have people who come and do good stuff. I hear good things about the people behind Lightsys.

Here's what an IT entrepreneur might look like:

• They spot a need across several organisations.
• They develop a prototype system that meets the need and open it up to the users.
• The users get on board and nag their management to make this system an official part of the organisations strategy.
• Crucially, they make sure the system is sustainable and now that people are sold onto it, that it continues to adapt to meet their needs.

Just thinking out loud. 

Update: Tom Lucas has posted a thoughtful reply on Google+.
Update 2: This post got picked up on my company blog: IT entrepreneurs in a mission organisation. 

Update 3: Tom has written a blog post on the subject himself.

LASA Charity Digital Summit

("Summit" is a bit grand.) Yesterday I was in London for the LASA Charity Digital Summit (#lasadigsmt on Twitter).

Update: slides and audio are of the digital summit are now available.

The first session was about the Future of Social media, though most of the discussion was about where we are now. One of the predictions was that location would become more important. This ties in with Robert Scoble's latest book idea about "context", i.e. your devices being helpful because they know where you are and other stuff about you. If Robert's interested in something like that he's usually worth following.

My take on location is that apps have to be really smart with it, and give you the warm feeling that you're in control of your data. This isn't new, look at Yahoo Fire Eagle which has been around since 2007, but I've heard no mention of for years.

Then I went to the session Light up Your Digital Campaign. Lucy Buck from Child's i Foundation talked about how she started the charity. Right from the start she was videoing and sharing stuff - she's a TV producer by background. Jude Habib talked about pitching your photos and audio to the media. As they get increasingly short-staffed they are more willing to use your stuff. Peter Gilheany is from an agency and talked about old-fashioned planning of your whole campaign (what are your objectives? who are you trying to reach? what are the best routes to reach them?). It was good down-to-earth stuff. Digital is just one of those routes to reaching people and he made the observation that people use a different persona online to what they might in other circumstances.

After lunch I went to the session on Digital Fundraising lead by Rachel Beer from Beautiful World agency. I have a lot of time for them as their blog is really good at highlighting what you need to know as a charity about online stuff. After some general points she focussed on banner adverts and took us through some good and bad points of some adverts and donation forms from various charities that I won't mention.

It was a good day, and worth the price of a train ticket (as entry was free). I got to meet Paul Webster for the first time, who I've been following on twitter for years, as well as Louise Brown who I've met once before.

Pray101112

I don't get out of the office much, but in the last couple of days I've been out twice. The first time was on Saturday when I was involved in Pray101112. Many Wycliffe organisations around the world have a day of prayer around 11 November, and this year we chose to invite the UK church to join us.

Fortunately the whole UK church didn't join us, as it would have been a bit crowded. We had three venues, Belfast, Coventry and the one I went to in St Albans. We were hosted by Spicer Street church and it was a good venue for the meeting. There were around 30 people, half Wycliffe and half visitors, which was a good balance.

I was doing sound and projection and fortunately it all went fairly smoothly. You can see the videos and powerpoints used here.

Federated identity - using Twitter to log into your intranet at work

Following up on my previous post, here's some stuff to help you get your head around Federated Identity. (The wikipedia article I linked to in that post isn't that good. I wish I head a grasp of the concepts enough to improve it. The one on Identity Management needs even more work.) The video in this blog post Federated Identity 101 is a good start.

Some questions that people might ask have come to mind as I've started thinking about this stuff. Here's the first:

Why can't I use Twitter to log into my intranet at work?

There are a few things preventing this from being possible. Although using existing logins makes life easier for the user the people who provide the systems have justified concerns. (Jargon sidenote: authentication is checking you are who you say you are. Related is authorisation which is checking what you're allowed to do. A service provider is a system you are trying to use.)

So if I'm a service provider running the intranet and the users are asking to use their twitter account, here are my concerns:

• I know that Fred Bloggs is an employee, but how do I know that @FredBloggs (who seems to be doing quite well making money at home) is the same person?
• Even if I do verify that, how can I be sure that Fred Bloggs twitter password isn't easy to guess? If Twitter's password policy is weaker than our existing password policy, then it's like putting a big lock on the front door, and leaving a side window open. Judging by the number of people who have their Twitter accounts hacked, their password protection isn't that strong.
• Even if Twitter's policies are good, then say they remove your account after 6 months of inactivity and someone else signs up with the same username. They the other FredBloggs can log into your intranet even though they aren't an employee.

These issues are all around the issue of identity assurance (apologies if you find italics patronising) and the last one in particular is identity lifecycle.

From time to time I think of this Dilbert cartoon when it comes to the latest Big New Thing, whether it be SOA, Cloud or Federated Identity.

So when your equivalent of the point haired boss comes up to you and says "I think we should build a Federated Identity system", you could ask him what colour he wants it, or ask him about identity assurance.

Edit: Here's the cartoon that Giddie mentioned below: