Monday, June 05, 2006

Creating Firefox Extension

Learn by example

Everyone has a good idea at one time or another to implement a new feature in a web browser. Well, with the goodness that is Mozilla Firefox, now you can do just that. You need to have a vague understanding of XUL and Javascript, but you certainly don't need to be a master of either.
The author explains how the extensions break down in a nutshell, using BugMeNot as an example

read more >>

Related Post : If you want to develop firefox extension

Friday, June 02, 2006

Stupid Engineering Mistakes

"Wired has bestowed on us a list of the ten worst engineering mistakes of all time. We have the St. Francis Dam designed by 'self-taught' enginner William Mulholland, which burst and wiped out several towns near LA; the Kansas City Hyatt walkway collapse; the DC-10, and more, but my favorite is the one I'd never heard of: a giant tank of molasses that ruptured in 1919 and sent 'waves of molasses up to 15 feet high' through Boston, killing 21."

Source :

Thursday, June 01, 2006

Vim tips: Using viewports

A really useful feature in Vim is the ability to split the viewable area between one or more files, or just to split the window to view two bits of the same file more easily. The Vim documentation refers to this as a viewport or window, interchangeably.
You may already be familiar with this feature if you've ever used Vim's help feature by using :help topic or pressing the F1 key. When you enter help, Vim splits the viewport and opens the help documentation in the top viewport, leaving your document open in the bottom viewport.
Read More

Article By: Joe 'Zonker' Brockmeier
Also Emacs Tips : Buffer & windows

Sunday, May 28, 2006

Learn how to comment

This wikipedia tells about different commenting styles and how they can be helpful while programming.
http://en.wikipedia.org/wiki/Comment#Summary

Comments could summarise code or explain the programmer's intent. This is called the why rather than how approach. The two are often close, but not always. According to this school of thought, restating the code in plain English may be a waste of time; the need to explain the code may be a sign that it is too complex and should be rewritten.

"Don't document bad code – rewrite it" (The Elements of Programming Style, Kernighan & Plauger).
"Good comments don't repeat the code or explain it. They clarify its intent. Comments should explain, at a higher level of abstraction than the code, what you're trying to do." (Code Complete, McConnell)
Happy Coding !!
Link from : Kshitij's Blog

vi survival guide

A comprehensive guide to a famous text editor "vi", written in vi itself.

read more | digg story

Installing and using Linux for the total newbie

So you've heard about Linux and you want to try it out, but you're scared you may screw up Windows or that it's too hard to install. Well fear no longer, here is a guide for the total newbie.

read more

I'm Back...

Now i'm back here after enjoying holidays at home...