News for hackers. Stuff that matters.
Re:Programming is just like writing by nessus42 on Monday September 12, 2011 @04:25PM (#2988755)
Ableson and Sussman might beg to differ. From SICP:

  First, we want to establish the idea that a computer language is not just a way of getting a
  computer to perform operations but rather that it is a novel formal medium for expressing
  ideas about methodology. Thus, programs must be written for people to read, and only
  incidentally for machines to execute.
Re:Programming is just like writing by St-Clock on Monday September 12, 2011 @04:39PM (#2988814)
It's funny this came from SICP's authors because I always found that Lisp was harder to read/write than languages like Python which look like English.

I'm not saying one is better or that one is easier to maintain than the other, just that Python is really close to the pseudo-code, design notes, and specifications in English that I write. Not just logically, but syntactically.

In Java, I used to write some pseudo code in comments before attacking a particularly difficult method. I rarely do this in Python now.

Still Lisp can be closer to English than some Perl one liners :-)

Re:Programming is just like writing by Peaker on Monday September 12, 2011 @05:50PM (#2989031)
Python is close to the way you think, because the tools you use shape the way you think.

I write my pseudo-code in a Haskell these days.

Also, closeness to English does not help readability of programs. Programs are pretty close to abstract maths, so closeness to maths actually helps readability of a lot of the expressed concepts (e.g: Even Python uses mathematical notation for its arithmetic).

Re:Programming is just like writing by St-Clock on Monday September 12, 2011 @07:34PM (#2989311)
"Programs are pretty close to abstract maths"

For you and many people, yes. For me and many other people, no. I sometimes write math when I program, but more often, I manage. I assign roles and responsibilities. I orchestrate communications. I try to keep conflicts to a minimum. I often automate the way I think and I rarely think mathematically (that's how I wrote my Master's thesis and this is how I'm writing my Ph.D. thesis. I mean, the programs behind the theses).

"because the tools you use shape the way you think."

Yes... When you are starting to program or when you haven't been seriously exposed to other programming languages and paradigms, you are right. But I think I've been exposed to enough of these and made a conscious decision. For example, to me, prolog was immediately natural during my bachelor degree, but haskell felt more constrained.

Still, if I was primarily writing code in Lisp or haskell, I hope my pseudocode would be different. Otherwise, it would be quite a waste of time translating imperative programming to functional programming.

Re:Programming is just like writing by groovy2shoes on Monday September 12, 2011 @07:09PM (#2989242)
They're not talking about Lisp in particular. They mean that programming languages are a formal way to express computation. The formality of the languages happens to make them suited for machine use.
Re:Programming is just like writing by hxa7241 on Monday September 12, 2011 @04:38PM (#2988811)
They want to emphasise a point. But think of what is indispensible. If the program was unreadable -- maybe the source is lost -- you still have a running, useful, device. But if you do not have execution, you do not really have software anymore.

Software as function -- for execution -- and software as representation -- for humans -- must be pretty much equally important, in the end. But surely the key constraint, the definitive matter is what software does, what it is as an artifact. We can communicate about anything, but software is software because it performs some action.