Live data from Hacker News

Why I don't write about programming and why it's not really worthwhile to do so

marco.org

71–80 of 97 posts

Re: Why I don't write about programming and why it's not really worthwhile to do so

#71
post #36

Earlier quoted context omitted.

This is something that has bothered me a lot in the past. Other engineers build bridges and towers and monuments that stand for years and years. The beautiful code written by a good programmer might be replaced 8 months later by a junior who doesn't understand it. I suppose in our profession we are able to perpetuate ourselves by communicating our ideas into the world. Our influence is felt in posterity through the i…

Comparing a Rails library to a bridge isn't quite right. Most things lone hackers write are bike sheds and family homes. No one builds a bridge alone. You want a legacy? Move up the food chain and start discovering new data structures and algorithms. Or work on a large project like GMail.

[deleted]

Re: Why I don't write about programming and why it's not really worthwhile to do so

#72
post #8

Earlier quoted context omitted.

I think another reason for this behavior is that programmers often define their identity in terms of their preferred tools (you're a " Perl programmer", not merely a "programmer"). That means that any perceived slight against a programmer's preferred tool must be aggressively defended -- hence the abundance of religious arguments about "$X is better than your favorite language."

I think there's a very similar dynamic at work in politics, where people self-identify as a particular party or supporter of a particular ideology, an then take any criticism, however mild" of that party or ideology as a personal attack upon their very identity.

pg has an essay about this very idea: http://www.paulgraham.com/identity.html

Re: Why I don't write about programming and why it's not really worthwhile to do so

#73
post #67
post #58

Earlier quoted context omitted.

Can't you just have the YC alumni ban or temp ban people from HN when they post nasty comments? Seems like you accomplish two goals: (1) You don't have to read nasty comments about your writing and (2) you help slow the decline of HN. If it's a site wide policy and someone other than you is doing it, you'll probably be able to avoid accusations of censorship. Of course, that only works if the comment falls into the o…

Actually what I've been thinking of doing is have the users do that, by flagging comments for incivility. I haven't decided yet exactly what to do, but I'm ready to try something, because it is a sitewide problem. As we get more users, I'm seeing more comments that are nasty or fluff (or both).

Excellent. This should help, although unfortunately such a system is only as good as the average quality of the user-base.

That's why I advocate selecting a group of trusted users to do it instead. Its non trivial to select this group correctly, but I think the end result is more effective. Over time you can expand this group based on the users that have the highest percentage of civil comments. Once you get the ball rolling, the group simply scales as the site gets larger.

Re: Why I don't write about programming and why it's not really worthwhile to do so

#74
post #41

I think it's just as well not to allow comments on one's site. If someone wants to say something about something you've written, they can say it on their own blog or on Twitter. When it's something of theirs they're writing on instead of something of yours, they think twice before being jerks: most people won't create a whole blog post just to make a trollish comment, and someone whose Twitter stream is a series of n…

If someone wants to say something about something you've written, they can say it on their own blog or on Twitter.

That sounds like an idea for yet another Twitter app: make a widget that displays a Twitter search for a blog post specific #tag, e.g. #m_eiman12 for by 12:th post. This will make it harder to be anonymous (not difficult, but at least a few more steps), and with an added filter to allow "deletion" of unwanted tweets should help keep it civil.

Even better, from a usability and SEO perspective, would be to use the actual URL of the post instead of a tag, but most URLs are probably too long. Maybe with a shortened URL, but they're Evil. Having a link makes it trivial for followers of commentators to find and read the post in question.

Re: Why I don't write about programming and why it's not really worthwhile to do so

#76
post #60
post #59

Earlier quoted context omitted.

What would the consequences be if you dramatically amped up the censorship here? Certainly it would improve discourse at the expense of inspiring lots of hatred...

It might also inspire unrest à la reddit when the HD-DVD keys were posted to the site.

I think it was Digg that failed at removing the keys. I remember Kevin giving a speech about failing to listen to his users.

Re: Why I don't write about programming and why it's not really worthwhile to do so

#77

"... He has outlasted the relevance of all of them. His first articles would have been frontpaged on whatever came before Slashdot. ..." Not quite true. Slashdot is from about '96 and JOS is from about 1999-2000. Could the real reason be a bit simpler as suggested Joel is running out of new ideas? Is it possible the upcoming IPO might also play part? "... I can’t, which is one of the reasons why I rarely write about…

> Not quite true. Slashdot is from about '96

I think you’re misreading. The author was saying that Joel’s posts would have been just as relevant before slashdot as they are today, not that the posts actually predate slashdot.

Re: Why I don't write about programming and why it's not really worthwhile to do so

#78

Comments are disproportionately critical and/or argumentative, but that's because it's a waste of bandwidth to post a comment saying, "I agree!" That's what the up-arrow is for.

Is this what the up arrow is for? I'd rather, insightful, funny, factual. Posting for consensus is pretty pointless in my opinion. Not that it's particularly obvious what that arrow is for in the first place.

Re: Why I don't write about programming and why it's not really worthwhile to do so

#79
post #41

I think it's just as well not to allow comments on one's site. If someone wants to say something about something you've written, they can say it on their own blog or on Twitter. When it's something of theirs they're writing on instead of something of yours, they think twice before being jerks: most people won't create a whole blog post just to make a trollish comment, and someone whose Twitter stream is a series of n…

I've learned to be careful about whom I discuss things with. If you talk to the wrong crowd, all you're going to get is unreasonable and angry people. People have to be primed and qualified before you share too much, or else they will react violently to your message.

I don't think that there's any problem with disagreement or common and civilized discussion. The problem arises when the discussion turns into a contention, and the contention gives into resentment, bitterness, name-calling, etc. Once something has devolved that far, it is generally irredeemable, so if you things heading down that path I think it's more often better to just leave it, even if the original comment is inflammatory and accusatory, because those people have already forsaken reasonability and intelligence (usually as a response to being stumped), and what's the point in discussing a thing with one like that, or one whose biases are immovable and emotional?

Re: Why I don't write about programming and why it's not really worthwhile to do so

#80
post #3

I'd say it's not worthwhile to write about programming if people already have high expectations for you. Spolsky is definitely well-known and some people probably view him as somewhat full of himself, so they like to pick out anything that might hurt his image. For the average joe schmoe programmer, people don't have such expectations, so there is far less negative reaction. Also, personality does play a huge role. S…

Most of the generic pontificating I find on the run-of-the-mill programming blog just seems like a marketing ploy to me. I worked with a guy who updates his blog almost every day, sometimes more than once, and always syndicates it onto Facebook, but it's all for marketing, and it's really annoying, because the post basically just boils down to "X is cool, here are a few paragraphs about what I like about it, I can implement it for your business!"

On the other hand, posts that are informed by real-world experience and stories that discuss specific implementations are almost always at least somewhat interesting. This is what Joel came up on; he became well-known because his blog detailed hiring practices and how they've worked out for his company, certain strategies and fallacies at Juno, Microsoft, and Fog Creek, and the outcomes of them, and informed analyses of progress at the institutions wherein he has specific knowledge (primarily Fog Creek, I reckon).

Joel's posts were interesting because he had a lot of stories and a lot of anecdotes to back them up. His blog doesn't simply say, "I think if you give programmers offices with good equipment you'll end with some pretty good programmers", but "I thought if you gave programmers offices and good equipment you'd get good programmers, so here at Fog Creek we do that. Here are some pictures. When I was at Microsoft, everyone was sad because middle-management got the glory and the offices. At Fog Creek, we focus on our programmers, and it greatly increases our productivity, morale, etc.". One of these is much more interesting.

Post reply on HN