News for hackers. Stuff that matters.
Re:Do you ever avoid submitting something on HN so devs won'... by mmcgaha on Wednesday December 08, 2021 @11:48AM (#29487061)
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.

Re:Do you ever avoid submitting something on HN so devs won'... by jayd16 on Wednesday December 08, 2021 @11:53AM (#29487120)
Sure, 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.
Re:Do you ever avoid submitting something on HN so devs won'... by mmcgaha on Wednesday December 08, 2021 @11:56AM (#29487155)
I took the competitive advantage comment as the short story to a much longer reason.
Re:Do you ever avoid submitting something on HN so devs won'... by Hekioi on Wednesday December 08, 2021 @12:12PM (#29487394)
We started to share those kind of snippets in Operation manuals and knowledge sharing session.

This helps other people to grow.