Programming Books

This book really couldn't have been more useful.

I've been working in HTML and CSS for about a year using Dreamweaver. I didn't have a great grasp of the basics, but didn't want to spend money on a book to cover what I already knew. I took a chance on this one and I'm glad I did.

The author's writing style is upbeat, but not overly playful. Other How-to books tend to take the humor too far (____ for Dummies) but this one strikes the right balance.

More importantly, the information is well explained and usually works on the first try. In other words, one can learn a great deal and build a working product quickly with this book.

I now have a knowledge base that helps me in every facet of web design. If you feel you're missing a few pieces of the puzzle, or are new to web design- you'll love this book.

I knew a bit about css and html back in high school, but needed a refresh, so I got this book. It did help me alot to not only remember css/html, and also help me do it the right way. After reading this book, you should be able to create a pretty decent website (assuming you have a creative mindset and apply these techniques to your own logic).

The book also covered tables and forms pretty well. Other useful stuff include how to put the site online, how to activate the forms, and other web-related advice.

There are a few minor cons to this book. There wasn't any info on frames (i would like to know). Theres a one small typo in the form chapter which confused me a lot. Also, the author could have skipped a couple of pages that deals with people who also beginners with computers.

Overall, I recommend this book for people who dont know anything about css/html and people who know css/html a little bit but wants to learn to do it the correct way. I would also like to note this book is probably not worth the money for people who know decent css/html.

I've been using HTML for 14 years, and have a long experience in software development, but I really found this book interesting and useful. I would highly recommend this to all, experienced and inexperienced - you're never too old to relearn!

This is a very good book. I have been stumbling around for some months now trying to figure out how to do web site development, yet never having had any training to do so. I'm only half way through this book, but it is like the lights have come on. This book really made sense to me. It was easy to understand and the directions were written in terms that anyone could understand and follow. I agree that it would have been nice to have some color, but it was okay not having it if that meant keeping the cost down. Once I finish this book, I'll be moving on to another that will teach me how to work in the Dreamweaver CS3 Suite, a program I have been stumbling around in for some months now with no success. I feel like Ian Lloyd's book has provided a firm foundation on which I could build before moving on to DW and CSS.

If you are a first time wanna be web site designer, with no computer training or experience, yet want to learn a firm foundation on which to build, I would highly recommend this book.

I teach college courses on Web development that emphasize Web standards and usability. This is one of only two entry-level (X)HTML + CSS books that I will recommend to students, and this is THE book I recommend for those who want to get started in the field as an in-depth guide to standards-based Web development, or as an excellent, no-frills reference for your Web development bookshelf.

A good reference to the PERL language.

As opposed to the O'Reilly publications, this book does not assume as much reading between the lines as what is written at times in those.

So, this may be useful for people to clarify what is being talked about in entries there, or just as a more clear starting point to begin with for the areas of PERL programming that it covers.

This book is a great reference if you just want to quickly look up a syntax. The index is very good and makes it easy to find answers to problems quickly, and it almost always beats trolling through google search results! While it would not be useful as the only text for beginners, I think it would make a good supplemental text. It also might be a good choice for people who already have experience in other languages, and are switching to perl, or intermediate perl programmers who cannot remember where every comma and semicolon should go!

I am extremely impressed by this merchant. The shipping was on time and the book was in great condition

This is a great reference book for perl. It doesn't try to teach the reader perl, which after you already know it is really nice. This is more like a collection of all the perlmod/man pages put together in an organized manner. I reference this book all the time for different syntax structures and many other reasons.

As a new programmer and new Perl programmer this is an invaluable reference. For the ambitious newbie this book can serve as a great starter guide to the Perl language. As a reference and supplement to another beginner book, this book really soars.

I was able to quickly expand my understanding of Perl and started writing real perl programs (albeit very simple ones as a beginning perl programmer) by using this book. You'll become well versed in Perl using this as your constant guide.

When a programming reference can be distilled is such a highly useful and pragmatic way, you've got to add it to your library. Brilliant job on this one.

I highly recommend this work and I'm confident you won't leave home without it. Or perhaps you'll buy one for home and work. I also highly recommend 'Perl Power' by John Flynt and 'Beginning Perl, Second Edition' by James Lee (Apress) as companion beginner books to this one.

