36 steps to success as technical lead(littletutorials.com)

submitted by danielstonerdanielstoner(335) 3 years, 9 months ago

The “tech lead” role can be treacherous at times. While the name implies “leadership“, most of the times it doesn’t come with implied authority like a manager role for example. It often happens that this role is in a no-man’s-land where it brings a lot of responsibility but not enough formal authority. In order to successfully help a project from this position one has to navigate through narrow and convoluted straits.

6 comments |category: |Views: 562

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by powerrushpowerrush(3873) 3 years, 9 months ago 0

2 out of 36 ain't bad... right?!? (man I hope these lists don't get longer)

Reply

posted by JemmJemm(9604) 3 years, 9 months ago 0

36 steps?? I'll leave that long walks to athletes..

Reply

posted by contourcontour(490) 3 years, 9 months ago 0

Yep, it ain't easy :). I still hold the hope one day I will find advice for a ONE step to success for anything :)
Good article, by the way.

Reply

posted by JemmJemm(9604) 3 years, 9 months ago 0

"Hard work pays off later, laziness pays off now"

But seriously, I agree: good article :)

Reply

posted by ugeertugeert(0) 3 years, 9 months ago 0

Very good article, keep them coming! I also liked "13 reasons why Ruby, Python and the gang will push Java to die… of old age"

Reply

posted by jaffarjaffar(0) 3 years, 9 months ago 0

So many steps... I have to go to the gym first :)

Reply

information Login or create an account to comment on this story