Great Article, well done

I’m wondering where you get off thinking you’re the one who determines how good a developer you are. You’re a commodity and the market values your worth, your blog, queries or whatever else you value has nothing to do with the bottom line.

anyway it was entertaining and you’re entitled to yoru opininoin..

The only thing I can’t stand is the ego with developers who think because they have a blog that they can just start talkng shit or believing their own hype.

get over yourself.. a good developer is a people person and a problem solve.. that’s IT!!!

Cheers

While you’ve clearly mastered the Hubris, you’re utterly missing the Impatience and don’t appear too serious about the Laziness either.

It was a nice article though which bring me here to read.

If I were you I wouldn’t let my manager to know that I “love” my work. I.T. Managers with no technical backgrounds would see this as a way to give you more responsibilities without the right pay. Simple fact, if you love your job then you would do all the things the manager throws at you.

I’ve been coding for nearly two decades and I consider my greatest asset my experience not my “knowledge”. I consider “knowledge” in world of Software Development as specific things such as programming against APIs. As you know in the world of I.T. in particular in software technology things can change very quickly before learning them in any depth. The knowledge you gain will be out-dated soon enough but not the experience you gained.

The more experience you have the quicker you would solve the next problems regardless of how knowledge full you are in the technologies that you are using. This is a common mistake among developers that assume knowing specific API/Framework i.e. SharePoint make them more expert than the rest but an experienced developer can pick things up at no time.

I do also blog about software development when I find the time so I’m not against your idea about blogging however I do differ in one thing with most of the developers out there. I’m totally against giving away too much or giving away complete solutions for the following reasons;

1. Giving away too much will make the developers too lazy to figure out a solution to a problem on their own. Google can be so counterproductive when one would use it as soon as they need to figure something out instead of using the brain.

2. Giving away too much would also devalue the knowledge itself. Devaluing knowledge only means your next employer wouldn’t consider your knowledge as an advantage to employ you. I always use the SAP community as an example to put cross my meaning. You can’t find any other community like SAP’s that safeguard knowledge so well. This is the very reason as to how the SAP consultants are still on very high salaries when the rest of us get far less since the crash of .com.