I alluded in a previous post to the fact that I’ve chosen Mac for all my development activities. I’m aware that in game development (outside iOS games), this is perhaps not the most common choice. Apropos, I saw a tweet thread last week, not gamedev related, where a heated debate broke out about what platform/editor/language ‘real’ developers use. I’ve lost track of the number of times I’ve seen threads like this, where opinionated developers try to tell others what choices they should be making.
In my recent post A new journey I announced that I was moving into game development. Some people immediately followed up with questions about what engine I was intending to use, because developers 😉 Plot Twist! So let’s get this out of the way early: I won’t be using Ogre 😱 Hold your incredulity for a moment. 😀 The reason is not because Ogre isn’t great; since I retired, the team has been doing some amazing work.
I’ve thought about having a proper go at making games of my own for quite a while. There’s always been some reason why I’ve never quite gotten around to doing it seriously; all good reasons but when you line them up in serial, you suddenly realise a lot of time has passed. I’ve decided it’s time I stopped just thinking about it. As of today, I’m stepping down from most of my other responsibilities to dedicate serious time to making games.
I’ve been running this blog through a CMS since around 2003. The first version of this site that went beyond manually edited HTML ran on on PostNuke, for reasons I can no longer remember. 🤔 I moved to Wordpress around late 2005, and I’ve basically been running it ever since. It’s served me well, but as you can tell I don’t blog as often as I used to, and it got to the stage that my most frequent use of Wordpress was updating it, rather than adding content.
A quick post today because I didn’t find an easily accessible reference for building Git from source on Mac OS X El Capitan, and I needed to. Maybe there’s another post out there just like this one, but I didn’t find it, so maybe this will be useful in future for those who similarly come up short on Google. After you’ve cloned the source from https://github.com/git/git, open up a terminal. I’m assuming you’ve got Xcode installed, and that you’ve already installed the command line tools - if not, execute this on the command line now: xcode-select --install As with most command line builds, you now just need to go into the git source directory and run ‘make’.
I never used to drink coffee.
Early in my career, fresh-faced and beardless as I was, while spending my days coding business software and my free time tinkering with 3D graphics, I burned the candle at all 3 ends in a fashion that was far from healthy. The lack of sleep often took a bit of a toll on the old (or at that point, young) synapses, so at first I started drinking coffee purely for the caffeine.
Over the intervening years I’ve grown greyer and more cranky, but in the coffee department I’ve at least become more sophisticated, or so I’d like to think. It occurred to me that maybe others might find this journey interesting, and have written it up below in a long and frankly rather self-indulgent fashion.
So, if you’re a fellow aficionado of the magic bean (or cherry, if we’re being pedantic), or maybe you’re thinking of taking your coffee a little more seriously, perhaps you’ll find this interesting or entertaining, or maybe you’ll just have a bit of a laugh at my expense. It’s a long one, so if you make it to the end, you’re entitled to respond to it however you like, including telling me it was a load of old bollocks.
If you’re sitting comfortably, let’s begin.
Hey everyone, hope you had a good Christmas and New Year break. You may have noticed I’ve been a little quieter of late, and there have been a number of reasons for that. I had to be a little more careful about what I talked about during the last quarter of 2015 because the company I work for went public (go TEAM!) - a new experience to tick off the list 😀 - and unintentionally that started a bit of a trend.
This is another article in my series about broadband in Guernsey and what the future might hold. You might like to read the previous articles: Hands on with JT’s fibre to the home, Why fibre, and why now?, Guernsey broadband should aim to lead, not bring up the rear, and some other secondary updates linked in those. Or not; I’m not the boss of you. I’ve talked before about how I think using the mobile data network to skirt around the problems caused by underinvestment in the physical telecoms network is at best a short-term stopgap, and not something to lean on long term.
I don’t welcome a new majority Tory government in the UK. It doesn’t directly affect me since I live in a politically separate crown dependency, but nevertheless I still consider myself British as much as Guernsey, much of my family live in the UK, and the tone of the mainland does rub off on our culture here in general. I’m a left-leaning liberal and a strong supporter of progressivism, social and otherwise, and I see a pure Tory government as generally regressive, pursuing an ideology that, despite the aspirational rhetoric, largely favours the incumbent wealthy in society.
I’ve been banging on for a while about why I think the only future for Guernsey’s internet infrastructure to homes and businesses is to embrace fibre broadband, and that technologies like VDSL and 4G are limited stop gaps at best. Fortunately, there is one telecoms company in Guernsey who agrees with me, and that’s JT (I’m sure Sure will come around eventually). JT have a fibre network to supply our government buildings and schools already, and are actively interested in trying to roll it out to homes and businesses who are near to this network, to free us from the horror of spotty, inconsistent copper-based broadband.