There seems to be a bit of confusion about what level this book is at. Based on some of the reviews I've read, I was a bit concerned that much of this book would fly right over my head, exploring advanced and obscure features. So let's get one thing straight: this is pitched at the same level as Effective C++, and has a similar structure and style.

And it's not just a 'puzzle' book - although it does highlight some tricky issues to do with templates and name lookup, which might conceivably appear in an unimaginative job interview.

And it's not just about the language feature of exceptions. All aspects of the language are covered, but the section on exceptions is particularly good.

Nor is it 'advanced' in the sense that many practitioners of C++ would consider, e.g. template metaprogramming, or non-portable hacks that take advantage of memory layout of compilers. Instead this is advice at an intermediate level, assuming you know the syntax and purpose of C++, but exploring their most appropriate use.

The structure of the book does involve a series of posed questions, but they differ wildly in how specific or general they are. You can see them more as a rhetorical device to frame the subsequent discussion, rather than questions you must answer (unless you want to retrospectively crown yourself guru of the week, of course).

Each question is followed by a significant discussion of a particular language feature, and summarised advice and recommended principles. Therefore the book is similar in structure to Effective C++. There is some overlap between the books, although even where similar material is included, there is differences in how much detail is given.

To some extent, this book is a victim of its own success. A lot of the advice given here can now be found in other books. But its legendary status means that like Effective C++, this is still essential reading as soon as you've graduated from introductory tomes.

This book and exceptional c++ series are the best book series, I have ever read. Its language and presentation of material is exemplary. I learned a lot from this book and suggest to anyone to leverage his/her knowledge.

Just finished it. It may not be so apparent at first, but definitely you need it to find how to write a "perfect" C++ code.
Of course, before reading this book, several intermediate books demand reading, such as "Effective C++", "More Effective C++", "Effective STL". Some system programming book may also need to be read. Otherwise, you may have no idea why you need this book.

This book presents advices more or less in the same format than books from the Effective C++: 55 Specific Ways to Improve Your Programs and Designs (3rd Edition) (Addison-Wesley Professional Computing Series) serie. What is similar is that topics are divided in 47 small items of few pages each. The difference is that the author first ask questions to the readers or propose exercises and encourage the reader to put down the book and to take the time to think about the problem and then come back to read his answer. This format is more or less original as I have seen something similar in Tom Cargill C++ Programming Style (Addison-Wesley Professional Computing Series) book.

I have read this book pretty fast which is a good sign of my interest in a book but in the same time this book did not leave me a strong impression that will make me remember this reading for a long time. It is hard for me to say exactly why but I think that it is because most items focuses on very small details of C++. Some of these problems are very hard and probably is an indication that the book targeted audience is advanced C++ users which is not a bad thing by itself but I am not convinced that mastering these small details actually has a high impact on someone programming skills. It is probably just a matter of topic choices as I really appreciate much more the sequel than this book.

My review will probably not affect your decision to read or not this book. You will have to read it to find out if you like it but hopefully I have been helpful to let you know what to expect from this book.

This book is a collection of silly, unusable tidbits. The author discusses unimportant issues that most programmers have no need to know in order to create excellent c++ code. If this is how one becomes a C++ Guru, then count me out!

This is the best book I've read on planning strength training programs. If you exercise for strength, you need to have this book.

However, while I thought this was a great book by the standards of the field, the lack of references really irked me. What's fact and what's opinion? It's hard to tell. Rippetoe often implies things are scientifically supported (and from other reading I have a pretty good idea about which of his points are supported), but he doesn't give you the references you would need to be able to tell. He doesn't tell you where his knowledge stops and his speculation begins. This book really is closer to best-practices than anything else out there, but you can't tell that by casually reading it.

Myth-based training and unsupported theories run amok in weight training. Scientific-ish people like Rippetoe could combat that. In that narrow sense, this book is a missed opportunity. There are readers who will get through the book and put it on the shelf next to McRobert, Mentzer and Schwarzenegger and not be able to tell the difference.

Quibbles: The Intermediates chapter, which ought to be the most useful for the target audience, is hard to follow. I was particularly disappointed in the description of the Texas Method. There's also basically nothing on mixing weight training with other sports, which is a common need.

Overall, it's a very good book, but it could have been a great one.

This book gets 5 stars because it focuses precisely on Programming. You can see by the other user reviews that this is an excellent book.

You want to make the most of your training? Tried of making no gains? Get this book, read it, shut the hell up and implement what is in this book!

This book is essential to your training library. It, with Starting Strenth should provide all the information that anyone would ever need in regard to weight training. It does not have a bunch of references, but that does not mean this book is not reputable. This book simply does not need many outside references because Rippetoe and Kilgore ARE those references. Their credentials are impeccable and it would "behoove" anyone who wants to weight train CORRECTLY to take their advice.

As with most of the books that I have read on advanced weightlifting programs, the book is heavy on theory and low on examples. The author gives some general and somewhat confusing parameters on how to design a program and then fails to give a full body workout. The book even states that working the body as one unit is the way to go, but then only gives examples on specific exercises like the push press or squat. Its well written and one can tell the author is extrememly knowledgeable. I just dont understand why he didnt give a full body workout example for beginner, intermediate, and advanced lifters.

Woody's book (and WOW site) offer the very best practical and error-avoiding advice on using MS Outlook 97. Using Outlook is very different from using other Office applications. The file management aspect is thoroughly confusing and inflexible. Woody's book helps deal with this thorny issue.

As a software trainer and consultant, I am always looking for good books. This book is not good -- it's GREAT! The information on pgs.643 to 647 is worth much more than the price of the book! A must have....

Until now I have practically only been reading the Outlook 98 part of the book, as this part was the most urgent from my point of view. I have certainly not been disappointed. But on the other hand I had not expected less as a keen reader of Woody's Office Watch (WOW) and Woody's Window Watch (WWW). I am really looking forward to the rest of the book. It is a pleasure reading and learning from a book where there are a lot of humour included.

I have been using Office 97 for 1 1/2 years and have taken college courses in Word 97 and Excel 97. Having received certificates in both courses I thought that I knew it all. RIGHT! Woody Leonhard has taught me about the easy ways to execute commands. His shortcuts are invaluable to me. I am a quadriplegic and find his advice very helpful and time saving. I am learning Powerpoint 97 in far less time than it would of taken me in school. I believe he has been most helpful in making me a real power user. Thanks to Woody and his gang.

Clear, concise and easy instructions on how to use MS Ofc 97. Points out the good, bad and ugly of Microsoft products. Can turn any novice into more of a professional than he/she ever dreamed of! I recommend this book to anyone who will be working with MS Ofc 97! Don't pass this one up!

It's a great book. As a senior developer with more than 5 year's experieces of Object-Oriented Design, I think this is a valuable pragmatic book about how to do in a practical project.

I bought this for my brother. Got for a good deal on Amazon. Very happy with the fast delivery by Amazon.

This book covers the most common, and usefull design patterns. Each patter is presented in plain egnlish, with full examples.

In addition to patterns this book covers the principles surounding patterns that make them truely usefull.

After reading this text, I feel it deserves the attention of other great texts such as Design patterns and Refactoring, even though much of it's content expounds upon the ideas of these two classics. It's my opinion that this text has two strong points: it explains the ideas and details of agile development very clearly, and it does an excellent job of explaining the most popular patterns originated by GOF, plus a few more. The authors style was very good, with most of the examples in Java. Being a C++ programmer, I would have liked to see more examples in that language, but this is not any fault of the author.

In my role as an architect and a J2EE evangelist, I have to teach a lot about OOAD principles, the Java language and Agile techniques. There are lots of books in my armour that capture the gist of many of these practices and techniques. But none in my opinion better than this book.

Robert Martin is a master at explaining OOAD concepts and applying them to the Agile methodology. For instance, the Agile practices mandate certain practices that need to be implemented in the upfront design and conception of the project. This is in contrast to the methodologies that were hitherto used that emphaisized methodology over design.

This book provides that point of fusion. A great achievement indeed! Concepts such as dependency injection and the Single Responsibility Principle were explained before they became mainstream design tenets.

I am still working on the front page book. I knew nothing when I started. I am now nearly finished covering chapter 4. there are a few places I strugled to understand what the author was talking about but overall the book is serving my purpose. I never expect to be a front page expert but one of these days I do expect to have a running website. I recomend the book although I have not looked at other book on the subject.

Wonderful book. Easy to read. Simple instructions. I followed and built my website just like I had taken a class to learn how. I would recommend this book to anyone that needs a quick way to learn FrontPage 2003.

I've been designing web sites for quite some time now. By no means am I a professional but I can make web sites using basic coding and that's what I had to do until I found FrontPage 2003. FrontPage 2003 greatly reduced the amount of time it took me to create a web site. Although I had been using the program for a while, after I decided to start a business designing web sites I bought several books on FrontPage 2003. I wanted to have the most knowledge about the program as possible and be able to produce the most professional looking web sites for customers. Out of the several books that I purchased all on this one program, I found this book to be the most helpful and overall best book on the topic. It covers everything you need to know from start to finish. It starts out by explaining basic web site design features of the program and then progressively describes more detailed processes as the book continues. All instructions are easy to read and understand. Out of all the books I've purchased, this book has helped me fully understand the program the best. If I had to recommend one book on FrontPage 2003 to a friend, this book would be the one.

Step by step instructions and screen prints. Perfect for beginner. Also purchased FrontPage 2003 the missing manual. An excellent complement.

Instructional manuals lack the one-to-one human connection that make learning more interactive. As complete as this manual strives to be--and it's very good--it can't take the place of individual instruction from a knowledgeable, experienced professional. Case in point are the directions for creating a navigation menu: follow them to a "T" and encounter a surprise when the outcome doesn't match what's listed in the manual.

It takes some savvy to blend one's own personal knowledge and intelligence with that of a great instructional manual. If you're really a beginner, opt for a class first, then use this manual as your constant companion.

I bought this book hoping it would supplement the PeopleSoft SQR class and in general was not disappointed, given my expectations. I knew it wouldn't include anything on PeopleSoft 8; thus the illustrations in the "SQR and PeopleSoft" section are dated. However, the examples in the section on working with effective-dated tables were very useful and apply to all releases. I haven't read the "Advanced Features" section of the book yet, because I was discouraged a bit when I had trouble grasping a few of the concepts in the SQR Basics section. I was pleased that their sample database, on which the reports are based, is modeled on the HRMS JOB, EMPLOYMENT, and PERSDATA tables; however, including sample output with each of their exercise/illustrations would have been helpful.

In summary, if you are a pretty experienced functional person (I am a consultant), are motivated enough to invest the time to learn SQR, and have access to the tool, this may be a good choice. Certainly more information (understandably) than you can get from a five-day SQR class.

You need this book if you are going to write SQR(s). However, you won't use it much with PS 8. You'll use App Engine.

I was working on a problem a couple of years ago and took the suggestion of a co-worker to buy this book. For the last two years I have been using it as a reference. I spent a few months off and came back and embaressed myself puting a report in process scheduler. So I sat down and read the book front to back. I wish I had done this a couple of years ago.

I have been working with SQR for five years. I have used examples and the SQR manuals to accomplish what I wanted. This work provided me with a lot of knowledge that I had never taken the time to pick up. Now even if I take the time off and need a refresher the sections are highlighted.

I have found this book very useful as both a reference and a knoweldge builder. Also, the writing style was good enough that rereading the portions that I was alread aware of was not too irksome. Interestingly, I could swear some of the interview questions I have been asked came right out of this book.

Aside from the fact that there is no other book that teaches SQR, this book is unique and valuable for following reasons:

- It teaches good programming practices. Anyone who has developed in any procedural language (including scripting and query languages) can quickly learn SQR. Therein lies a problem that this book overcomes: the excellent advice given about program development and structure can offset bad habits picked up in other languages.

- It's a definitive resource for SQR developers. Although SQR is relatively easy to learn, it's also rich with features missing from most other languages, such as complete control over printed and screen output, built-in constructs for graphs and charts, and multiple output file formats. Using many of these features not easy for beginners or programmers more used to other languages, but this book shows by example how to exploit every feature SQR has to offer.

- It dispels the common notion that SQR is a PeopleSoft-only tool. In fact, PeopleSoft doesn't own the language, and SQR will work in any database environment. More important, the book shows how to develop application and database independent programs that will work in any environment. This is an awakening for those who are going down proprietary paths, such as standardizing on Oracle's PL/SQL. While PL/SQL itself a powerful language, but is limited to Oracle - migrating from Oracle to, say, DB2 requires that all PL/SQL programs be scrapped. Had the applications and reports been developed in SQR the only changes would be to tables referenced.

In addition to the above, this book also provides good practices for forming SQL queries and understanding how a poorly formed join can make the difference between a resource hog and an unintrusive application. Since SQL, like SQR, is easy to learn many developers take the path of least resistance and develop queries with no thought on their effect on production systems. This book gives sound advice for avoiding that mistake.

The section on PeopleSoft, while out of date with respect to version 8, still contains valuable information for the majority of SQR developers whose exposure to SQR is via PeopleSoft.

There is something for everyone in this book - beginners can learn SQR the right way, and seasoned developers will have a ready reference that covers almost every facet of SQR in practical terms. If your job is primarily SQR development I also recommend that you also get a copy of "SQR Programmer Reference" by Don Mellen (ISBN 0967773008) as a quick reference to the features and nuances of SQR.

Expert systems designer and programmer Vlad Landres and PeopleSoft specialist Galina Landres have completely revised and updated this second edition of SQR In PeopleSoft And Other Applications. Covering the fundamentals of the SQR version 6, and how to integrate SQR programs with PeopleSoft version 8, SQR In PeopleSoft And Other Applications is packed from cover to cover with reusable code examples, warnings of pitfalls, efficient methods, effective-dated tables, complete SQR syntax reference, and so much more. There is no shortage of solid advice and demonstrations in this straightforward and strongly recommended "hands-on" guide.

Very well organized, and good content.
Id like to see more diagrams or so, so we can se how they decide to build the things... but it still is great.

I think this is one of the best books on this subject that I have read so far- very practical, very useful. There is a lot of information, real-life examples and experience from the .NET framework design team.

As a professional I have worked many times on building re-usable and extensible frameworks. Therefore, I had to read several books in order to make sure that the framework I was building was doing what it was supposed to do. However, in all these years I had never the luck to get a complete guide of "building a framework the right way" and I had to always put together pieces from different articles in order to make my own guide. Well, there you have it! Buy this book, read it and you will have a complete guide of how to do things the right way. Another great thing about this book is that different professionals make their comments about almost every guideline. As a result you are not only exposed to writer's view but also to the views and opinions of many well respected software professionals. Do buy this book and as hard as it might seem try to apply its recommendations to your daily development process.

If you need to write C#/.Net or even Java, this book is a must have.

I don't personally think that all developers will find this book useful. In fact, I have a feeling that some may find it highly useless and disruptive as it is abstract in a sense (one must apply the lessons to each library and scenario independently, taking into consideration many different aspects of usability and readability) and it does require some "retraining" of bad practices which have been long since ingrained due to years of usage.

But whether this book deserves a five star rating or a one star rating - whether this book is for you - can be answered by asking yourself the following question: are you obsessed with quality? Quality in the sense of creating a library that is:

- Easily reused by others, even first timers encountering the library or even first timers to .Net
- Well thought out with well designed classes
- Consistent within itself and consistent with the base libraries from Microsoft

The importance of the little things like naming classes, properties, methods, using one type of construct over another, using one type of accessor over another, etc. cannot be stressed enough in the overall picture of creating a library to a higher standard of quality, usability, and extensibility.

As Confucius is to have said:

"If names be not correct, language is not in accordance with the truth of things. If language be not in accordance with the truth of things, affairs cannot be carried on to success.

"When affairs cannot be carried on to success, proprieties and music do not flourish. When proprieties and music do not flourish, punishments will not be properly awarded. When punishments are not properly awarded, the people do not know how to move hand or foot.

"Therefore a superior man considers it necessary that the names he uses may be spoken appropriately, and also that what he speaks may be carried out appropriately. What the superior man requires is just that in his words there may be nothing incorrect."

As I wrote in an e-mail to my team, I think that digesting this book will lead to: higher quality public facing APIs for our customer development teams seeking to extend the functionality, increased readability and more consistency internally in our teams, increased usability and decreased maintenance costs for the support teams as well as new developers on our team, and of course, increased skill, knowledge, and competency as developers of each of the team members.

Many "how-to" business books pretend they are going to show you how to take your business from nothing to hundreds of millions in sales overnight.

"Micro-ISV" is refreshingly different.

First, it is written specifically for those who want to bring personal computer software to the market through their own small, independent company. Second, it is about small companies. There is little here for the person who believes they are going to become a software billionaire. Rather, this is for the person with a good idea who wants to launch a software development and publishing enterprise that will remain small, except in the most exceptional circumstances.

There are, in fact, thousands of small software publishers throughout the world who earn respectable incomes from their efforts. Some are truly small and the earnings of their publishing enterprise supplement the income from their day job. Others make quite significant sums from their products.

Third, Bob Walsh does not peddle dreams or impossible schemes. He lays out a practical program for every step of creating your own "Micro-ISV" from having a vision, as he puts it, through developing and marketing your product. He even covers forms of business organization, which would be helpful for the complete neophyte.

Walsh's orientation is toward Microsoft and the Universe it has created, which is about 90% of all the computers in the world. He offers a lot of extremely useful information about Microsoft and how even the smallest developer can benefit from their many support and assistance programs. Speaking from personal experience, Microsoft's support for developers is truly outstanding and Walsh presents the most detailed exposition of their developer support programs I've ever seen. (Note that some of Microsoft's programs have changed since "Micro-ISV" was published.)

There are many sidebars featuring interviews with successful small developers or short case studies. Some of the interviews are fascinating such as those with David Allen, the author of "Getting Things Done", an approach to time management that has attracted an almost cult-like following (and that is a compliment) and Joel Spoelsky, founder of Fog Creek software, who is something of a legend in his own time.

Overall, this is a remarkable how-to business book for anyone who believes they have an idea for a marketable software product.

Jerry

This book has a lot of good information on starting your own Micro-ISV. It does focus a lot on PC based software instead of Corporate Enterprise Software, but to be fair it's harder to build and sell Enterprise Level software with a few people.

There are lots of good interviews with people that have succeeded in starting their own company and as expected it's not an easy route, but most seemed to be enjoying what they do.

Great book!

As expected, it gives guidelines for becoming a Micro-ISV providing useful information in many topics: Product definition, cyber-infrastructure, market exposure, quality, support management, community relationships, law and payments.

Provides a good number of interviews from diverse entrepeneurs, talking about their producs, business stories and advices for beginners.

After reading it, i feel very motivated to follow the Micro-ISV road.

This excellent book deserves to become the definitive manual of the mechanics of software development for small (`micro') Independent Software Vendors. Not only for the in-depth content (some of which will quickly become obsolete given the speed of technical progress), but perhaps more importantly the description and outline of an approach to the business. Each of the seven chapters have right-now, to-the-point tips and tricks, along with the reasons for them, as well as an outstanding index and rich external references. This covers all the bases, and a few other things as well, and although well written by a seasoned and successful master, it has all the depth necessary to become a well-used reference manual. An excellent companion to this book is `The Business Of Software' by Eric Sink, from a broader perspective animated by anecdotes of his company's path to success.
Eric Sink on the Business of Software (Expert's Voice)

I only read half the book. Then why still rate it four stars?

Having my own ISV for over six years now I have arrived at the point of having 10 people in my staff and having experienced most things any startup will bump upon. Sometimes that makes you think you've seen it all by now, but this is an illusion.

No matter how many staff you have working for you, there will always be a Micro ISV within the company... you! Exept for any partners, no one will do your job of creating the company or product vision and has the same kind of commitment. Some would say that's sad to hear, but I think this is reality. You hire most people to complement you on your own skills, so most of the time don't expect the vision to come from them.

Going through this book I sometimes skipped some of the pages. Some things I knew just to well to read about again, some applied on starting your own business and some parts applied to US / UK law only. Still, I managed to gain a lot of knowledge, ideas and feedback from this book.

Thinking of starting your own ISV business? Then get this book first! Already a business owner with some experience under the belt? The pick your paragraphs and read what you have to. Great book, especially for ISV startups!