It’s been a while but for a good reason. We’ve been giving a lot of love lately to the shiny new web app we’ve been developing on and off for the past few months. And today I’m proud to have open its doors, albeit just a little bit, so a little of sunshine can go through. Suffice it to say, for now, that we’re still far from production mode and the next few weeks will be spent on some testing in our inner circles, desperately trying to iron the most obvious and silly bugs. More on this later, as I plan to write a series of articles documenting our experience while developing this app. I just couldn’t imagine this could be so much work, even if the tools available these days take a lot of the burden out of it.
Other than that, I guess I finally choked long enough in my own delirium and decided it was time to hit the books and actually get down to work, university-wise. The semester is quickly drawing to an end and there are still so many loose ends, it’s unbelievable. A lot of project works, at least one of them a bit, shall I say, tricky (writing a Prolog interpreter in Python, in this case) and others just plain boring. But a man’s gotta do what a man’s gotta do or so the saying goes. Come July, if all goes to plan, I’ll be able to catch my breath. Or not.
And into the title of this post, which pretty much boils down to this: these days, when I want to learn how to do something - say, the syntax to checkout a specific SVN repository revision - my first (and pretty much only) thought is simply hitting Google with the plain question. More often that not, I get the right answer right away. No thinking involved. What happened to the days when you actually had to read the manual or, God forbid, look into the source?
I leave that question hanging in the air.