5 comments about Classic Shell Scripting.

1. Great book. The emphasis is nicely split between actually using the shell itself and the whole supporting cast of unix tools (sed, awk, cut, join, sort etc.) The idea of carefully crafting solutions using the unix toolbox mindset is key. I also like the fact he doesn't try to teach to multiple shells, but first tries to emphasize portability by sticking mainly to a POSIX standard, and only later adds info about non standard shell topics. If I could only have one book on shell scripting, this would be it. The best description is 'Practical'.



2. I would say this is a pretty good book that covers it's subject very well, buti didn't use it much because i had also bought Unix in a Nutshell, Fourth Edition, which covered the basics and differences between the shells briefly, which was all i needed at the time. but i looked through this and read some stuff that helped and it is a good book if you plan on doing extended shell scripting. it was just a little more than i actually needed



3. This book provides a nice overview of the Bourne/sh shell's commands. I wish there were more examples with complete scripts. Korn shell users might want to consider "Korn Shell: Programs for Your Survival at Work" by Larry L. Smith. Bash users might want to consider "Bash Shell: Essential Programs for Your Survival at Work" by Larry L. Smith. Some of the examples in Randal K. Michael's "Mastering UNIX Shell Scripting" are also helpful.



4. The purpose of this handy little book is to help someone who is working with Unix through the labyrinth of tools available and learn how and when to use them. It is important to note what is mentioned in the preface - "Throughout this book, we use the term Unix to mean not only commercial variants of the original Unix system, such as Solaris, Mac OS X, and HP-UX, but also the freely available workalike systems, such as GNU/Linux and the various BSD systems: BSD/OS, NetBSD, FreeBSD, and OpenBSD." I quote the book because the word "Unix" is about as descriptive as the word "car". The intended audience is anyone who is computer literate, already knows how to program, and is regularly faced with diverse problems in the workplace that must be solved with Unix tools. This book should give you a taste of which tool to turn to and when.
   
   This book can be divided basically into two halves. The first half is a tutorial on writing Unix scripts. The book starts with a brief history of the Unix language and the philosophy behind Unix tools. Slowly, each chapter builds up your skill at script writing. You are shown how to differentiate between shells, how to work with text extensively, how to use loops, pipelines, variables, and decision statements, and how to work with files. There are detailed example scripts at every step along the way. By the end of chapter seven, you should know enough about basic shell scripting to be dangerous.
   
   Starting in chapter 8, you are showed more application-related information. First, Chapter 8 shows and discusses some ready-made scripts for some tasks for which there is no out-of-the-box Unix solution. Some of the handy solutions shown are for path searching and automating software builds. Chapter 9 is a crash course on awk, and is aptly named. It is just enough to be dangerous. You learn how to solve common text processing problems with awk, but you'll need more resources to be really knowledgable. Chapter 10 explains the usage of common commands for listing files, modifying their timestamps, creating temporary files, finding files in a directory hierarchy, applying commands to a list of files, determining the amount of filesystem space used, and comparing files. Next there are two applied chapters showing you how to merge several databases and how to perform spellchecking by using scripting. Chapter 13 changes the subject a bit and talks about the concept of processes in Unix and how you can use their statistics to accomplish a number of monitoring and control tasks. Chapter 14 talks about problems you may run into if you try to take advantage of shell-language extensions, while Chapter 15 addresses the issue of writing secure scripts to the extent it is possible to do so. Writing man pages, and the basics of the Unix filesystem are the subjects of the last two chapters of the book.
   
   I would say it is a good modern introduction to the subject of shell scripting and Unix tools and how to use them. It doesn't dive deeply into any particular topic, but it will get you started by broadly introducing you to the problems most Unix script writers and system admins face regularly and how to get started solving those problems. I highly recommend it for that purpose.



5. I've scrolled through lots of books, there is so much information out there, but this book has a tendency to keep it simple and to the point. It has good illustrative examples that not only are useful but also serve as a good practice guide.

5 comments about Mastering Windows Server 2003.

1. Need to do something with Windows 2003 server?? GET THIS BOOK....



