Computers Books

This was a great book both for me and my team. I've been in the software industry for many years. I started building a team of developers and needed an easy way to bring novice and experienced programmers together on a similar set of standards. This book provided us with the perfect framework from which to start our team. We've developed several major projects using the principles in this book and have experienced a great deal of success.

One warning, the book gets a bit tedious after the first half. If you're looking to improve your C programming skills, it gets really detailed into pointers and other fun, or not, stuff. Also, the examples are in VB.NET...but you still get the point.

If you're an experienced software developer or a newbee in the world of commercial computer programming this book will give a good kick in the right direction. Steve McConnel will keep you hooked by mixing the right guiding concepts with real-life knowledge and examples.

I'm currently studying computer science and have been reading this in my spare time. Skip your lectures. Just read this book! If you want to construct software in a timely, efficient, and complete manner--this is the definitive book to read. Not dry at all, Steve McConnell covers topics for all experience levels. Even if you're an experienced programmer, you will learn something from this great piece of literature.

I've only gone through the first few chapters thus far. So pending finishing my reading, I'll update this review. Unfortunately this might never happen as I find myself re-reading portions of the book to pick up new ideas and details for software construction!

it's a book that all programmers must to read. it explain a lot of interesting things about how to made good software!

I started by reading the first edition of this book. I got the second edition when I was almost finished with the first edition of this book.

After getting the new version of the book I decided to continue reading the old one because I found that there are quite a few differences between the old and the new edition.

This is perhaps one of the best books that I have ever read on programming in my life. The author Steve McConnell has put together a book that is independent of what ever programming language that is used. In the authors words. He wanted to write a good book on software construction because he had looked around and had not found any good books out there on the subject. I would have to agree with him there are not a lot of books on good programming technic. There are hundreds of books on this programming language or that programming language.

Code complete is so good that I feel every programmer should read it. It would be best if in the first year of college every single student read the book. I just don't know how it could fit into a regular curriculum. Even if it does not fit that well into a regular curriculum what is taught in this book is probably more important then what most people learn at school.

I like the book and would advise it to anyone that programs.

I am looking forward to the new edition because the old book didn't have much advice about object oriented programming. Mostly because it was a new way of programming when the book was first written and he didn't want to commit much information to it when object oriented programming was so new. He does talk a little about things that are outdated but the book is still one of the best.

I will wait a while before I read the second edition but I expect to be as satisfied with it as I was this one.

Great book that should be in every programmers library.

I bought this book as an additional material to study for the CISA exam. However it didn't help me with the exam at all. Furthermore, in an attempt to cover many things, it did not cover anything in detail. This book is just an endless recollection of bullet points. On top of that, it misses very sensitive topics like disaster recovery planning.

Audit is not the most exciting topic in the world, but this no fluff book really sets the standard. The care the authors took is obvious from the start, the table of contents is one of the most detailed I have ever seen, it allows the book to be used as a reference.

My favorite chapter was Quality Management, best job of making quality approachable I have seen to date. My least favorite was Project Management, it seemed to lack the application and lean to theory a bit.

I am not an auditor, but as an auditee, this book really helped me understand how they think. Recommended!

Not having much experience in the IT audit field, this book was a great resource and was easy to understand.

This book has some material relevant to the CISA examination based on the 2003 content areas, although it is not organized or focused as a CISA examination guide. If you are looking for CISA review material for the test, I would strongly suggest to stick with ISACA's combination of review manual and questions CD. I also searched everywhere for study aids for this grueling test and ended up using ISACA's expensive material, but it proved to be the best choice as I passed the Dec 2006 test.

However, as owner of a copy of this book, I assure you that this is an excellent reference of IT management, planning, implementation, risk assessment and control procedures for anyone in the IT business. Most of the material is still relevant as of 2007.

This is a huge book but spends no more then 1 page on any topic. In my opinion the authors only have financial audit experience and little understanding of IT controls. This book shows the failure of the 'integrated auditor' as the authors are tyring to be IT auditors with little IT experience. They touch on some very good points in a few instances and, in general, the book is decent. The authors do not know much outside of the CISA, IIA and financial based certifications as they seem to think that the ISSA (Information Systems Security Assoc.) is sponsored by ISC2/CISSP's (it is not). Overall, I have not been impressed with this book.

This is a great book, with one rather glaring error. Under the SETI entry, there is a picture of Pioneer's plaque. On the plaque, the Pioneer appears to be launched from the second planet from the sun. As we all know, the probe was launched from the third planet, Earth.

The COMPLETE encyclopedia of Star Trek info. A must for those fans who want to ensure an exhaustive Star Trek knowledge base.

