Comments on: What It Takes To Be A Great Technical Lead

By: Article (and my opinion + some) on What It Takes To Be A Great Technical Lead? | Microsoft SharePoint & Windows (Vista, Azure, 7) Cloud & Social Computing Space

Thu, 11 Dec 2008 10:19:17 +0000

[...] 4. Project Management. Every technical lead should have project management training. You need not turn over pages and pages of metrics and variances on a daily basis. I do not like that either. I keep things as simple as possible and maximize SharePoint. Simplify, simplify, simplify.trackback [...]

By: Milo

Milo — Thu, 11 Dec 2008 07:15:23 +0000

“”that’s a tough situation… one thing you could try is to bring in the other teammates, have both sides explain why they prefer their solution, and the downsides they see with other solution, and then let the other teammates vote on it.”"

Everyone on both sides should have strong arguments and explain their thought process. The decision is not about a certain approach because every approach have positives and negatives. The decision should be about what is important to the client — long-term goal, maintainability, usability, budget, timeline etc.

When all is said and presented, I decide. Period and that’s where my technical lead role kicks in. Get real, unemployment is rising rapidly in all parts of the world, go figure…

By: Interesting Finds: 2008.12.08~2008.12.11 - gOODiDEA.NET

Interesting Finds: 2008.12.08~2008.12.11 - gOODiDEA.NET — Thu, 11 Dec 2008 03:07:31 +0000

[...] What It Takes To Be A Great Technical Lead [...]

By: prashant

prashant — Mon, 08 Dec 2008 17:06:23 +0000

Hi,

Nice post.I like it.

Thanks
Prashant

By: Davy Brion

Davy Brion — Sun, 07 Dec 2008 20:08:57 +0000

that’s a tough situation… one thing you could try is to bring in the other teammates, have both sides explain why they prefer their solution, and the downsides they see with other solution, and then let the other teammates vote on it.

But obviously, if they prefer the other way you’re pretty much stuck with it then

By: Nis Leonhard Simonsen

Nis Leonhard Simonsen — Sun, 07 Dec 2008 19:56:58 +0000

Very good, and inspirational, summary, I must say.

Any tips on what to do when one of your teammates insists that something should be built a certain way, and you simply cannot persuade him that it should be done otherwise?

Obviously in this example, what he suggests would “work”, but would also place restrictions on the codebase afterwards..

By: links for 2008-12-05 | Yostivanich.com

links for 2008-12-05 | Yostivanich.com — Fri, 05 Dec 2008 15:03:59 +0000

[...] The Inquisitive Coder – Davy Brion’s Blog » Blog Archive » What It Takes To Be A Great Technical… (tags: programmer management career work job leadership) [...]

By: Veera

Veera — Thu, 04 Dec 2008 15:03:12 +0000

Well said. Thanks for the tips.

By: Dew Drop - December 4, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - December 4, 2008 | Alvin Ashcraft's Morning Dew — Thu, 04 Dec 2008 14:07:49 +0000

[...] What It Takes to Be a Great Technical Lead (Davy Brion) [...]

By: Doni Grande

Doni Grande — Thu, 04 Dec 2008 14:02:08 +0000

Great. I usually summarize the n-1 and n-2 bullet points with the simple “Give credit, accept blame”. For too many times you see the opposite.

By: good leadership skills | Digg hot tags

good leadership skills | Digg hot tags — Thu, 04 Dec 2008 09:19:47 +0000

[...] Vote What It Takes To Be A Great Technical Lead [...]

By: Tuna Toksoz

Tuna Toksoz — Wed, 03 Dec 2008 23:57:23 +0000

Wow that’s great! Thanks, Davy.