2. If you're looking for a Windows 2003 book, this is the one. It's comprehensive and well written in a way that caters to newbies and experts alike. As a plus it's printed on high contrast paper in a very readable font.



3. Fantastic. Still reading it, but this is a worthy reference guide and a long but interesting read. The only book I'll own on the subject. No need for anything else, as far as I can tell.



4. This book is extremely valuable as reference after you have read it through carefully. Everything is in "Plain English", so whether you are a novice or advanced in the field, this will answer your questions. This is "a must" for anyone wanting to learn about Windows Server 2003.



5. it's an okay book and it's really big. don't plan on taking it anywhere regularly.

5 comments about Creating Web Pages For Dummies, 8th Edition.

1. This is a great starter book, but once you get your web site designed, then what? I wanted to know more about hosting services and costs, etc. Then found another title on here called "The Complete Web Hosting Kit Pro." This is a complete kit that lets you host your web site on your own PC for free. Comes with everything you need... instructions and software to host your site on your PC at home or at work. I recommend both this book and the web hosting kit.



2. This is a great book for the person just getting started in thinking about putting up a web site.
   
   The basic concept here is to use a fairly minimal amount of HTML, which he teaches you, and then one of the hosting services such as GeoCities, Google or AOL to get your site up and running. All in all, he presents an excellent description of what you need to think about, what technologies you need to understand, and the various tools that are available to assist in the construction of the site.
   
   The intent of this book is to enable to get a site up and running, fairly quickly (He says in a day, I think he is a bit optimistic, plan on a weekend, maybe even a three day weekend.) but only after having thought a lot about the various aspects.
   
   Then in chapter 18 he talks just aenough about things like JavaScript, database connectivity, cascading style sheets and more to let you know that you've barely scratched the surface.
   
   An excellent place to get started.



3. Thanks for the quick responce in the product, received what I needed for less



4. I was hoping for something that would help me get started on building my own site. This book is for someone who just wants any site, and is looking for someone else to do for them.



5. This was my first "for Dummies" book purchase and it will be the last (unfortunately, I also purchased "Web Sites for Dummies" at the same time. A How-To book this not....you get no step-by-step instructions, what you do get is a lot of information that is generally available on the internet with a dose of new-age you can do anything you want if you try.........well, at least the title is right..........only a DUMMY would buy this book.

5 comments about Pro CSS and HTML Design Patterns.

1. This book is a nuts and bolts CSS/HTML reference book, that you'll be pulling off the shelf frequently, when editing stylesheets and web pages.
   
   Each entry is presented in this clear, practical and timely format, that allows skimming straight down to the section you want (borderless table format, not inline paragraphs):
   
   Problem
   Solution
   Pattern
   Location
   Limitations
   Advantages - (Some entries)
   Disadvantages - (Some entries)
   Example - (Some entries)
   Tips
   Related to - (Some entries)
   See also
   
   It doesn't waste your time with 1001 details of each tag, yet does give you the essentials you need to know about each tag (some entries have screenshots of the examples, mostly in Firefox, but some in IE7), so you can get to work quickly -- and not get bogged down by the hyped cheerleading, that fills many of these CSS/XHTML books these days.
   
   Would've given this book 5 stars if the author spent more time with cross-browser support other than a few tip suggestions, especially with IE 7, as it uses conditionals instead of hacks to get around the box model SNAFUs. Cross-browser troubleshooting is essential, and not an after thought to be addressed with about 20 words -- more time is spent debugging than actually writing code, and it needs to be addressed accordingly.
   
   Overall, this is the best CSS/(X)HTML reference book I've found to date. It's due to the presentation format above, that doesn't have you trying to find some remote reference in microprint, in a sea of 500+ pages!



2. I often rely on readers reviews before making a purchase so I thought it appropriate to give feedback on this book.
   I am a self-taught programmer who needed to take my CSS knowledge to the next level. This book clearly sets the bar high and helps me get over it almost daily. The models depicted are extremely accurate and on point, and foster a wealth of ideas that extend to some really nice models. Mr. Bowers research and implementation on cross-compatability between browsers is nothing short of excellent (a big learn for me). The style in which the book is written makes it easy to follow and learn from, as well as reference. As a new programmer, I am extremely pleased with this book as it has taken me to the next level of CSS.
   I would recommend this book to anyone who, like me, has a general knowledge of CSS and wants to fine tune and hone their skills in CSS.



3. There is some useful information in this book, but the author's rigid adherence to the format works against the presentation of it. I find that Andy Budd's book (CSS Mastery ...) is a much better book. They seem very different but I think that many developers will read them needing the same information.
   
   Further, as is becoming more and more the case with new apress titles, the copy editing is substandard. It's a pity, as apress had such a good reputation for quality books, and this kind of thing is hurting them.



4. Hi
   
   I have read about half the book and I find it very interesting and very practical. The book gives you patterns and approaches to solve the problems which designers confront daily. The index is also very helpful at the back, which points me straight to the solution of the problem which I am seeking. When compared to other books, this gives more than what every other book is giving, which I have seen. Generally all CSS books give various properties of the html elements, its possible values etc. While this book, has a different approach. This book discusses the affect of changing these element properties based on the context where the element is placed. It has very good discussion of the box model concept and positioning concepts.
   
   Till now, I have loved this book and has become my reference for all my css needs.



5. Those who understand CSS will find a trove here. One may trudge through other one true holy grail bulletproof designs. They have their place.
   
   Then, leap, at last, into this book. It's been sitting on your bookshelf, perhaps, undeservedly ignored, for a week? You peruse. You find the page for your problem. You read, carefully. A light bulb! "Of course," you may think! Or, "He's telling me, what I SHOULD have known!"
   
   Yes, but, everybody needs SOMEONE to gather these essential prods. Here they are, distilled, a fine essence. Rock solid. No fluff. Problem, stated clearly; solution, stated plainly; sample code, crisp. Just what you need. Terse. Precise.

5 comments about Agile and Iterative Development: A Manager's Guide (The Agile Software Development Series).

1. The book is very informative and presents both previous (EVO, XP) and current (UP, Scrum) methodologies. I am a project manager and this book helped me understand enough of Agile methodologies to apply it in my work environment. Good detail about each method and how it provides benefit. Before attempting to deploy Scrum or RUP/UP, read this book to understand the larger context and get other ideas for things to incorporate into your framework.



2. What caught my eye on seeing this on the bookshelf were the color of typography, the small notes near the edges of the page that summarized a paragraph, the good graphics and diagrams. It looked like a quality book. After seeing how long was the discussion on "proving" that waterfall methodology was too long, "heavy", slow, and projects that used it more prone to less-than-satisfying end results, I understood why this book is titled for managers. In fact, one of the sentences it mentions that the step-follow-step process of the waterfall was popularized in the 70's and 80's, age during which today's managers got their education. On the CMM of SEI, a brief mention on it was that it resembles the heavyness of waterfall. Wished I had a bit more on it, but did learn from it anyway. The very last paragraph of the book had information I wanted: it was about Fitnesse, but it was just too little.



3. This book tries to provide an overview of several different "non-Waterfall" techniques for managing and organizing projects. The authors are pretty scrupulous about not really advocating one method over another, and as such, I did not find it particularly helpful for my own situation with my software team. Reading about Evo, XP, Scrum, RUP etc. all in one place with key characteristics and comparing their "levels of ceremony" might be interesting to project management/methodology researchers, but there aren't very many professionals out there who are sold on iterative development but are wondering which one they should use.
   
   The book also is fairly technical, with lots of grids and charts trying to explain which levels of critical projects should be considered for a methodology, how levels of effort of different tasks change over time, who the stakeholders are and what to label them, and so forth. I got practically zero out of this.
   
   On the positive side, now that I've read it I am armed to discuss the different methodologies much more, in case a new person arrives advocating a methodology I disagree with or something. I can use this overview knowledge to also pick and choose some terms or approaches which might be helpful in my situation at work. The part of the book which was most interesting was a chapter in which a typical Scrum project was described in narrative form. I think more of that, such as perhaps a narrative illustrating each methodology, would have been more helpful to those trying to decide which methodology to follow in future work.
   
   For the audience of PMs who don't want to know the ins and outs of every IID methodology since the 70's, though, and just want to know how to run their projects better, I don't think this book will fill their need. Or if it does, it will be from the readers picking and choosing little bits across the book--something the authors recommend against.



4. Unlike many of the books out there, this book covers iterative development techniques in general. The book is well organized and structured and gives a good framework for thinking about different ways to manage a project and develop software. Agile, Scrum, Extreme Programming, Unified Process and Evo are all covered and compared which is invaluable in deciding which one to use or, more likely, which elements can be used for your projects.
   Finally, some practice tips and a FAQ are provided to help you succeed in applying these methods to your project as well as answering the questions your team may come up with.
   I found this book easy to read and understand and now feel well equipped to apply these techniques.



5. This work by Larman shares some commonalities with Balancing Agility and Discipline, a work by Boehm and Turner (see my review for that book) in which a wide range of methodologies are compared side-by-side to determine the best fit for teams. However, rather than serving as a guide to determine best fit from a wide assortment of methodologies, Larman's work is limited to a discussion of Scrum, XP, Unified Process (i.e. RUP/UP), and Evo, within the broader context of what the author categories as iterative and incremental development (IID). In my opinion, this book is probably the best organized text on this subject currently available in the marketplace. Although the subtitle for this work categorizes itself as a manager's guide, the content Larman has included here will prove beneficial for anyone involved in software development. And this is the case even if one does not read the four methodology-specific chapters. After a thorough explanation of iterative and evolutionary development, the author discusses its relationship to agile development and the motivation behind adopting such methodologies. The subsequent chapter on the evidence behind the effectiveness of IID is the most concise listing of research findings I have come across. While this chapter begins with a warning that "exhaustive data can make for exhaustive reading" and that it is "probably best spot-read as a reference", at only about 30 pages in length it is well recommended. While many in technology recognize the benefits of IID and have used the ideas brought to the table by various IID methodologies to some extent, the author reminds the reader that not only do many technology shops simply remain paralyzed by waterfall methods that view software as a predictive process, but that IID has been around for decades. David L. Parnas, a software engineering pioneer who developed the concept of module design, is quoted by Larman as follows. "Q: What are the most exciting, promising software engineering ideas or techniques on the horizon? A: I don't think that the most promising ideas are on the horizon. They are already here and have been for years, but are not being used properly." I found the following sections within the specific methodology discussions to be especially beneficial: common mistakes and misunderstandings (or how to fail with a particular methodology), signs that one has not understood a particular methodology, sample projects, process mixtures, and adoption strategies. In addition, the reader might be interested in knowing that the last chapter consists solely of questions and answers summarizing many of the main discussions presented elsewhere in the preceding eleven chapters, serving as a quick reference by pointing to specific portions of the text where ideas are elaborated upon.

5 comments about SQL For Dummies (Sql for Dummies).

1. I have read several books in the Dummies series and found them all excellent, so when it was time to learn SQL for a programming project I got this one immediately.
   
   Unfortunately, SQL for Dummies, turned out to be that absolute worst technical book I have ever laid eyes on.
   
   It jumps from topic to topic without ever really explaining anything. It uses examples that are unecessarily complex -- I get the feeling his examples just come from years of working with databases, rather than a desire to illustrate any particular thing -- and the examples are never explained. Over and over, there will be a snippet of SQL code used as an example, and I will wonder, "what does this or that part of the statement do?" But he never explains anything. He just throws it out there and then moves on.
   
   Dummies books always have a conversational tone, but the tone in this book is overly hokey and just reads like meaningless filler; all the more frustrating because there isn't really any content that it's filling in between.
   
   All I wanted was the basics of database design and interaction, an enumeration of the commands used for creating and interacting with databases and why some actions are useful and for what, and examples throughout of how one would do typical things. Instead I got an intolerable and incoherent ramble.



2. About a year ago, I was writing up a series of lessons for a course in Java DataBase Connectivity (JDBC) that I was preparing for a local business. As is always the case, they needed the course right away, so I had little time to prepare the lessons. To illustrate what can be done using JDBC, I used the executeQuery() method of the Statement object. The executeQuery() method accepts an SQL command as input, so it was necessary for me to quickly brush up on SQL commands. This is the book I reached for to get myself back to speed on SQL commands. Like all ""For Dummies" books, it can be used to quickly learn the basics of the topic, although it has little use beyond the beginning. I found it adequate for my needs at the time, although when I needed to delve deeper into SQL for a later course, I went elsewhere.
   All of the basics are covered at the level one expects from the series, and at the level of the beginner. Of course, some people will struggle with the book, as there is no precise definition of "beginner", or "dummy" for that matter. Nevertheless, if you need to learn the fundamentals of SQL in a hurry, then this book is the one for you. It is simple, direct and just thorough enough to put you on the right track.



3. If you know absolutely nothing about SQL, this book is for you!



4. Hardcore DBAs have knocked this book, but I have coworkers who reference it daily and they are now very experienced and knowledgable of SQL.



5. 0 to sql in just a few days. starts with basic relational database information and continues all the way up through advanced SQL functions. handy tear-out quick-reference card included.

5 comments about UML Distilled: A Brief Guide to the Standard Object Modeling Language (3rd Edition) (The Addison-Wesley Object Technology Series).

1. I do well appreciate how those who believe the earth is flat must feel. I believe the people have lost their senses in their enduring alacrity over the aptly-acronymned OOPS. I have read a number of books on OOPS and worked with OOPS languages, and I continue to believe it is nonsense. The gullibility of my fellow humans has most surprised me.
   
   1/3 of OOPS is logically without foundation: "Everything is an object", the notion that object-oriented procedural systems suffice for reuse, and the notion that object-oriented procedural systems are necessary for reuse, for example. The remaining 2/3 is just old ideas, such as various diagrams, modularity, and control over others, parading in new lingo.
   
   For all their talk of reuse, the champions of OOPS are the ones who sought to discard previously existing software and to rewrite the entire corpus in the style of OOPS. OOPS developers have brought error messages to new levels of incomprehensibility. OOPS is an obstructionist vanity that continues to impede more than it helps systems development and maintenance.



2. This is a good book to have as a reference and to get an introductory understanding into UML. Many engineers at the company that I work at have this book and also at previous companies that I've worked at.



3. With just about 200 pages, this little big book covers the most common features of UML in a clear, crisp and fun way. No other book has given so much to so many in so few pages.



4. This is a handy reference book for UML diagrams. I like the quick summary on the inside covers, useful when you want to a quick reminder of which UML diagram is the one you want to use. I find it helpful that instead of spending pages and pages describing some of the hardly used notations, it actually concentrates on describing the essentials and the typical. If I then find I need more information on a certain diagram, I just go find it in the internet. It is not an in-depth explanation of object modeling.



5. This book is not the ideal UML book for the business analyst (and I now work as one). There is reference to OO programming concepts that will probably always be lost on me. However, it is the ideal overview of the UML for starters, and I suspect I will be using it as a reference for quite some time to come. Enough detail to do some serious work with, concise enough to allow me to find what I need. After reading this book I was curious for more and ordered four more books from the Object Technology series. Hope they are equally good.

3 comments about Learning Autodesk Maya 2008, (Official Autodesk Training Guide, includes DVD): The Modeling & Animation Handbook.

1. it is a great reference book!! I'm a student at animation major.. this is helping me all the time.. Also you can use this book for learning the software by yourself.. it is explaning and then give you assignments so you can understand the lesson well..
   
   good luck!!



2. This is the ideal guide for those who want to perfectionate his or her modelling skills. Extremelly usefull step by step tutorials. Highly recommened. Another score for Autodesk!



3. This is a really cool learning guide. It is geared a little more towards people who have a basic understanding of the Maya universe. If you have never used maya at all, it may be a little confusing. I suggest playing with the interface and going through the "Getting Started" lessons included with the Maya software before getting into this book.. The dvd contains support files for the lessons in the book. It would have been nice if it had some video reference. The pictures in the book aren't the best guides, so unless you understand the text, you may find yourself using more creative freedom to complete the models than actual tutoring. Still, it is a great reference and gives you all you need to create some complete models to practice building and animating. Hope this helps.

5 comments about Hackers and Painters: Big Ideas from the Computer Age.

1. I was entertained and greatly appreciated the view of the author but the many times I completely disagreed (due to very substantiated reasons) made me skeptical of several ideas of the author. But, the reasons for him holding those views is, in and of itself, interesting. He does have several good and controversial ideas and his experiences are quite valuable to read. Most of the time, I found myself flying high with him as he stated things that really need to be said which ran against conventional thought. Other times, I found myself raising my eyebrows in bewilderment. After all, it really is a book about his thoughts so take it as such. His book, his soapbox.
   
   The book reads well but really trails off towards the end. I found myself finishing the book just so I could say I was through with it. The opening chapters are quite entertaining. Read a few chapters that you find interesting and leave it at that.



2. In spite of the strong desire to punch the author in the face after finishing the book, there are many great truths inside. Basically why is it that most people think salaries on the same position should be the same if work results differ in orders of magnitude.
   
   Also it's funny to see an ultra-capitalist criticize the western decadent corporate structure. It's The Market for Lemons all over the place.
   
   Don't expect to find anything useful to make a dot com startup on this book. It's all anecdotes from his experience and his quasi-religious views. It's more rhetoric on Lisp than business.
   
   As another reviewer said, read first his online essays before diving into this.



3. Paul Graham is very clever (and rich - is that relevant?), however light also bends around his ego. Whether the sum of these qualities is positive is not absolutely clear to me.
   
   If you want to read the best thing that he has written, you might be better served by his book on advanced Lisp programming, which is a monument anybody can be proud of - it comes close behind SICP on my personal list.
   
   And, if you do read this book, I suggest you also look at 'The Science of Art' by Martin Kemp, which gives another perspective on the maybe slightly overweighted metaphor of the title, and the relation between theory and practice it implies.



4. The book particularly deals with the nexus between programming, creativity, social commentary, wealth-generation, business-personal-entrepreneurial psychology (his specialty!) and LISP-related stuff. I skipped the programming sections because Im not a programmer. The philosophical commentary was better than 90% of other philosophy books I've read, more cutting and more true-to-life.



5. Hackers and Painters is a good read. I enjoyed learning about the author's perspective on programming trends. I really enjoyed learning about his enthusiasm for Lisp. This book is not a how-to, but a collection of essays describing the authors views, opinions, and experiences with various programming topics. I definitely recommend it.

5 comments about Using Moodle: Teaching with the Popular Open Source Course Management System (Using).

1. An excellent introduction to Moodle -- a course management system I'm teaching myself. Yes, much of the information is available online at the Moodle site, but I'm a person who would rather look through a book as opposed to clicking links online and printing what I require.



2. I started out muddled over Moodle. I knew I wanted to do some of what this LMS could do, but fairly ignorant and hesitant to jump into the Moodle community to ask the most basic of questions. This book seems to do the job.



3. Thank you to the authors of Using Moodle! This comprehensive introduction to Moodle is exactly what we needed in my school district. I recommend it to anyone charged with Moodle-related staff development.
   
   Well-done, Fellow Moodlers.



4. This is an excellent book for a teacher who would like to know a little bit more about Moodle. The teacher does not need to know much about course management software. This book gives a great overview, with examples, while not getting caught up in the technical details.
   
   For example the Lesson module section starts off with non-Moodle classroom story told by Jason. Then the chapter gives a short overview and talks about the different features of Lesson. There are a couple of inserts on tips and examples of how a feature could be used. Plus a few screen shots.
   
   If you are looking for examples of GIFT or XML formats, then this is not the book for you. On the other hand, after reading the Lesson and Quiz chapters, the potential teacher will know that these are a few of the question formats that can be imported into Moodle.
   
   Moodle documentation and on-line forums are great resources but are not designed for the non-user or really new user. This book will help a teacher ask or find more information about what they want to do in their course. It is "Moodle 101 : An Introduction to teaching with Moodle."



5. Very pleased with the book, its content, and usefulness. Also, pleased with delivery and timing.