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

301–310 of 312 posts

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

#301

Post by [deleted] »

uhtred wrote: post #42
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…

I get this. If you tell people, and it gets released into the official tool chain, you will also probably then be its "owner". More work for you with no extra money.

[deleted]

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

#302

Post by BatteryMountain »

uhtred wrote: post #42
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…

I get this. If you tell people, and it gets released into the official tool chain, you will also probably then be its "owner". More work for you with no extra money.

We do currently have an abandoned tool in our chain that was built about 4 years ago but the guy ran away. We have yet to untangle his mess. Our operations/devops units kicks heavily against stuff like this for this very reason.

Unless I can guarantee myself (and them) that my tool will be a very tight integration with the rest of the system and not become a wart, then I rather won't introduce it. It has to fit properly with the rest of the puzzle.

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

#303

Post by BatteryMountain »

Hekioi wrote: post #122
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 that's a next level shitty. Holy shit. I would not want you and your philosophy around me at all.

I've taken the time this morning to read and comment on all the messages below my original comment. Please read them with empathy. The decisions are not coming from a malicious place.

It is important to know when to leave your mark in the world and when not to. Sometimes it is better not to inflict my own way of life onto others. Just because it makes me work better doesn't reduce other people's efforts. And with the extra time I gain, I do still use it for work stuff, but not on the mundane stuff. I also work in the slow behemoth industry known as Healthcare, so introducing new things carry a ton of risk in our domain and some personal risk. It really depends on the situation, the people/company involved the domain, the government and how formal/academic things are. Context is everything.

My preferred alignment is Neutral in DnD terms. Specifically in this order: Chaotic Neutral, True Neutral and then Lawful Neutral. It's amazing how well the DnD alignment matrix fit onto real life situations. I don't even play the game.

I hope my comments in the conversations on this topic helps others navigate and balance this kind of problem that we all face at one point or another. Introspection and empathy helps a ton in this case. Don't just think about how it will improve other's lives, but also the consequences if things goes wrong. If you ignore the dark side of your invention, you might be blind sided by those consequences when they appear. Then you are forced to pick a side: either support and fix your creation or shrug your shoulders and tell yourself that you don't care. That has it's own set consequences, both for others and your own mind.

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

#304

Post by BatteryMountain »

jayd16 wrote: post #51
version_five wrote: post #40

Earlier quoted context omitted.

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…

Assuming its not trivial, its hiding a useful tool from your coworkers. Why share any knowledge at all? Why mentor someone if it just gets them more work? Seems pretty toxic to me.

Cause some of the tools are completely outside of the scope of work or company culture or tech stack.

We do share knowledge but not all of it is relevant, so not every little thing needs sharing. If I come to meeting and share everything in my head I might as well crab a box to stand on and preach to the clouds. I'd rather just get on with things than trying to convince people of my way of working.

No toxic intentions involved here.

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

#305

Post by BatteryMountain »

Philip-J-Fry wrote: post #28
toomuchtodo wrote: post #17

Earlier quoted context omitted.

You wouldn’t know if you did.

I would because they'd be more productive than me.

To be honest, I try my best to conceal my gains. I intentionally time my feedback to when it is expected of me.

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

#306

Post by BatteryMountain »

bsder wrote: post #257
uhtred wrote: post #42

Earlier quoted context omitted.

I get this. If you tell people, and it gets released into the official tool chain, you will also probably then be its "owner". More work for you with no extra money.

Agreed. Ownership sucks and everybody will duck it even if they depend upon it. Back in the Bad Old Days(tm) when disks still spun and displays weighed as much as a human, all manner of crap used to go into /usr/local but nobody would ever own it--consequently, you'd have knife fights over versions of Perl, for example. Eventually my VP turned to me as a noted BOFH and asked "This is getting out of hand, should we ju…

Thank you for sharing. I've had one or two similar events over the years. I think often times people don't even know that they are indirectly using something or have indirect ownership of something. Only when switching it off does it get crystalized.

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

#307

Post by rurban »

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…

This only help msvc devs, who are in vendor lockin disadvantage anyway, and are always 10 hrs behind.

Normal people used flymake on emacs for the last decades, recently switched to LSP feedback or VScode.

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

#308

Post by Amorymeltzer »

matheusmoreira wrote: post #267
Amorymeltzer wrote: post #129

Not 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 a…

> the author started getting harassed off-site Because of a post here on HN? What happened?

Negative, sexist, belittling comments, and a fair bit of https://xkcd.com/385

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

#309

Post by dkersten »

awillen wrote: post #274
dkersten wrote: post #21

Earlier quoted context omitted.

For work sure, but it also sounds to me that it was built during personal time. If I use my own time to make something, work isn’t getting it without paying for it. I don’t care what the contract says about personal projects (although I‘ve also never signed one of those “we own everything you do outside of work” clauses because I find them exploitative and abusive)

I agree with you on the personal projects stuff and have also had that language struck from contracts (I've published a couple of short books on Amazon and had one contract that pretty clearly said my employer would be entitled to profits from those books... pass). But in terms of building it on personal time, I'm iffy on that. Obviously in tech the time tends to blend together... I've worked on weekends but also spe…

My contracts either stipulated set work hours or was contract work for which I billed for the hours. If the project is completed outside of the stipulated work hours or not billed for and not using company resources such as computers, then they have no claim to it.

If I’m meeting my contactual obligations, anything more is mine. If I go above and beyond, then that is, essentially, a gift from me to the company, because I’m only compensated for what the contract says I’m compensated for.

If I spend my leisure time to build something that makes my job easier, I see that akin to using the time to go to the gym or get more sleep because that also makes my job easier. If it’s my leisure time, what I do is my business even if it helps my work.

Of course we don’t know when this person built the tool and maybe it was done in a less clear way. I always try to keep things I do for myself clearly separate. Eg if I’m WFH and the last hour is quiet maybe I’ll also put some food on while I finish work, but I would never use that time to work on a personal project but rather wait until I’m clearly clocked out.

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

#310

Post by buildsjets »

Hekioi wrote: post #177
buildsjets wrote: post #165

Earlier quoted context omitted.

Compensate people appropriately for their contribution, and they will contribute. I prefer managers who pay me, rather than thank me. No Bucks, No Buck Rodgers.

And? You think you will not be seen as a very good developer companies want to keep? You can mention your optimization in every salary discussion etc.

I am not interested in your BS pull system. I do not beg for dollars. Very few people do what I do, and my skills are in high demand. Continuously and proactively compensate me, or I leave, and take my productivity and inventiveness to your competition. Fuck your annual salary review.
Post reply on HN