> 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.

▲

ravenstine 2 days ago | parent [-]

Yeah, well, I challenge them to do that. In the meantime, I'll keep it to myself.

▲

a96 a day ago | parent [-]

Contracts vary, but here if your employer tells you to do work ("document and deliver a tool that does X") and you refuse, here that's grounds for warning process and dismissal as a breach of contract.

	▲	tardedmeme 14 hours ago \| parent [-]
		His employer didn't tell him to do that. You have to get used to acting within the grey area and playing politics. Your counterparty (your employer) certainly does. Every businessperson is good at it, or they wouldn't be successful. In any transactional relationship - which employment is - when you want to do something, don't think: I can't do this because they wouldn't like it. Instead think: what are the likely consequences of doing this? Are they positive or negative for me, on net?