Great stuff, gentlemen. :-) Incase any of the listers are thinking what this thread is all about, well you are have come to the right place. And if it makes you curious to know more, you are at the next step towards learning programming! Programming is not magic nor some myth. It is real and you can make a computer perform functions, your imagination is the only restriction. To put this thread into an easier learning way, programmes are all around you. Programming gurus can correct my contribution at any time, which is very welcome. Lets move on. For network people who have accessed cisco, nortel or even juniper boxes can relate to this. Ever wondered what that command prompt was? Well, in a simple way it is really a console application. When for example you enter the ? at the prompt on a cisco, it lists all available commands that have been programmed to respond to the ? input. SIMPLE! And each time that you type and enter parameters like config t, intE0 etc all are really a very simple program written by cisco. When cisco moved to enable configuartion via a web based page, it basically took the functions of that simple console application and made it more user friendly. For RF people, I hope you remember the first time that you dealt with frequencies. You cannot see them nor can you touch them, yet they are there. When you first designed a tiny FM transmitter, you had to calculate the inductance/capacitance to arrive at the frequency of your transmitter. With those inputs, what you really were doing was establishing ways to do things with devices that had set properties. What about things like dbms? What about when you created your first RF network, you had to create your inputs and outputs and work with things like decibels. You simply did not go and install a cable and then wonder how to terminate it. Way back even to the early days, you needed some sort of a software program to connect your laptop serially to a microwave transmitter eg to set a loop test and return back commissioning data for SNR levels. These programmes made it simple to talk to devices and perform tests. For people who did Electronic eng, well you do remember those resistor colour codes, don't you? Or remember the PNP.NPN transistors that had Base, Collector, Emitter leads. What about things like Hfes'? As early as those days, the multimeter that you used to check the various settings were working on simple programmes in voltage form. Without any references to the internal functions of the components, you could arrive at a diagnosis on where the fault was. There are many examples and they are around you. Your mind just has to be curious enough. :-) Programmer gurus on this list, I think it is time to introduce frameworks and why many programmers will take those routes. And for those still interested and itching for more development, well shoot your questions. Incase you wondering what a framework is, for Network people you already know it. Cisco, Nortel, Juniper developed the systems and the software framework allowing you to work with these devices without having to write any special programme to communicate with their hardware. Fact to interested listers : Did you know that you use a Console application to enter a password in your *nix box? I'm taking a short timeout to focus on my project but will be reading the contributions. :-)