4 ms·
This isn't any different than keeping a bunch of text snippets that you use as a starting point for creating things. Text snippets may seem trivial in compariso
by mmcgaha 5y ago
This isn't any different than keeping a bunch of text snippets that you use as a starting point for creating things. Text snippets may seem trivial in comparison to some tool that writes code or checks for your common errors, but when there is a bug in your text snippet, you own the bug.
Let's say he gives away his tool and all of a sudden he is the guy who has to work on it when other people have problems. Now his coworkers have more time, he has less, and he is the scapegoat for when things go wrong. Not only that but since it is not a real product of the organization, no one will recognize the time he works on it so he will have to work over time to meet his other goals.
Now if someone wants to ask for a copy of what I use, sure but they own their copy and I own mine.
- jayd16 5y agoSure, there's plenty of reasons to not push every line you've written. However, the stated reason is to keep a "competitive advantage" against their coworkers.
- mmcgaha 5y agoI took the competitive advantage comment as the short story to a much longer reason.
- Hekioi 5y agoWe started to share those kind of snippets in Operation manuals and knowledge sharing session. This helps other people to grow.