If you consider yourself a Trekkie or just someone who is truely intersted in Star Trek this Encyclopedia is a must buy period.It has insight to every facet of the Series.From the Original to Voyager you'll know details to everything.You'll won't be able to just glance through it once.I consider myself a huge Trekkie and like to think I know alot about the Shows,but I'll find myself amazed when I discover details about a certain charecter of Episodes I've forgotten or never knew exsisted.Especially interesting is the Timeline parts of the book,The breakdowns of Ship commisions and Designs,information about Actors,Cuisine,backstories of Charecters.You name it and they have everything about it...well almost everything.

You have to realize this fact before buying this Encyclopedia is that it was made in 1999.It's been 9 Years.Alot of History has happened in Star Trek since then and if you don't realize this now,you'll be disapointed to discover that to information about Deep Space Nine's last Season,the last 2 Seasons of Voyager,The whole of Enterprise and Star Trek Nemesis.All of this information is non-exsistant.And just imagine the frustration of people who actually owned this book through the years and reread it wishing it had all this wealth of new information.I honestly can't comprehend why Pocket Books would not release the Book with all of this missing information availible.Or make a CD-Rom of it.

This might sound like I'm ragging on the Book,but that would be impossible to do.Wiether or not this info is in this paticular Book doesn't really matter,because it extensively covers in scrutinizing detail of all the Series up to Deep Space Nine Last Season,Voyager's last 2 Seasons,the whole of Enterprise and Star Trek Nemesis.And believe me you'll be more than satisfied with that alone.

So,most definately buy this now and enjoy it and you will.But just realize it's outdated and once you do that then you can truely enjoy this Encyclopedia the way the Publisher intended you enjoy it:with wonderment and fun.

I bought this book in 2003, and it covered most of the bases then, but only the movies through 1998 ("Insurrection" IIRC; "Nemesis" is not covered.), and the 5th season of Voyager. It just covered the last season of DS9. And of course it has none of the "Enterprise" series.

There have also been events such as the Paramount auction of all the series and movie paraphernalia since then, and that could be a chapter all by itself.

I came on Amazon today expecting to see a new and updated version for sale, and was disappointed that the old edition is still all that's available.

Michael and Denise Okuda know everything there is to know about ST, and are the perfect people to update this. If I were shopping today for the first time I would say wait for the new edition, but buy a used paperback 1999 just to see what it's all about.

Keeping my fingers crossed that someone sees the demand for an updated version!

Nothing on the end of Voyager's Delta Quadrant wanderings? Nothing on Enterprise's backstory additions and newly-created anachronisms? Both this book and the related Star Trek Chronology need serious revamping. I appreciate the Okuda's insider Trekker style, but this reeks of willful blindness!

This book was delivered to me before time and also paid a decent price for it.

The book is really perfect and is exactly I hoped.
However, the main and only bad critic I want to highlight is the shipping.
The package was very light and the book cover arrived damaged: the corner were maltreated.
No really, only a box including 2 plastic bubbles is not serious and totally insufficient to correctly protect such kind of nice books.

An excellent book. The only comment that I have that has not been covered is that you should know c++ templates to use this book... theres a problem with that, most if not all template books require you to know STL. You will have to read both in conjunction if you do not all ready know templates.
Once you get past that little pit fall though, this book is invaluable to any c++ programmer.

This is far and away one of the best written programming and reference books I have purchased in 20+ yrs of programming.

It gives a perspective on state-of-the-art C++ style, language constructs, and technique that only a choice few people in the industry can offer. The book has all of the meticulous attention to detail and design formalities that one could expect of the finest academic.

Bravo, Mr. Josuttis, and THANK YOU!

Tutorial? Hardly. Reference? I can find better, more complete, and more accessible reference material in 10 seconds with google. Whenever I open this book to find information about some aspect of the STL, I end up googling for the same information a few minutes later.

The examples are near useless. They are all minimal examples of basic functionality and offer no help in using the library for real-life tasks. They do show you which header files to include, which is a plus.

Hash maps are completely left out of the book. While not officially part of the stl, they are still a significant part of it, and one that requires more explaining than the rest.

I am to understand the +5 reviews were because there are no better books on this subject, similarily my +2 review is because there are not enough negative reviews of this book.

Anyone remotely interested in animation should pick up this book. It is amazing. It is truly the perfect reference book for anyone who wants to animate, and do it well.

This is one of the best books on frame-by-frame 2D non-vector animation. The only problem is, Richard Williams overdoes it by a large margin. He is a man possessed with talent, and he demands perfection of himself. That is a hard way to do things, no? In every other respect, this book is excellent. By the way, the culmination of Richard Williams' style of work is the movie The Cobbler and the Thief, available online on [...]. The exact title to search for is this: The Thief and the Cobbler (2007 Recobbled Cut) [v2.0]

