Live data from Hacker News

How to Be a Programmer: A Short, Comprehensive, and Personal Summary (2002) [pdf]

doc.ic.ac.uk

11–20 of 58 posts

Re: How to Be a Programmer: A Short, Comprehensive, and Personal Summary (2002) [pdf]

#11
post #7

Okay, I’m going to be a little bit far out there. A lot of this seems to be grounded in the negative. “How to deal with x” how to “do y when z has failed”. Some of it technical and some of it interpersonal. Why have we created this sphere around programming? What makes /this/ profession so different from any other? And my believe is: nothing. It’s not hard. It’s not better. It won’t “eat the world”. Heck it probably…

Eh. Most major centers of power have large computing resources changing how they do things. Wal-Mart, for instance, as a basically non-tech company, leveraged computers for stocking and supply chains and became a culture-chaging retail giant. Computers have made their way into cars, and even toasters. We have high frequency trading (done by computers) majorly affecting markets. I could probably go on like this for a while. Eating the world, check.

As for not hard--I don't know. We have an unusually high paying career, which companies do not do out of the generosity of their hearts. They have a limited supply of people that can do it. Quite a few people show no aptitude at all. At the high end, it merges into pure computer science, with an essentially unlimited amount to know. So, you can draw badly, or become a professional artist. Certainly, a person can program badly, but I don't think you can call it "not hard" any more than you can call anything else "not hard".

I wouldn't, and don't, romanticize it. It often just sucks. And programmers can often come with pointless, inflated egos from some view that they do something special, and I would like to see a check on that and those pointless egos deflated. But "not eating the world" and "not hard" don't really check out, from my perspective.

Re: How to Be a Programmer: A Short, Comprehensive, and Personal Summary (2002) [pdf]

#12
post #7

Okay, I’m going to be a little bit far out there. A lot of this seems to be grounded in the negative. “How to deal with x” how to “do y when z has failed”. Some of it technical and some of it interpersonal. Why have we created this sphere around programming? What makes /this/ profession so different from any other? And my believe is: nothing. It’s not hard. It’s not better. It won’t “eat the world”. Heck it probably…

It never occurred to me that someone might disagree with that. Obviously sw development is not harder, more complicated or more important than any other trait.

Re: How to Be a Programmer: A Short, Comprehensive, and Personal Summary (2002) [pdf]

#13
post #7

Okay, I’m going to be a little bit far out there. A lot of this seems to be grounded in the negative. “How to deal with x” how to “do y when z has failed”. Some of it technical and some of it interpersonal. Why have we created this sphere around programming? What makes /this/ profession so different from any other? And my believe is: nothing. It’s not hard. It’s not better. It won’t “eat the world”. Heck it probably…

As some one with a lot of development experience - I don't see any problems with the authors comments.

Re: How to Be a Programmer: A Short, Comprehensive, and Personal Summary (2002) [pdf]

#14

I read through some of the Beginner section that I thought seemed inappropriate for beginners and found a number of grammar and punctuation errors. While trying to navigate the file I found that the page numbering shown in the Table of Contents is off by two pages. His advice on "difficult people" sounds like he is talking about a single, specific person but is doing so in a vague way and expects that to function as…

And your point is?

Re: How to Be a Programmer: A Short, Comprehensive, and Personal Summary (2002) [pdf]

#16

I read through some of the Beginner section that I thought seemed inappropriate for beginners and found a number of grammar and punctuation errors. While trying to navigate the file I found that the page numbering shown in the Table of Contents is off by two pages. His advice on "difficult people" sounds like he is talking about a single, specific person but is doing so in a vague way and expects that to function as…

And your point is?

What is yours? The point of the comment you're replying to is obvious. They provided some specific criticism of the material.

Re: How to Be a Programmer: A Short, Comprehensive, and Personal Summary (2002) [pdf]

#17
post #10
post #7

Okay, I’m going to be a little bit far out there. A lot of this seems to be grounded in the negative. “How to deal with x” how to “do y when z has failed”. Some of it technical and some of it interpersonal. Why have we created this sphere around programming? What makes /this/ profession so different from any other? And my believe is: nothing. It’s not hard. It’s not better. It won’t “eat the world”. Heck it probably…

No other profession has quite the same capacity to transform itself. Like blacksmiths, programmers are capable of building tools that not only change the way they work but enable new kinds of work to be done, often by making previously onerous tasks trivial, and giving the individual a much large potential impact. Unlike blacksmiths, programmers can share their inventions with the entire industry in the blink of an e…

You should watch Primitive Technology on youtube: https://www.youtube.com/channel/UCAL3JXZSzSm8AlZyD3nQdBA

Re: How to Be a Programmer: A Short, Comprehensive, and Personal Summary (2002) [pdf]

#18
post #4

I honestly don't even understand the title, write code? How to become a better programmer makes some kind of sense, though the short answer is similar: write more code. Which leaves no time to fill the ether with noise, so it's a double win. How does this end up on the front page in the first place?

Boys; I've got this:

Because the chapters for instance under 2.0 are absolutely spot on.

Edit:

The rest are absolutely as well. Are what you say? Spot on!

Re: How to Be a Programmer: A Short, Comprehensive, and Personal Summary (2002) [pdf]

#19
post #7

Okay, I’m going to be a little bit far out there. A lot of this seems to be grounded in the negative. “How to deal with x” how to “do y when z has failed”. Some of it technical and some of it interpersonal. Why have we created this sphere around programming? What makes /this/ profession so different from any other? And my believe is: nothing. It’s not hard. It’s not better. It won’t “eat the world”. Heck it probably…

What "we"? This was written in 2002 (16 years ago), as it says in the title. I think your outrage is excessive.

Re: How to Be a Programmer: A Short, Comprehensive, and Personal Summary (2002) [pdf]

#20
post #9
post #7

Okay, I’m going to be a little bit far out there. A lot of this seems to be grounded in the negative. “How to deal with x” how to “do y when z has failed”. Some of it technical and some of it interpersonal. Why have we created this sphere around programming? What makes /this/ profession so different from any other? And my believe is: nothing. It’s not hard. It’s not better. It won’t “eat the world”. Heck it probably…

At some level of abstraction all jobs can be made to look similar. It's just not particularly useful to abstract to that degree. I think if you look in the communities formed by any groups of people sharing professions, you'll find a similar magnification of the importance and uniqueness of that profession: humans generally have a tendency to find the stuff they spend the most time around more significant, and often…

I'd say it's at least on par with accounting and finance which are pretty ubiquitous in our society.
Post reply on HN