The Techie Decalogue

It was with High Hopes and Noble Intentions that one chose to train oneself for the exalted profession of Engineering. One thought it would be mostly about warp drives and lightsabers and telling robots what to do (“A robot must not disturb the One during a game of Minesweeper or, through inaction, allow the One to be disturbed during said game”). It actually seems to involve mundane and extremely unglamorous things like debugging core dumps and writing system specifications, neither of which one has really got the hang of.

See, six years of concerted study have taught one remarkably little except for the fact that a penchant for computer games and science fiction cannot see a chap through. One finds oneself in the unenviable position of being a Techie Who Knows Nothing Of Things Technological (TWKNOTT).

Today one shall spare a thought for fellow TWKNOTTs. A few pointers (no pun intended) will, one hopes, go a long way towards making their lives easier. One delivers, O people, the Ten Commandments of TWKNOTT-dom:

1) When the in-house ubergeek (and there is always an in-house ubergeek – he’s the one who spends his weekends writing device drivers and was probably born hacking away at the Linux kernel) mutters something about how that newfangled filesystem doesn’t work too well with the Allegro library, thou shalt silently nod in agreement.

2) Thou shalt occasionally remark, in reply to aforementioned ubergeek, that thou hast heard rumours that the aforementioned filesystem doesn’t take too kindly to UPnP either. If feeling particularly enthusiastic (or if it is a Friday afternoon), thou shalt add that it is only possible to verify these matters by running simulations using the Parallel Virtual Machine. Over the Secure Shell. With private-key encryption.

3) Thou shalt liberally pepper conversations with the words “robustness” and “scalability”. They’re powerful concepts, those two, and may be used in connection with many different things, like hardware, software, organizational structure, and the secretary’s new lipstick.

4) Whenever a fellow techie describes what he is doing, thou shalt ask him what layer of the OSI model he works at. This question is almost universally applicable, and you’ll sound pretty clever asking it.

5) If someone utters an incomprehensible acronym-with-numeric-suffix, thou shalt retort with acronym-with-larger-numeric-suffix. For example, if talk turns to MPEG-2, thou shalt immediately speak of the more advanced MPEG-4. If someone then dares to move to MPEG-7, you may raise him all the way up to MPEG-21 (which is so advanced it hasn’t even been developed yet). Thereafter thou shalt start with H.263. And then thou mayst go pretty much as far as thy heart desires.

6) Thou shalt refer to “levels of abstraction” at least twice in every conversation (more if it’s an interview). This, again, is a powerful term, so you need not worry much about where you use it.

7) Whenever thou hast no clue how to solve a certain problem, thou shalt reveal to fellow workers (in a suitably low tone) that the problem is so difficult you’re thinking of using a neural network. This shall suitably impress everyone, and you can always tell them later that it didn’t work because the damn thing wasn’t intelligent enough.

8) Thou shalt regularly perpetrate extremely bad techie puns – these are actually well received by other techies. Thou mayst begin with something basic, something along the lines of

Q. How did the operating system know how to execute the shell script?
A. The interpreter mentioned it in parsing.

9) If having tea with desi techies, thou shalt give in to temptation and disseminate substandard Sholay jokes based upon the unsuspecting Samba suite.

10) Thou shalt account for the fact that the person you are talking to might be a TWKNOTT too. If such is indeed the case, the two of you may merrily undertake the task of preparing additional tips for fellow TWKNOTTs.