As I promised, I’ve given this blog a bit of an overhaul in anticipation of posting more often again. For those who are interested, here’s a run-down of the updates: New responsive design Responsive design is all the rage these days; in summary, it’s all about making your site adapt fluidly to the reading environment so it looks good on a variety of devices, even resizing images so they always fit.
Apple kept everyone on tenterhooks this year by announcing WWDC 2012 very late - the second latest announcement ever in fact. Like many other people (11,000 of them I hear, which is alarming given that there are only 5,000 tickets to the event) I signed up to WWDC Alerts, which sent me an SMS message while I was having lunch, only a few minutes after the tickets went on sale. That I was lucky enough to bag myself a ticket has a lot to do with that - about 90 minutes later, they were all gone - so big thanks to fellow Brits Anthony Herron and Aaron Wardle for running that, completely free of charge too.
I’ve been shamed by Scott Hanselman into realising that I’ve been neglecting my blog recently, and using Twitter as a poor surrogate for more detailed commentary, something I plan to address in the next few months. Google+ acted as a sort of halfway house for a while too, but a combination of their lack of mobile updates, a terrible new desktop design, and the realisation that my blog does a better job of forming a permanent archive of my musings mean that I’m unlikely to use it very much beyond linking now.
How often do you stop and think about why it is you do what you do for a living? Maybe it’s a mid-life crisis thing, but of late I’m acutely aware of the finite nature of time, and that there are an infinite number of ways I could spend that time. I’m also aware that ‘software developers’ are a quite diverse bunch of people, despite the persistent stereotype of math geeks huddled around technical toys talking in obscure acronyms (OK, we do that too).
I posted a few months ago about the problems I’d encountered with performing privileged actions from a Mac OS X app - in my case, installing a command line utility in /usr/local/bin - and that all the examples of this that I’d come across used an approach which was now deprecated. You can find my original post here: Escalating privileges on Mac OS X securely, and without using deprecated methods.
It’s that time of year again, the end of that artificial construct we call a ‘calendar year’ that prompts so many of us to cast our minds back over the last 12 months. So, apart from rocketing helplessly through space at 107000 km/h, only to return to where we started (relatively speaking, ignoring where Sol and the Milky Way have moved since then), what’s up? As I talked about in my review of 2010, my goal had been to simplify and take back more control in my professional life, revolving around making my own products and cutting down contracting to just single, more significant projects.
This week I implemented a much-requested feature in SourceTree for the upcoming 1.3 release (beta 1 went out on Monday, this will make it into beta 2) - a command-line tool so you can quickly pull up SourceTree for the repository you’re in from a terminal. Writing the command-line tool was trivial, but when I came to implement the menu item which would install it in /usr/local/bin, which inherently needs privilege escalation, it turned out to be a lot more complicated than I expected.
A lot of you will already know, but SourceTree, a Mac client for Git and Mercurial I created over the last 18 months, has just been acquired by Atlassian. There’s a press release, articles on TechCrunch and VentureBeat, and an official FAQ on the SourceTree site. But this is my personal blog, and I’ve had a few requests for a personal angle on this, so here you go. I said in a previous post that in my experience, the best opportunities often come along when you’re not looking for them, and that was certainly the case here.
“So, where do you see yourself in 5 years?” I’m willing to bet every person reading this has had that question posed to them at some point, most likely in a job interview, but possibly during an appraisal, or if you’re really unlucky, by a potential father-in-law at a dinner party. I’m going to call it out right now - it’s one of the stupidest questions you can be asked. It’s a test, of course - does this person have a plan?
I was In Sydney when the UK riots broke out, and I didn’t hear about it until it had become an international story which showed Britain in the worst possible light. Much hay will be made about this over the coming months, but I thought I’d add my tuppence worth. Firstly, there can be no justification whatsoever for this behaviour, regardless of your background or surroundings. But it is a good idea to try to understand it, because locking people up after the fact only goes so far.