> I don't share it with anyone because of the negative return in both supporting it and everyone else being able to be as productive as I am.

That sounds like a toxic environment. Sharing those types of things is how I got the recognition to get ahead in my career and I have never once regretted it.

In my place of employment, anything I create while on company time or using company resources is the property of my employer.

So while it might be nice to say I won't share, boss-man can certainly make it so I must share.

Over the years, I too have developed ad hoc tools to make my job easier or faster. I don't hide them, but I do not share any since the tools are not really ready for that. I don't have them properly documented, other people would not understand how to use them, why and all the quirks. I suppose a lot of developers do the same.

Yeah, if there is no gain then employees shouldn't be giving any more than exactly what they were hired for. Most big companies are and should be treated as adversarial, because they won't think twice about dropping your ass, you are just a name in the HR departments computers to anyone you don't directly work with every single day. I think a lot of tech employees bought into all the bullshit because they made such good money and were for awhile uncommonly skilled. But their uncommon skill sets have become more and more common while the actual knowledge needed by individual employees has dropped. All the garbage conditions many game programmers and artists have to deal with? Yeah that is coming for the entire tech industry, and that isn't the low point, that is the shit pile just picking up speed. It should be obvious looking at almost every other industry after a few decades.

I sadly have to agree with this. In a collaborative "give and take" world sharing is good. In an environment that takes only, all you have left is your own intellectual property. It is your own most vital asset worth protecting. Shouldn't be like this, but it is.

I don't think this way because I like to collaborate. If a colleague can benefit from a tool I made I'm proud to save them time. I also think your attitude doesn't pass the golden rule: would you like to work on a team full of people like you?

I go completely the opposite direction. I stick my name right in the script and write a wiki page documenting it as clearly as I can manage. It becomes part of my value proposition to the company.

> I wrote my own CLI to make aspects of my job easier

I mean, according to your employment agreement, that code is owned by your employer, since you wrote it as an employee for use at work. They could easily demand that you share it, if they knew it existed.

This just illustrates that smart people figure out their own productivity/time-saving shortcuts at work, and little scripts and tools like this are part of it. Happens all the time. Other employees don't, and just plod through whatever manual process they were trained to do.

What are your thoughts on open source? Seems like the same problem writ large

It sucks to work with people like you, honestly. Prima-Donna types that overindex on their own personal paranoias instead of trying to succeed, grow, and excel along with the people around them. Quite literally not a team player.