Found this article at redhat related to software licenses. Quite an old post but as they say “Old is Gold”. This would give anyone reading it a better idea about the various licenses in the open source world. The article is avaliable at
This post is specifically for my software coder friends who are presently coding or have done it in the past. Every software developer after leaving college dreams of a job where he will be building great software . If he is lucky he will get a really good job where in he will be able to fulfill his dream of coding all day long and making some great software. If he is more lucky he might even get a decent salary for doing this stuff.
Recently during some discussions one of my office colleagues who was promoted to a position of “Team lead” was announcing that he has “given up” coding and he was now not at all interested in even looking at the code. I had encountered similar situations before where in a person was recruited as a team lead and was asked do some coding since he did not have much idea about the product the company sold . Mr Team Lead disappeared after 10 days and left behind an email saying that he was “demotivated as he did not want to return to a coding job”
Personally i think a small amount of coding is absolutely necessary and should be reduced if at all depending upon ones job profile. If one moves to a managerial position or something similar, he could give up looking at the code altogether. But if you have developers working in your team then it would be absolutely crazy if you decide not to look at the code as then you will surely lose respect among your team as they expect you to bail them out whenever they are stuck up somewhere .
Why did this concept come up that as you move up the ladder you reduce the amount of code you write. ??? The answer to this is simple. More work happens by delegation. If you are good at your job you finish only 25% of the job but as a lead you would be able to “code” all the 100% with 4 developers working in your team though you may not actually code . You monitor them . You review the code. Since some “hardcore coders” fail to understand this theory even when they complete few years on their job their bosses have to tell them that they are not supposed to do coding now. I guess since many fail to explain it in a better way there is this wrong myth that coding or even looking at code should be avoided at all costs.
Personally i feel everyone needs to continue some amount of coding irrespective of his position in the ladder so that he is not out of touch and when there is a situation he can easily face it. This could be coding for hobby projects or the official work but some amount at regular intervals definitely helps.
I still feel that many could have exactly opposite views than the one expressed above . Will surely update this post if i get some convincing opposite view about this.