This is one of those books that has helped me out alot. If you are a beginning animator in need of learning the principles of animation or if you have had difficulty figuring out how to create walk cycles and facial character animation, then this book is for you.

I give this book 5 stars simply because it was written in a style that's easy to read and understand and uses common terminology. The best part about it is the readability and resourcefulness of the content. Everything a student needs to learn the subject matter in a motivating format!

If you like normal animation and if you like 3d animation or if you like stop motion animation...you'll find all information needed and much more inside this unique book!

A great reference for everyday encounters plus some bizzar data you would never have known about. I have checked many of the Calculations and have found them to be right on. Don't tell the publishers this is worth 4 times the price.

The information contained in this book is extensive. I've never seen so much diverse information contained in one place. And the size makes it very handy
as well. A great resource.

This was a gift and they loved it! It has so much information in one place! Great reference!

The "Pocket Ref." is a must have for anyone that lives and breaths. The information in this book is invaluable. I highly recommend this book to anyone & everyone that has a desire to be prepared for any situation. This book has it all, from first aid, automotive, geology, carpentry& construction and even world zip codas. Anything you will ever want to know. This book would make a great gift for students from grade school to collage or any professional. It is a must buy, well worth the small price tag for what you get. Order one and see for your self. You wont be disappointed!

My husband has this book and uses it frequently. It is all kinds of useful information and conversion charts. My 14 year old thought this would be a good thing to keep in her backpack, it is like carrying an encyclopedia of math and science information packed away in a small book.

Thick Oracle book which is intended for developers who might need to understand the Oracle internals and administration parts besides writing SQL. It's useful for them working in other database also as the general database concept is simlar. Developers can now have more DBA knowledges after reading before on-going performing some DBA task.

Gr8 stuff for all the Oracle ppl.

A true masterpiece, and a great way to learn Oracle concepts. No more to say.

I have been an Oracle DBA for about six years and this book is still the one I turn to when looking for deeper insight into tough Oracle problems. The author recently published a new book on 9i and 10g and that one is also quite excellent. When it comes to analysis and clear writing style, no one can beat Tom Kyte for excellence. Highly recommended.

I bought this book on cheap clearance after the original publisher went out of business -- the best $12 I ever invested. Remembering even 10% of this book makes you better than 90% of Oracle developers, modelers and architects. Mr. Kyte's real world experience and reliance on solid examples instead of folklore makes this light-years ahead of any other Oracle book; it's the only Oracle book I re-read regularly. If you can afford only one Oracle book, this is it. And you may not need any other.

Either if you're a pro or a student, this book is a MUST-HAVE. "Buy it NOW, don't waste more time" is the best advice I could give to you.

This book has very well detailed TCP/IP information, unfortunately some of the information is outdated. The book is easy to follow, and would make an even better learning tool if updated. I bought the book since it was required reading for a class, but I would opt out for a younger publishing on this topic if I had a choice.

This is a good book that covers all the fundamentals of TCP/IP networking. Good illustrations. Seperate chapters for each common application protocols.

Well written and illustrated. Very comprehensive. After reading several books on the subject, I find this one to have easily remembered formulas for everything TCP/IP. A must for the networking professional and the up and coming professional as well.

This book is an excellent reference or source to really learn some of the innards of TCP/IP. Very good diagrams and everthing is explained in an easy to understand way. I would recommend some basic to intermediate knowledge of network before picking this up.

Very handy cookbook reference for my office bookshelf. I've used it a number of times, and it's more than paid for itself in expediting regularly-scheduled inquiries of our AD structure here at GEICO HQ.

Excellent reference if you work with AD on a regular basis either as an admin or a developer. Each "how to" offers methods for manually performing a specific task as well as (where possible) how to automate the task using code. Should be on every Windows admin/developer's desk.

Overall, this is a great book for reference.

There are a number of areas where I think the book falls short - all of the scripts are very hard coded scripts that don't tell you how to do some functions that would make their scripts actually useful (like "pull the list of users with attributes from a tab-delimited file and create them" or something similar, this would make mass creation of users actually useful, instead of "create user1, user2, user3, etc..."). I think that the writers expect you to be a VB expert (or at least close to it) if you're going to actually make the vb scripts useful.

Most of the scripts are "How to use a script to do the same functions that you can already do in AD with ADUC or another MMC", but I think that the most important thing for me about the book is what it inspires me to think of doing. Things that MS doesn't necessarily expect you to do. I'm still not seeing a way to add sidHistory to an object (MS does it with another applet - there is a way...), but there are so many things in the book that just have me thinking about how you can implement changes to an environment that MS says you can't do. What they really mean is "You can't do that with the GUI tools that we provide you".

