The “Don’t Learn To Code” movement continues to chug along in the background, attempting to counter the “Learn To Code” folks. A recent post, along with a seminal piece on Coding Horror, all express opinions on to why learning to code really isn’t that important, or in some cases may be either inappropriate or even dangerous. A lot of these “don’t learn to code” pieces tend to focus on the technical elements of why coding is harder than you think, why it takes more than a quick weekend course, and lament the state of development tools. But few address a more fundamental question, one posed as a popular argument for learning to code.
The interwebs are now rife with retrospectives on what happened in the past year, as well as predictions for the coming 12 months. I’m not going to go back and reminisce, because what’s done is done. It is fun, though, to look at ahead to the future. Some of this will look and sound and feel like a “prediction” at times, and I’d be lying if I said they weren’t, but I don’t claim any of them will actually come to pass. Like any estimate, it’s a guess and not a guarantee. And I know I’m more likely to be wrong that right (which is the only prediction I’ll probably get right). But I don’t let little details like that stop me :-).
A post on AlleyWatch proposes a way for a non-technical person to qualify and hire a developer. It presents, among other things, a list of 10 interview questions to ask prospective candidates. The problem, though, is that the author makes some fundamental mistakes in my mind, and is trying to avoid hiring multiple people for multiple jobs.
An article in the Globe & Mail posits a way to “start fixing BlackBerry”. The problem? There wasn’t a truly useful or meaningful suggestion. Worse, the writer fails to challenge one of their sources on an inconsistency in the industry.
The new Playstation 4 from Sony is going on sale in the US tomorrow. There are plenty of reviews out for this amazing machine, but one common complaint is apparent: it is short on games. Could Sony have fixed this problem?
Apple’s announcement on Tuesday definitely had a lot to cover. They weren’t kidding on the invitation. Was it too much at once? You could argue that. Apple seems to try to keep these sorts of events to 90 minutes, and parts of it definitely felt rushed. Having lots of new toys is cool, though.
Okay, so I haven’t posted anything in a couple of weeks. This is about the time people start wondering where I’ve gone, or what I’m up to. My silence is a combination of factors conspiring against any sort of semi-thoughtful rant.