Comments on: Choose The Right Goals

By: Nam HT

Nam HT — Tue, 18 Aug 2009 06:22:21 +0000

As a normal developer, the responsibility is only getting very small and detail functionalities done. Without higher position, ‘lead developer’ or something like that, it is hard for developer to know about the bigger picture that system towards or be involving in design, due to there is an impact on detail implementation. It is really dangerous for projects if ‘lead developer’ is not good as him should be.

By: ncloud

ncloud — Wed, 12 Aug 2009 13:32:15 +0000

It’s inspiring to read this. I’ve been under a lot of pressure for the last year to be more political and move up the ladder, but it’s not really what I want, at least, not right now. @Eric Smith, thanks for sharing that great quote from Uncle Bob! He’s absolutely right.

By: Eric Smith

Eric Smith — Tue, 11 Aug 2009 04:56:45 +0000

As Uncle Bob said in a recent Hanselman podcast interview – “an architect who doesn’t code is irrelevant”. I think that the reason for this situation is twofold viz., 1) Businesses don’t “get” software development (unless it’s their core business) and as such incentivise on the wrong things and 2) Because developers are usually so young at their prime, they haven’t yet acquired the maturity to know what they want in the careers (and therefore are heavily influenced by the model “sold” to them by management).

By: Thomas Moerman

Thomas Moerman — Mon, 10 Aug 2009 21:45:09 +0000

It is kind of sad that many (large) companies don’t acknowledge the value of experienced developers who want to dirty their hands with code on a daily basis. But then again, I’ve witnessed a case where the lead developer (truly remarkable guy, should’ve been a professor in theoretical physics or something) was the real power behind the throne, the inmate running the asylum, so to speak Perhaps there is hope? Peace.