Skip to main content

The Time of Computers

Hello, all! I'm back after another nice, long, refreshing hiatus because for the nth time, my parents have put their feet down and insisted I compose a blog post. I MAY HAVE TO DO IT, BUT YOU'LL NEVER MAKE ME DO IT WITH GOOD GRACE, MOM!

I was thinking about my school computer science class (I wasn't really, I just need a way to introduce the topic) and about the kind of programs we have to write. They're not very complex programs, they do pretty simple things like adding up numbers or sorting things. They also aren't very long. A program that I'm asked to write in class will scarcely take me ten minutes to finish, and be around fifteen lines long. The Google home page has more lines of code than that, for crying out loud!

Now, there's nothing wrong with short programs. A lot of the most efficient programs are quite short, and I'm always thrilled to be able to write one line instead of two. However, the problem with writing only 15-line programs is that it doesn't really give you a sense for how much work really goes into building a software product. It leaves people with the impression that an entire operating system, say, can be built with around 30 lines of code. Now, while I hope that that may be the case in the future, none of the tool sets currently available to us are that good. Windows XP, for instance, is around 45 million lines of code in size.

The usual explanation is that a computer science course is supposed to teach you the concepts required to build a program, not actually have you build a program. While it's very good for me to know what I'm doing with while-loops and for-loops, I think I'd also like to know the amount of work that goes into developing a functional product. I wrote an app a couple of months ago - a pretty simple app by today's standards - that took me several weeks to finish. Of course, it probably didn't help that I was only putting in one hour every day, and even then not every day of the week. The point is, though, our computer science course implies that building the next great piece of software is something that I can accomplish with half an hour and a computer.

It also strikes me that people who have been taught programming by writing fifteen-line programs in visual basic are rather more liable than everyone else to break down and weep after their computer tells them, for the fifth time, that it "could not locate aeinv.dll" or whatever. I'm not saying that I don't feel the urge to chuck my computer out the window and go out for a walk every time my code doesn't work. I'm just saying that I'll probably sit down after the third failure and reboot the computer (and that's what every overpaid repair engineer doesn't tell you - if your computer isn't working properly, you should probably just turn it off and on. If that doesn't work, ditch Windows and use Linux like a real programmer.)

The obvious solution, of course, would be to set up computer science courses to be more like a team working towards a goal. The current format seems to be to throw a bunch of problems at you which use all the features of a given programming language. I wish I had a less obvious, well thought out solution to offer you, but I never have, and I'm far too lazy to come up with one. Instead, I'll leave you to hope that you never, ever have to learn to use Linux.

Comments

Post a Comment

Popular posts from this blog

Weighing In

Today, I'm writing about something I'm actually rather proud of. Today, I'm writing about my weight loss. Over the past ten months, I've lost 12 kilos.

My parents have been begging me to start exercising since eighth grade. When I was 13, they'd boot me out of the house every day at 5:00PM and make me go running. I hated it. I barely even bothered to run, let alone push myself or stick to a diet. I ate like a trash can, sat in front of the computer all day and did nothing at all about my rapidly swelling pot belly. By the time I'd turned 15, even Dad had given up any dreams of seeing me with a flat stomach. I'd trained myself to stop looking in the mirror, and I stayed out of pictures as much as possible.

Fast-forward to the present day: I weigh 69 kilos. My stomach has all but vanished. Looking in the mirror is a satisfying experience, and I even have some muscle on my arms. I can now fit in medium-size t-shirts, and whenever I wear my old jeans, I look li…

5K:) - 2017

If you've been following my blog for a while - since the end of 2015-beginning of 2016 - you'll probably remember a post I did last year about the Thousand Smiling Faces project (I also wrote another post about it immediately after). For those of you who are too lazy to click through those links, the Thousand Smiling Faces project was a bunch of us teenagers getting McDonald's Happy Meals for 1000 kids in orphanages.

I was planning to this again on New Year's Day 2017, but couldn't get it to work out. However, Independence Day is coming up, and we're going to do it again, but this time, we've gone a little crazy - instead of working with 1000 kids, we're aiming to deliver 5000 meals! That's roughly  ₹5,00,000's worth of Happy Meals, a lot of burgers by anyone's standards.

We've also got another twist to the thing this year. Seeing as we're doing it on the 15th of August, which is India's Independence Day, and seeing as how McDon…

Talking Trouble

I want to begin this post by saying that I don't volunteer to speak. I'm not one of those guys who's always MCing this or giving a speech about that. I speak in public only if I have no other choice, and those situations come by rarely enough that I've had very little experience actually being on stage and talking.

Last week, though, I was at an NCC camp, and the PI (Permanent Instructor, for you non-NCC folk) staff decided that I should host an event on account of I spoke decent English. Normally, I would refuse, but in the NCC, if they ask you to jump over a cliff, you need to have been over that cliff five minutes ago. You don't get to ask why you're jumping off of a cliff, you just jump. So it was that three days into the camp, I found myself on stage with a co-MC I didn't really know, in a uniform that I had lost the knack of wearing and holding a mic that caught, oh, about 50% of the words you spoke into it.

At first, I was incredibly nervous. The pr…