Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

A New Bible For Programmers?

Posted by timothy on Wed Jun 18, 2003 07:56 AM
from the squinty-little-eyes dept.
KZigurs writes "The wonders of online publishing... If you are ready to take on a heroic task and read thru all 976 pages of Concepts, Techniques, and Models of Computer Programming (draft) (pdf file, 3MB, intro here) written by Peter Van Roy and Seif Haridi you won't regret it. Just finished reading it and I feel like I have read the Bible. And who knows? It has the potential, and since current de facto books about programming are aging with increasing speed it very well may become one. (Please read the intro to get more detailed outlook at topics covered)
Anyone before heard about Oz?"
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Newer Copy Available (Score:5, Informative)

    by erasmus_ (119185) on Wednesday June 18 2003, @08:02AM (#6232262)
    I'm not sure why the article links to the April 26th draft version of the book, when the intro page itself has the link to the much newer June 5th version.

    http://www.info.ucl.ac.be/people/PVR/booksingle.pd f [ucl.ac.be]

    I look forward to reading it from the intro, however, might be really worthwhile.
  • So.. (Score:5, Funny)

    by dr ttol (674155) on Wednesday June 18 2003, @08:10AM (#6232323)
    Does this bible also make the prediction that something huge will happen at the end of the millennium?
  • by IdleMindUI (171872) <barry@barry r a n d a ll.com> on Wednesday June 18 2003, @08:16AM (#6232378) Homepage
    It appears that the site is already...umm...slashdotted. Google's cached HTML version can be found here. [216.239.39.100]
  • Anyone have it mirrored? I'd love to read/print it.
    • Mirror Here (Score:5, Informative)

      by Bluetrust25 (647829) on Wednesday June 18 2003, @11:09AM (#6234246)

      It's mirrored here [surveycomplete.com] courtesy of SurveyComplete.

      Incedentally, I highly recommend the book Code Complete: A Practical Handbook of Software Construction [amazon.com] by Steve C McConnell. It tought me more about programming than the rest of my computer book bookshelf!

      Another great resource is Safari [oreilly.com]. It's a web service that for a fee, allows you to view O'reilly, Que, and Sams books online. I find the code search feature to be invaluable. Cheap way to read technical books.

  • by tsa (15680) on Wednesday June 18 2003, @08:27AM (#6232458) Homepage
    I am not a programmer but this seems to me a very interesting book for people who want to have a detailed yet general (hope you understand what I mean) idea of what's going on inside their computers as they are hammering their keyboards. Seriously, popular books on computer programming usually learn you how to use a certain programming language and not the concepts behind writing a computer program so this is a must-read for all people that want to learn to program computers.
  • Another Bible (Score:5, Informative)

    by Ann Coulter (614889) on Wednesday June 18 2003, @09:01AM (#6232813) Journal
    Design Patterns [amazon.com].
    • I've got no mod points at the moment or I'd reverse the idiot who modded this offtopic.

      With luck, someone who does have points will jump in...

      -- MarkusQ

    • "Design Patterns" is something specifically targeted toward object oriented development. If you looked at the documented linked to in the article, you'll see that it covers the the entire wide-spectrum of programming techniques, of which OOP is just one small portion.
  • Already slashdotted? (Score:4, Informative)

    by stienman (51024) <adavis@@@ubasics...com> on Wednesday June 18 2003, @09:02AM (#6232825) Homepage Journal
    The google cache of the pdf (converted to HTML by google) is here. [216.239.39.100]

    -Adam
  • OutDated? (Score:5, Insightful)

    by peripatetic_bum (211859) on Wednesday June 18 2003, @09:04AM (#6232849) Homepage Journal
    since current de facto books about programming are aging with increasing speed


    I'm sorry to sound susppicious, but the concepts of programming are not out dated. The problem is tat programming has actaully become (or rather started out) incredible sophisticated and that a lot of programmers now have not been properly trained (be it by self study or a rigour CS program). And that flurry of programming books are more lke cookbooks and dont really *teach* anything anymore.

    I find it rather hard to believe that Knuth's analysis of algorithms of Sorting and Searching have/will become out dated. I think his title the ART of COmputer Programming was always incredible ironic because he has done more than anyone else to turn into a real science, which it is now, and by which I mean that it has hypothesis that can now be tested. His book lay the foundation for it and I doubt any new programming book, short of specilized computer journal articles have done much to advance programming.
    • Re:OutDated? (Score:4, Insightful)

      by Asprin (545477) <gsarnold&yahoo,com> on Wednesday June 18 2003, @09:30AM (#6233154) Homepage Journal

      I think his title the ART of COmputer Programming was always incredible ironic because he has done more than anyone else to turn into a real science, which it is now, and by which I mean that it has hypothesis that can now be tested.

      I disagree.

      Real science has proper control groups and reproducible results. Programming has neither.




      [/me grins, ducks and runs]

      • reproducible? Are you saying results cant be reproduced on computer? Im sure you are not saying that, please explain.

        Proper control groups? hmmm, are you thinking something like a placebo group? perhaps, but what I am thinking of is testing one algorithm against another, or using the say, a standard algorthm for sort (say, bubble sort) and being able to compare to another sort process and get empirical evidence (ie speed) of which one is better.

        I would say you have total control of the control group in
        • Re:OutDated? (Score:5, Interesting)

          by Violet Null (452694) on Wednesday June 18 2003, @10:54AM (#6234098)
          I think (hope) you're just pretending to be sarcasm-challenged when taking the parent post seriously.

          But, now that I'm on the subject...

          Once you've gotten your first non-reproducible bug, you'll see what the parent poster was talking about with reproducible results. An awry pointer can cause all sorts of havoc that's incredibly difficult to track down, and, even worse, it often won't break the same way twice.

          As for your example of algorithms: "better" is rather subjective, especially in regards to sorting algoriths. Although quicksort might be faster for general purpose use, there are plenty of algorithms that can beat it in certain conditions. And, programming being what it is, you can never be sure that your program will be running under those certain conditions or not.
        • Re:OutDated? (Score:5, Interesting)

          by Asprin (545477) <gsarnold&yahoo,com> on Wednesday June 18 2003, @11:14AM (#6234289) Homepage Journal

          Well, I was actually making an ironic joke, but since you ask, I can certainly give it another shove closer to the edge of the cliff, so to speak.

          First, let me say that I was actually serious when I said that programming (just like mathematics and logic) is not science.

          This opinion was not formed without a fair amount of consideration (BS in math, MA in physics). We could argue semantics for many moons, but my definition of a "science" goes something like "A course of inquiry which employs the proper scientific method: only ask questions you can actually answer, employ direct empirical observation with proper control groups, verify the results independently (one trial does not a conclusion make), and reserve nature as the authority - you must maintain a complete willingness to be proven wrong."

          Mathematics, Programming and Logic work this way because they conform to a different kind of rigor for validation -- namely, constructive or analytical "proof", which is not, by its nature, empirical. I'm not trying to refute, denounce or demean non-scientific studies, I just want to point out that "scientific" means something specific, and it does not apply to those other areas I mentioned.

          BTW, one pet peeve of mine is when in sci-fi movies, the dude says "There has to be some kind of scientific explanation for this." Well, no: METHODS are scientific, not explanations.

          Also, please note that many areas of study: Psychology, Sociology and Political Science (as well as certain areas of Biology and Chemistry -- needle, needle, jab, jab, ha-ha!) *could* be scientific in some cases, but typically aren't because they are populated by dumb researchers employing horribly poor experminental and analytical techniques.

          So, having said that, I will conclude with the "on-topic" tongue-in-cheek gags:

          Reproducibility: (In WRITING programs, not running them)
          Since all developers on a project typically work from the same source tree, no programming results have ever been independently verified except the programming assignments in textbooks.

          Control Groups:
          Well, maybe you have a point on this one. I suppose a NOP loop would qualify as an effective control, but how do you halt the experiment?

      • Real science has proper control groups and reproducible results. Programming has neither.?

        So, physics, chemistry, & astronomy, which don't have control groups, aren't science? Methinks you need to revise your definition of science to be more in line with what other scientists mean when they use the word "science".


        • Ultimately, yes, it does.

          The theoretical work is a critical component, but if we stop when the theory is finished and do not go into the lab to see if the model we have been working on is correct, we haven't done any science, just math.

    • Re:OutDated? (Score:3, Insightful)

      by egomaniac (105476)
      I find it rather hard to believe that Knuth's analysis of algorithms of Sorting and Searching have/will become out dated.

      Really? When's the last time you wrote your own implementation of a search or sort algorithm?

      I haven't done so in a decade. Every language I use has built-in implementations which are more than fast enough for my purposes. Likewise with virtually all such basic algorithms -- they have been implemented, and generally very well, in libraries. Computers are fast enough now that even a
      • by Sunlighter (177996) on Wednesday June 18 2003, @12:58PM (#6235260)

        There are two kinds of transistors, bipolar junction transistors and field-effect transistors. Bipolar junction transistors are sandwiches made from two layers of N-type silicon separated by a layer of P-type silicon. A bipolar junction transistor has three terminals: an emitter, a base, and a collector. The emitter and collector are connected to the N-type silicon (on opposite sides of the sandwich) and the base terminal is connected to the P-type silicon. When a small voltage is put on the base terminal, current is allowed to flow from the emitter to the collector. (This is for an NPN-type transistor. There is also a PNP type which is the opposite and works with negative voltages instead of positive.)

        A field-effect transistor has three terminals, too, but they are called the source, the gate, and the drain. The source and the drain are connected by a channel made of N-type silicon, but the channel is somewhat narrowed by P-type silicon in the middle which is connected to the gate terminal. When you put a voltage on the gate, it creates an electric field which chokes off the current flow from the source to the drain. There is also a type of field-effect transistor with a channel made of P-type silicon, and the voltages are negative.

        I have done better than implementing a sort algorithm; I implemented keyless 2-3 trees in a functional style and thus speeded up my LR(1) parser generator from 27 minutes to 4 minutes.

        The work of people like us makes the work of people like you possible. So: nyah nyah na-nyah nyah.

        • The work of people like us makes the work of people like you possible. So: nyah nyah na-nyah nyah.

          Huh? I never said that I didn't know how a transistor (or parser, for that matter) works. I said that most people around here probably don't, and I'd still bet a hefty sum of money on that.
        • The work of people like us makes the work of people like you possible.

          I hope this was meant to be sarcastic. Everyone makes everyone else's work possible. Otherwise, there would be no such thing as an economy nor such a thing as progress.
        • Its obvious you have only a passing knowledge of transistors, and as such, couldn't truly comprehend what is going on in your computer.
          No talk of valence vs. conduction band, no talk of doping concentrations, no talk of electron current vs. Hole current; good sir, you have given semiconductor physics a slap in the face with your cursory knowledge! You're the type who'd forget body effects ignore adding a contact to the substrate! Phillistine!

          (P.S.- this is a joke. Laugh. Except for forgetting the substr
      • Re:OutDated? (Score:5, Informative)

        by Arandir (19206) on Thursday June 19 2003, @01:11AM (#6240385) Homepage Journal
        Just like long division, there are times when you need to write your own search or sort algorithm. Why?

        1) Sometimes it's easier to write your own sort than to write a weird ass adaptor for your weird ass data.

        2) Sometimes "good enough" isn't "good enough" and you need that extra 15% performance increase you get for writing a search/sort customized for your data.

        3) Actually knowing how stuff works is good for the brain. After you learn basic bonehead algorithms, take some time to learn long division as well.

        4) Just to prove that you aren't a code monkey destined for the dustheap of history when you turn thirty.
      • I'm not saying that it is useless to know how sort algorithms work, but suggesting that it's relevant in the day-to-day work of a typical software developer (which is what you seem to be implying) is very misguided, in my opinion.

        On the contrary. In my experience, an awful lot of programmers, mostly those who are self-taught but don't realise what they're missing, frequently choose an incorrect data structure or algorithm even for simple things like sorting and searching. If you're working in a field wh

    • Re:OutDated? (Score:3, Insightful)

      by oni (41625)
      I find it rather hard to believe that Knuth's analysis of algorithms of Sorting and Searching have/will become out dated.

      It's too bad that you mentioned searching and sorting because it seems a lot of the other replies here jumped on that issue and completely missed your point.

      The Art of Programming isn't about either of those topics. It's about algorithms. Knuth uses seaching and sorting as a means to the ends of teaching the programmer to think about his algorithms. As other people have pointed out,
      • Re:OutDated? (Score:3, Insightful)

        I agree, and I think much of the misinterpretation comes because many are commenting on Knuth without ever having really read it. This comes from the introduction to TOACP.V3 2nd edition(which is from 1998 by the way, not so ancient):

        The title "Sorting and Searching" may sound as if this book is only for those systems programmers who are concerned with the preperation of general-purpose sorting routines or applications to information retrieval. But in fact the area of sorting and searching provides an i

      • Re:OutDated? (Score:5, Insightful)

        by Oscaro (153645) on Wednesday June 18 2003, @10:20AM (#6233725) Homepage
        Gnahhhrrrrg I keep hearing this argument over and over. But knowing how to do things right (and why) is the ONLY way to survive to new problems and situations that the STL does not solve.

        That's one of the reason I hate Java. Its huge library lets you write programs without having to learn or understand what the hell you are doing.

        Thanksfully, when I learned to program, I had to code my own hashtables.
          • One can desire to understand how a good hash table algorithm works without coding their own (except as an exercise in understanding, perhaps?)
      • I don't know about you embedded and systems folks, but we use a database to do that stuff now. Lacking are teaching guides that tell how to use a database properly and effectly within an application. I am not saying that building sorts is useless knowledge, but its priority is dropping IMO.

        I understand where you are coming from and if you catch me in the right mood I might agree (almost) without reservation, but I have some doubts. There are certain programming tasks that just can't be solved with a pred

  • It looks like it takes the /. crowd some time to go through nearly a thousand pages before they post comments.

    More interestingly, it seems may are actually RTFBing.

    Oh, I just hope no karma whore posts the book here. 8-)

  • by joelparker (586428) <joel@school.net> on Wednesday June 18 2003, @10:50AM (#6234057) Homepage
    The book uses the Mozart Programming System [mozart-oz.org]

    Mozart & Oz are well-developed and worth a look--
    your programming may improve because of them.

    Cheers, Joel

    p.s. here are quick excerpts:

    The Mozart Programming System is an advanced development platform for intelligent, distributed applications. The system is the result of a decade of research in programming language design and implementation, constraint-based inference, distributed computing, and human-computer interfaces...

    Mozart is based on the Oz language, which supports declarative programming, object-oriented programming, constraint programming, and concurrency as part of a coherent whole...

    We have developed many applications including sophisticated collaborative tools, multi-agent systems, and digital assistants, as well as applications in natural language understanding and knowledge representation, in scheduling and time-tabling, and in placement and configuration.

  • Oz (Score:5, Interesting)

    by thelenm (213782) <mthelen@gmai l . c om> on Wednesday June 18 2003, @10:59AM (#6234154) Homepage Journal
    Yep, we had to use Oz in a Programming Languages & Semantics course I took in grad school. All I really remember is that it used "constraints" rather than "values" for variables. For example, a variable doesn't necessary contain a single value, but it might contain the constraint "greater than 100, less than 2000". And you can do all kinds of stuff with intersection and union of constraints, and... ahh, that's all I can coerce out of my brain. I thought I had repressed it forever. :-)
  • by Anm (18575) on Wednesday June 18 2003, @11:08AM (#6234242) Homepage
    For those curious why this books uses Oz as it's language of choice, it is one of the few, if not the only language, to support the many popular paradigms of programming:
    * procedural, like C & BASIC
    * object-oriented, like Ada & Java
    * functional, like Scheme & Haskel
    * declarative, like Prolog

    It that way, this book is a good way to keep your mind open to different approaches to doing things.

    Anm
  • hmm (Score:4, Interesting)

    by rpeppe (198035) on Wednesday June 18 2003, @11:48AM (#6234555)
    I'm a bit dubious about a book that talks about the "substitution property" of objects without once mentioning Liskov's [mit.edu] substitution principle [objectmentor.com], or that talks about message passing concurrency wthout mentioning Tony Hoare's CSP [usingcsp.com].

    Is this book really as authoratitive as it tries to appear?

    • It is a draft copy, and there is contact info on his site, why not let him know that?
    • Re:hmm (Score:2, Interesting)

      by KZigurs (638781)
      Most probably no. But then - what is? If it would pretend to be JustAnotherBookFromThatLibrary noone would be interested to read it. And as for the contents - anything may miss something, but if it is good writen, easly readable and actually lets you have a look from a different perspective - it very well may be worth reading. :D
    • Is this book really as authoratitive as it tries to appear?

      I had a quick scan over it, and while I'm reluctant to judge on first impressions, I couldn't help feeling that it had a lot of breadth but not much depth. It struck me as somewhat similar in style to the wizard book [mit.edu], though obviously with wider coverage.

      I had the same immediate reservation as you did: the OOP section seemed weak compared to established "classics" in the field. Failure to mention things like LSP is unforgivable in a book aimin

        • Why, the LSP is known by many different names. The 'substitution property' for example.

          What they called the "substitution property" is a waffly version of Liskov's clear and concise principle.

          Why not try actually *reading* the OO chapter before giving such a sweeping judgement :-).

          I appreciate the smiley there, but OK, I've now read the first half of the OO chapter in its entirety. Not only does it fail to mention the LSP in any useful way, it also fails to stress the interface/implementation sep

          • ...I'll apologise now for the perhaps overly harsh tone of the parent post. As I noted in my original reply, there seems to be a lot of worthwhile material elsewhere in the book. I'm afraid I really don't like your presentation of OO, though.

            Programming is my full-time job, and I use this stuff (and other programming styles you mention) all day. I also teach it to newbies from time to time. At that level, I've found that it's vital to get across concepts like invariant/pre-/post-conditions, and the focus

  • by sohp (22984) <snewton@GAUSSio.com minus math_god> on Wednesday June 18 2003, @07:05PM (#6238417) Homepage
    Based on reading the Preface and a brief scan of the table of contents, this book is interesting for what the authors do not cover, by design. Nothing on static typing, nothing on algorithms, AI, databases, or numerical techniques.

    To some, leaving these topics out of a "bible" would amount to extreme heresy. The content of this book owes more of its lineage to The Structure and Interpretation of Computer Programs than The Art of Computer Programming.
    • all depends what those 1000 pages are full of. If it's 1000 pages of "teach yourself NEW_FAD_TECHNOLOGY in 21 days" then I'd agree. If it's 1000 pages of authoritative, carefully considered and exhaustive thought, then I'd say 1000 pages is to little... I'd like a lifetime supply.

      As for this book... so far I've only skimmed, and for being free on the web as a preprint, I'd say it's fantastic. I'm also reading Programing Language Pragamtics [amazon.com] right now, and it's a little more complete treatment of the same
      • I'm going to partly retract what I sad above now that I've read more. While Programming Language Pragmatics may cover more ground, a lot of it is just trivial mention. This book sticks to the core of illustrating the concepts of modern programing, and fully exploring their possibilities. It's a different kind of book, and doesn't address the implimenters view as other "programing languages" books do. So far I'm really enjoying it.