Slashdot Mirror


Amazon's Best Computer Books of 2004

theodp writes "Amazon.com's Editors have announced their selections for the Best Books of 2004 in the Computers and Internet category. Their favorite book of the year? Excel Hacks, which edged out Head First Servlets & JSP (#3), a Grand Theft Auto Strategy Guide (#5) and The Data Warehouse ETL Toolkit (#8). Can Slashdot readers offer some more inspired choices?"

3 of 228 comments (clear)

  1. J2EE Development without EJB by Anonymous Coward · · Score: 3, Interesting

    Expert One-on-One J2EE Development without EJB by Rod Johnson, Juergen Hoeller.

    This is an excellent book with great advice about many aspects of software development. As the title suggests, it describes how EJB is not necessary for most J2EE projects, and offers alternative solutions to many of the problems EJB's solve. It does center around the Spring framework, as the authors are the creators of that framework, but it does give other technologies a fair chance.

    I've personally found the strategies and technologies discussed in this book to be very useful. My new projects are developed in a manner largely based on this book and they've been pretty successful so far.

  2. Favorite computer books of 2004... by teknurd · · Score: 3, Interesting

    IMHO

    • C++ Primer Plus - Stephen Prata (4th edition)
    • Adobe Photoshop CS Classroom in a Book
    • Designing with Web Standards - Jeffery Zeldman
    • Beggining PHP5 and MySql - Jason Gilmore
    --

    The early bird may get the worm, but the second mouse gets the cheese!
  3. "Write Great Code: Understanding the Machine" by strider5 · · Score: 5, Interesting

    "Write Great Code: Understanding the Machine"

    Unbelievably interesting book. the premise being that the current generation of coders is among the first who were not *required* to learn Assembly Language, thus do not truly understand what is going on under the hood. Because of this, they are unable to create "great" code in high-level languages because they simply don't understand the inherent costs of various routines.

    One of the secondary premises focuses on the fact that, while hardware power is advancing at Moore's Law pace, software is requiring more power at nearly the same rate, many times for no reason other than the developer(s) not knowing how to write truly efficient code.

    --
    "All that glitters is not gold"