No one cares at youtube whether people can or cannot make an extension that brings back the dislike count. If there is a way to do it, it might be intentional for guys like you to stay on the platform.
Do you ever avoid submitting something on HN so devs won't ruin it?
121–130 of 312 posts
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#122Yeah 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 that's a next level shitty.
Holy shit.
I would not want you and your philosophy around me at all.
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#123> I thought we were supposed to have each other's back An engineer's primary concern ought to be the engine. Preoccupation with popularity or feelings seems like a distraction to me.
I find that I am able to make the engine run more smoothly when my colleagues and I trust each other and can amicably discuss problems that come up.
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#124Yeah 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…
We are writing software!
It's our fucking job to optimize the world around us.
How do you think can we, as a society, advance while doing bullshit jobs?
Make me obsolete!
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#125I’ve been iterating and abstracting a project layout tool into just the right thing for about a decade.
It’s like remix and all those frontend bootstrap wizards/tools, but it bootstraps projects in any language with my preferences.
It prompts me to ask if it should fetch my favorite deps (Requests for Python, or my own go CLI builder since Cobra is to bloated and complex for my needs) depending on the language I’m using for the project. I don’t always need them but I can get them in place fast.
IMO using everyone else’s tools is boring. I don’t see a blacksmith getting tongs from another blacksmith. I can’t hope to be an expert if I just import experts code. Seeing something like bash and being expected to believe that means anything when I can just write my own; those old guys made syntax art which actually just made “computing” hard. That was job security as much as anything.
Too many people don’t realize listening to others tell you not to do X is just giving them a monopoly.
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#126Yeah 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…
And how do you get around the concept of any code you write on company time, on company resources is owned by company?
That’s a legal construct. The company owns it (in licensure), but he’s the sole user/operator if it.
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#127Earlier quoted context omitted.
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…
The question I have is how did incentives get so misaligned that this person feels that doubling the productivity of all their peers is unlikely to be worth the effort of presenting a tool.
Because making it work the way YOU want can be far easier than making it work the way 50, 100, 200 people want. And once they see you as a supplier of thing they'll expect you to give them what they want, because that is how people are.
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#128I mentioned something we built at work and got the typical HN nitpick about it and decided to never bring anything else up again. If something is open source and you don’t like just move along.
I think some of us are more sensitive to criticism than others (?). I'm like this. I have several projects that took me forever to showcase due to anxiety of negative criticism.
Advice given to me was to post your projects anyway and don't fret too much about the negative comments: you'll always always get a mix of negative and positive comments, everyone does, so don't take them personally.
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#129Not the same sort of thing as OP's example, but a while ago I found something simple and neat that made me think about code a bit differently. I shared it.
The first few comments were negative — not ideal but certainly okay! — but then the author started getting harassed off-site. I was contacted and immediately deleted the post.
Start to finish, the whole process took maybe 30 minutes, but it was sadly instructive and I think about it every time I submit something here. It's probably made me comment less.
Re: Do you ever avoid submitting something on HN so devs won't ruin it?
#130Earlier quoted context omitted.
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 wou…
He/she is blocking a head count for a person who would improve the success of our team and our company.
I prefer people who genuinely like to improve our whole environment than not.
Sharing and caring!