Earlier quoted context omitted.
Wait, why don't you want to help your colleagues? That seems pretty shitty.
It’s entirely possible that his colleagues have no desire to be helped, which can happen in a shitty organization.
Do you ever avoid submitting something on HN so devs won't ruin it?
61–70 of 312 posts
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#62I don't understand this sentiment at all. I have no idea what any of what you're posting has to do with "well intentions" or "money mak[ing] people do anything". Are you just mad that dislikes were removed from YouTube? I don't see what that has to do with any of those statements.
don't understand this sentiment at all. I have no idea what any of what you're posting has to do with "well intentions" or "money mak[ing] people do anything". Pretty sure they're saying that the YT developers would break their cool hack if they knew about it, because they want to keep their jobs (eg, getting paid, or "making money"). Sounds like the OP wants to view all developers as adhering to some Platonic ideal…
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#63> but apparently money makes people do anything. I don't see the link with your example. How would people profit of finding the number of dislikes on YouTube? Also, sharing this would increase the number of users of the exploit, and its general publicity, making it more likely to be fixed. Nothing to do with having each other's back. And then, considering that you are disclosing a security leak, the "having each othe…
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#64Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#65Yeah I do this. Most of what I build, nobody knows about it nor is it release into the wild. Latest example: at my current workplace we have some crappy custom compilers for our platform.... I've rebuilt them in a way that I like (and using C# instead of Java), that enables me to use it in a small visual studio code plugin that enables me with real time error messages as I code against our platform, so basically cons…
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#66Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#67Earlier quoted context omitted.
They might be more efficient, but by working 1/4 as much they're equally productive!
Exactly. You get paid for your output, not your effort. Edit: A deleted reply said “You don't even really get paid for output. Output theatre pays better than output.” Great insight I thought worth persisting.
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#68I avoid mentioning anything that points to topic-oriented Discord servers that are not yet 100% fedoras.
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#69Yeah I do this. Most of what I build, nobody knows about it nor is it release into the wild. Latest example: at my current workplace we have some crappy custom compilers for our platform.... I've rebuilt them in a way that I like (and using C# instead of Java), that enables me to use it in a small visual studio code plugin that enables me with real time error messages as I code against our platform, so basically cons…
A lot of people are assuming the worst intentions here but anyone who has worked in an enterprise knows sometimes it's useful to build tools for your use and not to share. The tool might not even be allowed, C# is probably not in the supported platforms and even if it was, getting it into the official repos can be arduous. If OP really cared about maximizing everyone's productivity of course they would share the tool…
Also, scaling tools to more than one user is incredibly hard. Software development is still custom / art. This tool works because it is suited to OPs workflow and his "way of thinking". In order to make it work for others, it needs lots of improvement and generalization, which is incredibly hard. Some people may even hate it, because they have their own best way to do things.
Devs should stop being delusional about their self-importance in these things. There are 100 other factors going on in an org and your one little tool ain't gonna make a penny difference in the profitability or productivity of the company (unless you have data to prove it, including impact on profitability)