Sharing the Work You Do 

  • Comments posted to this topic are about the item Sharing the Work You Do 

  • This reminds me of the situation I have faced, and that many of you might face as you get older, so you might want to consider this scenario.  During my 42 years in IT I worked under both good and bad managers.  My conclusion is that the 'best' managers I worked under were both OLDER than myself and MORE EXPERIENCED.  Taking a position reporting to a younger and/or less experienced manager could be setting yourself up for lots of frustration, pressure, lack of appreciation, and loss of opportunity.

    Having decided I did not want to spend any more time as a manager, by the time I retired at 67 years of age, the odds of reporting to a younger, less experienced person were great.  Some younger managers may see you as an aging liability. and others may seek to take advantage of you without due recognition of your ability and efforts.

    Face the possibility that a younger manager may well be more interested in taking care of themselves than in taking care of you.

    Now, on the other hand, in my last position I was actually assigned to help 'break in' a younger person who did soon become my manager.  It was evident that he had very good understanding and skills without an overgrown ego, and it was a pleasure working for him.  You just never know.



    Disaster Recovery = Backup ( Backup ( Your Backup ) )

  • One of the key benefits I've observed from sharing is the acceleration of learning. By exposing our work to peer review, we open ourselves to feedback that can refine our approach, expand our understanding, and inspire innovation. Moreover, it fosters a sense of community and mutual support that is invaluable in navigating the challenges of our field.\

    • This reply was modified 4 months, 2 weeks ago by  arnoldnashwel.
  • This was removed by the editor as SPAM

  • I like what you've said here, Louis. However, I've never worked anywhere where we shared with one another what we've learned or an approach we've taken to solve a problem. I don't know why that is, but it seems like the tech culture in my state is opposed to sharing with colleagues.

    There is only one exception which enforces the unspoken rule of never sharing something you've learned. That exception is if you've run into a problem you cannot solve. Then your manager is likely to tell you to talk to so-and-so, because they may have done something similar. So, the message is if you're sharing anything, it's always a failure to comprehend it on your own. Thus, you're a moron who needs the help and pity of others. Thus, seeking help from someone else tends to only happen once every few years.

    I do share what I've learned at our local .NET user group. User groups are the only acceptable place you can share whatever it is you've learned. In my community.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • This was removed by the editor as SPAM

  • Go for it, the only way is up!

    If you research your subject, capture your method and your results then you have something that future you will thank you for, whether you share it or not.

    Sleep on it for a few days and re-read what you put.  Your unconscious mind will have processed it and have suggestions for improvements.  Again, future you will thank you, especially if you use a spell checker.

    If you do decide to share remember that there is always an audience of people who are beginning their careers so any article that gives them a leg up will be gratefully received.

    The vast majority of feedback will be kind, criticism is generally constructive.  If there are trolls, don't take it to heart.  They are relatively rare.

    Do not be dissuaded and judge yourself harshly because you have seen slick presentations at conferences where everything was sweetness and light.  I saw an amazing presentation on personalisation where the vendor had delivered in record time a project that saved the company millions.  Slight problem with the story, it wasn't true, not even close.  I described the presentation to some people who had actually been on the project and they responded with some heavily industrial language.

    All the best presenters at SQLBits started nervously.  Martin Fowler from Thoughtworks came out publicly and said he was refraining from public speaking because he found it so stressful.  Anyone who has heard Martin Fowler present would be aghast when they heard that.  He was one of the most insightful and gifted presenters on the circuit.



  • This was removed by the editor as SPAM

  • This was removed by the editor as SPAM

  • This was removed by the editor as SPAM

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply