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

241–250 of 312 posts

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

#241

Post by visarga »

Sohcahtoa82 wrote: post #218
ClumsyPilot wrote: post #141

Earlier quoted context omitted.

Nobody cares about 'the company' - "In US the average share holding lasts just 22 seconds" Management can break the law, leave with their bonuses, and years down the line 'the company' gets fined. Employees are the ones that might be there for decades, but the anglosphere shareholder model allocated 0% stake to employees. TThere are alternatives: Codetermination in Germany is a concept that involves the right of work…

> Codetermination in Germany For some reason, at first, I read this as "Code termination" (not co-determination) and thought it was a mistranslation of some German compound noun, and I was confused.

TTS on Mac also reads it as "code termination"

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

#242

Post by dylan604 »

slingnow wrote: post #96
dylan604 wrote: post #61

Earlier quoted context omitted.

Seems like better time spent on looking at how to get out of shitty org than gaming the system

I'd be curious to see why you're so confident that OP's time is better spent getting out of this organization where they can work 2 hours a day for what I assume is a decent living.

Financial wellness !== mental wellness.

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

#243

Post by zentiggr »

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.

A lot of places would see someone not following development guidelines, doing something unsanctioned, or otherwise not fitting in to the expected culture.

That can be far more toxic pushback to any attempted improvement.

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

#244

Post by cole-k »

KennyBlanken wrote: post #213
pavel_lishin wrote: post #101

Earlier quoted context omitted.

Commenter complaints about negative, unproductive responses to things they've posted; immediately gets negative, unproductive response.

It's not unproductive and it's clearly poking fun. "Had one bad experience, never did it again" is, to put it bluntly, immature. "Only do things that immediately result in a positive experience" is a great recipe for a life and career that descends into grey nothingness.

I think it's just a difference in attitude.

Some people (like myself) prefer to be treated with more respect than a snarky comment. You can attribute that to being sensitive if you'd like.

I think other commenters think more along the lines of, "It's the internet, I'm (sort of) anonymous, if you don't like what I say, T.S."

Personally, I think that aside from being rude, the comment in question ignores the fact that the original commenter stated they saw other people receive snarky responses, and after receiving those responses themselves decided they'd rather not be criticized. I think they'd know better whether their life or career require exposure on HN.

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

#245

Post by dylan604 »

cyberge99 wrote: post #126
dylan604 wrote: post #59

Earlier quoted context omitted.

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.

Right, so if company finds out that you have code written on company time meant to be used to do company work, company can then say that all employs must be able to use that code. OR they could say that you can no longer use that code. No longer abiding by either mandate could be cause for dismissal.

Legal construct or not, it is a work product that would be owned by the company. Using that code at a new company would be wrong as well.

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

#246

Post by boringg »

wccrawford wrote: post #211
willcipriano wrote: post #55

Earlier quoted context omitted.

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.

It's simple: What's the company's response to the tool? Is it a percentage of the money saved? Absolutely not. Is it a raise? Unlikely. Is it a pat on the back? Maybe. Is it more work, and a lot of pain supporting the tool in ways it was never meant to be used? Absolutely. And it'll also mean a larger workload and more stress now that the company knows how much easier the job is now. With that outlook, why would they…

And maybe once they find out how long you've had such tools you now get a lot of grief and blowback for not sharing sooner even given that list you just wrote. Could easily be a fraught situation.

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

#247

Post by dang »

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.

We've banned this account for breaking the site guidelines.

If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow the rules in the future. They're here: https://news.ycombinator.com/newsguidelines.html.

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

#249

Post by spc476 »

afrodc_ wrote: post #152
CrazyStat wrote: post #91

Earlier quoted context omitted.

> Increasing productivity never lays people off, unless the people were originally being unproductive. Maybe in some imaginary world with spherical cows, infinite demand, and no friction (physical or transactional). In the real world, increasing productivity so that one person can do the job that ten used to do very often results in layoffs. 70 years ago there were hundreds of thousands of telephone switchboard opera…

This is so true. Anecdotally, my dad worked in FABs on chips and stuff in the 90s during the dot com boom before they stripped all those jobs away to outsourcing and it basically destroyed him as an older man. Funny how we're desperately trying to get the silicon manufacturing back after we sold out.

"Hey, it improved the financials since it moved from capex to opex. Also, I got my bonus and jumped ship before the excrement hit the cooling unit."

Yeah, several years ago, our corporate overlords sold off a database we created to a competitor and leased it back from them. Now, we're trying to recreate that database to avoid the financial overhead. I'm sure at the time it made sense to some bean counter but it was penny-wise, pound-foolish in the long term.

I think now it's impossible to think long term financially. Thanks, Wall Street.

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

#250

Post by benhurmarcel »

dylan604 wrote: post #59
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…

And how do you get around the concept of any code you write on company time, on company resources is owned by company?

It’s unenforceable if they don’t know about it.
Post reply on HN