Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Do you ever avoid submitting something on HN so devs won't ruin it?

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 312 posts

Re: Do you ever avoid submitting something on HN so devs won't ruin it?

#31

Post by Aardwolf »

BatteryMountain wrote: post #9

Yeah 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…

Real time error messages are useful, but I don't see how they could make you win 4x time

Re: Do you ever avoid submitting something on HN so devs won't ruin it?

#32

Post by albatross13 »

BatteryMountain wrote: post #9

Yeah 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…

Respect.

Re: Do you ever avoid submitting something on HN so devs won't ruin it?

#33

Post by wffurr »

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

Re: Do you ever avoid submitting something on HN so devs won't ruin it?

#35

Post by legrande »

Design by internal committees is largely a bad move since your users will always want decisions reversed, or call any new features 'feature creep' or over-engineering. There is a trend of design where secrecy is allowed because devs code for 'the developer experience' and not the 'user experience'. Striking a balance between those two is worth it IMHO. (If that means feedback from your users then so be it, but don't let the users dictate the whole of the system).

Re: Do you ever avoid submitting something on HN so devs won't ruin it?

#36

Post by hallway_monitor »

BatteryMountain wrote: post #9

Yeah 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. But if I'm working at a large enterprise and increasing productivity may only lead to laying people off I have exactly zero motivation to share something like this.

Re: Do you ever avoid submitting something on HN so devs won't ruin it?

#38

Post by hwbehrens »

> I thought we were supposed to have each other's back,

There are 3 to 4 million devs in the US alone -- with a sample of that size, you'll get the full spectrum of people. Heck, you'd probably find some that like that the dislikes were removed. From their perspective, by blocking your extension they're actually making the world a better place.

It's shades of grey all the way down.

Re: Do you ever avoid submitting something on HN so devs won't ruin it?

#40

Post by version_five »

northisup wrote: post #11
BatteryMountain wrote: post #9

Yeah 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…

wow, super happy I don't work with people like this.

Why would you care? He's not actively harming his coworkers, he's doing what is asked of him work wise, and his colleagues presumably are too - and are themselves getting apparently slack jobs if there is 6hrs per day of easily automated work. Imagine if your coworker told management about an efficiency hack that made you responsible for 4x the output per day. Would you rather work with that person?

Personally, I wouldn't want to work at a company that apparently is not incentivizing creativity. I'd rather work somewhere where I knew if I did something like this I'd get more money or career progression or something, not just more work to do. But I certainly don't blame the employee for this

Post reply on HN