31–40 of 175 posts
This conversation reminds of the old programmer joke: How many programmers does it take to screw in a light bulb? Five. One to screw in the light bulb and four to say, "I could have done that."
none. it's a hardware problem.
Someone should research this. Every-single-time a nice little community starts expanding rapidly all the construction is gone and all we're left with is the destruction. Reddit and HN being the most recent examples I can think of. For a throw back: Anyone remember GameFAQs of 1998? Go check it now.
Took a break from HN (and others) for about 8 months at the end of 2012 and start of 2013. The HN I came back to feels very different. Everyone knows better and is eager to prove it by putting others down. Comments are no longer about the OP, but about how the OP is laughable, let me tell you how to do it . So sad.
Earlier quoted context omitted.
Offtopic, but a quick googling led me to this: http://www.cs.bgu.ac.il/~omri/Humor/lightbulb.html Fun read!
Off-Offtopic! But I loved this one: How many Prolog programmers does it take to change a light bulb? False.
NaN.
For example, you can find this behavior when someone posts something about problem X and there is a minor grammatical mistake or an opinion that is expressed in the post that is unconventional. The comments section will zero in on that and miss the big picture.
Earlier quoted context omitted.
Offtopic, but a quick googling led me to this: http://www.cs.bgu.ac.il/~omri/Humor/lightbulb.html Fun read!
Off-Offtopic! But I loved this one: How many Prolog programmers does it take to change a light bulb? False.
?Sometimes OPs are wrong or misguided and somebody with more experience or expertise is there to point out why.
That's valuable.
Often you hear from the creators of things. Folk who are at the coalface of some system, company or problem.
That's valuable.
So sometimes it comes with a bit of grunge and grump. I don't really care. The rest is worth it.
- Huge projects which are still understandable within minutes,
- Products which handle special cases, which in turn amaze its users (when the dev has managed to get beyond her own use cases),
- and devs who write more elegant code than me (clever use of patterns, readability, yadayada).
It's easy to sniff at another dev's code, since nobody's perfect, and code is often a compromise of a conflict of various factors (and each conflict can be solved in various ways). But, this loop which has a workaround for a off-by-one error which is caused elsewhere - has likely been written under time pressure, and I might someday make the same mistake. I think it all boils down to dev compassion.