The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Actually I've been encouraged to knowledge dump my biggest client's code onto this site.
I just haven't yet because I haven't had the time.
Mind you it's not exactly the same situation, because my primary deliverable is hardware, not software. That's where the money is for us.
Anyway, that's where I am ideally.
And as far as knowledge being proprietary? My personal opinion is that knowledge frees itself over a long enough timeline - we can only get in the way of that. I do my part not to try to get in the way of that. The boundaries on what I share are set by my clients, not me.
As far as the rest of your comment, having elaborated your point, I don't have much to argue with. My initial read was different than my takeaway having read your response.
Yes some team members are crap. Sometimes. I read your comment as suggesting that was the norm that team members were crap, which is what inspired my initial response.
I can see not wanting to do it for "free". You have tasks to finish. Unless training others is one of them, your manager should know about it unless it won't interfere with your schedule. It can then be scheduled, and you can get credit for it. Being on a team doesn't mean that you owe everyone charity.
Except they can't be removed from the team as there would be a gap in skills and knowledge which you can't have right now as it would slow down the project, which is exactly why these people don't share: job security
Seen it happen and removed myself from the team instead.
Contrawise, I've had jobs where I was reprimanded for using advanced concepts (i.e. actually using the latest C++ standard which they stated as part of the job requirement.) I was once chastised for using a predicate with a std::map.
My favourite part of the job is passing on knowledge and watching people grow, having been doing it for almost 30 years I guess I have acquired some degree of experience to share (whether some people want me to or not )
I have been doing this long enough that several people I helped mentor have gone on to 'better' things sometimes at the same company sometimes elsewhere.
Which is fine by me, those better things often involve managing people, which I have never had any interest in doing.
True, to a point, but not always. I agree with you that under many circumstances it’s best to help those around you. A rising tide raises all ships.
There was a time, (29, 25 years ago) I aspired to be a ‘vast store of information’ - to have an answer for most questions. Over time my co-workers found it more expedient to ask me instead of learning/remembering for themselves. It became too burdensome.
Consider also the co-worker that asks, and is answered, only to ask again, the same question, days weeks or months later.
Lastly, consider that sometimes the direct, efficacious answer may involve considerations and complexities greater than the co-worker’s level of expertise with that platform. So answering may open a path to more problems.
So, if you’re cranky because someone isn’t helping you, perhaps you should ask why they’re not being helpful. If they’re truly an information hoarder whose habit is to disadvantage others as opposed to helping the group effort, then they’ll not get far in life.
Time is the differentiation of eternity devised by man to measure the passage of human events.
- Manly P. Hall
There was no particular incident that triggered this post. I'm just passing along advice based on my 30 years on the industry.
More than ever, teams need to be cohesive and supportive units in which the stronger senior developers mentor junior developers. Anyone who will not share knowledge that will benefit the team and/or the project is a detriment. Try to change their behavior first, but if they refuse to change then, in the long run, the team is better off without that coder.
<rant> I don't know about you, but I have a lot more trouble finding anyone that wants to even know my unique knowledge and skillset, which unfortunately leaves me pigeonholed for some things, despite my role having grown beyond it. I'd be more than happy to share so that I could take a full-time position on program that didn't leave me still helping with those items. When I ask management to make sure that the next person they hire have the ability or desire to learn these skills to backfill me, they put it at low priority and hire someone without the desire or skills. I'd like the rest of the team to be team players too.
it's actually my biggest gripe, in not only development but anything technical, we don't need primadonnas on the team. we need people who show their support by volunteering information, not hording it.
If a pet rock has a receding hairline is it a little boulder?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
According to timeanddate.com[^], the equinox will be at 9:37 AM (UTC). At that time sun will be directly overhead at 2(hours)*15(degrees) + 20(minutes) * 0.25 = 35 degrees East longitude. Assuming my math is right, this is very close to lake Victoria.