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

If You Call Out Bad Code, Make Sure It's Bad First

naildrivin5.com

Post reply on HN
Print view View original

121–130 of 134 posts

Re: If You Call Out Bad Code, Make Sure It's Bad First

#121

Post by MartinCron »

rjzzleep wrote: post #119
reinhardt wrote: post #54

Earlier quoted context omitted.

Missing option: grow a thicker skin and don't take everything personally.

she chose to read it. it's not like someone rubbed it in her face. well someone told her about it. just like she chose to read the good things, she chose to read the bad things. SHE CHOSE. people seem to ignore that little fact, instead they result to writing meaningless essays, on how to apply their opinion as a universal standard to life. nothx

This is the first time I have seen the "blame the victim" approach applied to public ridicule. So I guess that now I have seen everything.

Re: If You Call Out Bad Code, Make Sure It's Bad First

#122

Post by rjzzleep »

MartinCron wrote: post #121
rjzzleep wrote: post #119

Earlier quoted context omitted.

she chose to read it. it's not like someone rubbed it in her face. well someone told her about it. just like she chose to read the good things, she chose to read the bad things. SHE CHOSE. people seem to ignore that little fact, instead they result to writing meaningless essays, on how to apply their opinion as a universal standard to life. nothx

This is the first time I have seen the "blame the victim" approach applied to public ridicule. So I guess that now I have seen everything.

ok, see you're entitled to your opinion. you think i'm an idiot, and I think you're an idiot. but that's kinda besides the point. the thing with opinions is that's a little bit like taking a dump. everyone takes one, but it kinda is a reflection of what's in your digestive system.

look through the tweets. https://twitter.com/search?q=%40harthvader&src=typd

noone personally shoved it down her throat. it's new to me that you get personal messages for someone talking about your github repo somewhere.

the blame the victim talk is like saying getting personally assaulted is the same as someone getting his car destroyed after parking your car in front of central park in new york. sure you could argue that they did it solely, because they knew the person, but this is clearly not the case here.

Re: If You Call Out Bad Code, Make Sure It's Bad First

#123

Post by e4c5shev »

zeeg wrote: post #80

If you call out bad code, you call out bad people? Half of you included, look at the ridiculous shit you say, and how much more offensive you are than anything anyone originally said. Also this is great for a laugh: http://dl.dropbox.com/u/116385/Slingshot/Pictures/Screen%20S...

The problem with being rational is that you are dealing with people that don't seem to like you, or have taken to disliking you.

Re: If You Call Out Bad Code, Make Sure It's Bad First

#124

Post by MartinCron »

rjzzleep wrote: post #122
MartinCron wrote: post #121

Earlier quoted context omitted.

This is the first time I have seen the "blame the victim" approach applied to public ridicule. So I guess that now I have seen everything.

ok, see you're entitled to your opinion. you think i'm an idiot, and I think you're an idiot. but that's kinda besides the point. the thing with opinions is that's a little bit like taking a dump. everyone takes one, but it kinda is a reflection of what's in your digestive system. look through the tweets. https://twitter.com/search?q=%40harthvader&src=typd noone personally shoved it down her throat. it's new to me th…

I don't think you're an idiot, I just think that saying it is all her fault because she chose to read the horrible things that high-profile people were broadcasting about her work is not a very good analysis of the situation.

It doesn't take long to read a tweet, and you can't exactly un-read it if you find it to be deplorable.

Re: If You Call Out Bad Code, Make Sure It's Bad First

#125

Post by MartinCron »

benatkin wrote: post #45
CodeMage wrote: post #29

Earlier quoted context omitted.

Agile? Could you elaborate on that?

To me, both this and the original complaint, come from dogmatic sentiments like "Legacy Code is Code Without Tests". http://www.kjetilk.com/2009/02/legacy-code-is-code-without-t...

The actual truth is that legacy code is code that works well enough for people to care about

Re: If You Call Out Bad Code, Make Sure It's Bad First

#127

Post by SyneRyder »

MartinCron wrote: post #74
CodeMage wrote: post #27

Earlier quoted context omitted.

Let's face it, there seems to be nothing anyone can share on the Internet without someone else demonstrating John Gabriel's Greater Internet Fuckwad Theory [1]. I'm not saying everyone should always just let it slide, but try not to let it get to you, either. [1]: http://www.penny-arcade.com/comic/2004/03/19

I have shared literally thousands of photos on Flickr. Nobody has told me that my photos shouldn't exist of that my photos make their eyes bleed. Can we, as a community, be at least as nice as serious amateur photographers?

Perhaps you haven't found "You Are Not A Photographer" yet. Some photography communities have a similar level of snark and calling out others, sadly.

Re: If You Call Out Bad Code, Make Sure It's Bad First

#128

Post by philh »

rektide wrote: post #116
philh wrote: post #111

Earlier quoted context omitted.

I actually have been hoping to get feedback on whether people think https://github.com/ChickenProp/ds-debug is/could be useful.

a wire protocol for named context patches: you'd do better not writing your own wire serialization format, and instead adopting an existing transport: websockets, stomp, and MQTT all strike me as sufficiently stupid simple & end to end enough, or anything from thrift to zmq to flume for transport would be slightly more inter-linkable than your "length/json-payload" ad-hocracy. it's JS but you might enjoy node-webwork…

I did find myself thinking "this has to be a solved problem" as I was writing the socket code. Thanks, I'll look into those.

Re: If You Call Out Bad Code, Make Sure It's Bad First

#129

Post by taproot »

rektide wrote: post #115
5hoom wrote: post #81

Earlier quoted context omitted.

I've suffered pretty severe depression and anxiety for most of my adult life. While the idea that we should all just grow a thicker skin and 'just deal with it' is both understandable and practical given the nature of the internet - it just wont happen for me. I know myself well enough to have recognized that even a tiny drop of vitriol could have me questioning my every decision and shatter my self confidence for da…

please email tarballs to rektide+anongit@voodoowarez.com if you have code you have no aspirations for but wouldn't mind kicking out into the wild. i will eliminate author headers from the code and seed over p2p and make available. thank you for any sympathy you might have towards this request to let us syndicate your work.

And annonhub an anonymous github clone in 3...2...1...

Re: If You Call Out Bad Code, Make Sure It's Bad First

#130

Post by [deleted] »

ncallaway wrote: post #110
MartinCron wrote: post #93

Earlier quoted context omitted.

Actually, this makes me think... I don't think I've ever given feedback on an open source project. Maybe I, as someone horrified by Heather Arthur's story, have some sort of ethical obligation to provide constructive and helpful feedback to people. I'm not a great programmer, but I've been at this for long enough to have some useful opinions. Open invitation for my fellow HN community members: point me at a repo and…

This reminds me of the recent ShowHN of criticue ( http://criticue.com/ ). You could do something similar (or those guys could do it) where you provide feedback on other people's repositories in exchange for feedback on your repository. Sort of a community code review process.

[deleted]
Post reply on HN