I am so glad that this book was recommended to me by a guy I took a class on scripting from. I use this book everyday (almost). I even took it on vacation with me for light reading.

Hard to say in words to adequately describe how much I like this book. I highly recommend to anyone who works with AD.

Quick enjoyable read. Some interesting commentary on team dynamics and the social problems teams encounter. I wish more solutions/suggestions were offered.

Nice reminder on what should we do during project.
We all know these things, but often we forget on them.

I expected the book to contain practical advice. The book covered many undesirable situations and business settings. There were no recommendations made on how to improve a bad situation. The book merely reported on the bad environment. If you are in an unpleasant work environment and want to know there may be others worse off then you, you may like this book.

This book is a collection of short essays on how real people's productivity in software industry is affected. It is about human aspects of software development. There is a great variety in the material for such a small volume (about 250 pages). For example, it covers this:

1. The key to software development is people. People are not drones nor they are easily replaceable. They work by themselves and require not constant pushing, but careful motivation. If you don't trust your people you are in trouble. People are a capital investment.

2. Mind-intensive jobs require concentration, hence a private and quiet environment. Breaking the worker's flow leads to frustration and dive of effectiveness.

3. Teams require efforts to form and keep running, but the effect could be miraculous. There is nothing that could stop a running team. (Btw, I tend to call this a locomotive force myself).

4. Methodologies (the big-M ones) don't matter, same for the processes. Technologies and stuff, they never replace people who really understand and love what they are doing.

The book is of most interest to project managers or even upper level managers (may all our managers follow these advises please ?).

What can you do with the book being a software developer ? Not much, just look around and see if you like it where you work now. And take actions.

[quote]
If you've smiled ruefully at any of the characterizations in this book, it's time now to stop smiling anf start taking corrective action. ... It's supposed to be productive, satisfying fun to work.
[/quote]

The second edition differs from the original book in that an all new part VI is added, a few short chapters. Written many years later in a perceivably different tone. It's not just that the authors admit in its preface

[quote]
The first five parts were written by two yongish middle-aged consultants who spent most of their time working at the project level, part VI is written by two gnarled and grizzled old consultants who now spend appreciably more of their time working at organizational levels. ... Part VI is concerned with with the design of entire organizations that include development work.
[/quote]

but it is also that it is written in less confident and undoubted way. I see it as good, after all there is no universal truth, it is all just a food to the reader's thoughts.

And this is a great food too.

Providing an overall rating for this book was extremely difficult, and writing this book review was not an easy task. This difficulty is due to the nature of "Peopleware". This DeMarco work enjoys what appears to be a solid 5-star rating, and to some degree this is a very reasonable collective assessment. Without discussing at length all of the reasons I think this book should instead be assigned less than 5-stars, I think my reasons fall into two categories: (1) the original work was penned in 1987, and due to the industry pervasiveness of many of the ideas presented by the authors, a lot of the material can no longer be considered extraordinary, and (2) the cohesiveness of each chapter and the flow from chapter to chapter is less than optimal - in other words, it is a bit choppy. Now I realize that there exist many in the software industry that can gain great strides in their respective workplaces by reading this book and understanding how best to apply the provided advice, which is why I give this work 4-stars rather than 3-stars, but I must say that I was just disappointed by all the hype about this book, from a year-2007 perspective. And simple math obviously will conclude that 20 years have passed since the original publication. The 8 new chapters added by the authors in 1999 really do not communicate many ground-shaking ideas. In my opinion, Chapter 33 is the only one of these new chapters that personally provided me any insight. And the premise of this lone chapter is simply that "the ultimate management sin is wasting people's time". The simplistic line graphs that accompany this chapter provide some substance to the discussion about project staffing, but again this chapter still seems to be geared toward individuals who do not bother to keep up with the insight shared in industry periodicals. Despite all of these drawbacks, however, there are some strong areas of the book that are worth reading by all software industry professionals. These strong areas are more comparable to the content of timeless classics like "The Mythical Man Month", "Waltzing with Bears" (also by DeMarco and Lister), or "Death March" (see my reviews for all of these books), and are worth reading even if just to provide discussion starters within your organization. These chapters include "Vienna Waits for You" on working smarter and project deadline pressures, "Quality-if Time Permits" where the authors state that "Quality, far beyond that required by the end user, is a means to higher productivity", "Parkinson's Law Revisited" on estimations and productivity, "You Never Get Anything Done Around Here Between 9 and 5", "Brain Time Versus Body Time" on understanding the work day of a technology worker, "The Self-Healing System" on process, and "Teamicide" and "Open Kimono" on team jell. Realize that there are 34 chapters in this book. The bottom line is that this book on productive projects and teams, targeted at a software industry audience - although perhaps not overly impressive from a holistic perspective - is still heartily recommended.