Programming Books

In learning how to use FrontPage 2003 step by step, this is the book. It's very colorful & informative, it provides all you need to get started in the development of your own website, you're going to like it very much.

I bought this for my daughter and she said it was very easy to follow. She has already started designing web sites for her friends.

I have just begun to use this book. I am an extreme beginner and find the book attractively laid out and well-illustrated. I have not finished my web site yet, but I'm on my way. There are a few details that are "over my head" but I think I can work around them and still get good results.

FrontPage was a new application to me and somewhat different than other web page applications. I was asked to take over website updates and didn't have time to go through a class, etc. This book enables the user to look up the task at hand and then basically follow the step-by-step instructions. It has been a fabulous tool. It is very user friendly for the novice but still has enough technical information to satisfy the HTML hound. I found it to be a more effective tool than Microsoft's on-line classes.

If you can only have one book on FrontPage, this should be it.

I am just learning about web page development and bought Microsoft FrontPage. I needed help understanding the program and bought this book. I find it very helpful. The layout of the book is most useful. I needed assistance with taking the first steps, and this book is serving my needs. It would probably be too basic for someone with web development experience.

As a dotNet Developer, I am often called upon to write my own database code or maintain existing db code. I am also called upon to diagnose performance problems or set security. Sometimes on lightly staffed projects, I am a defacto DBA.

I have always strived to have a comprehensive understanding of the technologies I use. However, my level of understanding of SQL Server was more limited then my understanding of the other technologies I use.

I purchased this book based on existing Amazon recommendations. In particular, I was interested in the Performance and Security sections, as well as what is new. It did not disappoint. The depth on items like Indexes was exactly what I was looking for. The discussion of new items was enough to get we to a working level.

So it definitely fulfilled my needs and expectations.

However, the book seems aimed at DBAs. Given the number of topics covered in the book, I suspect it could not be comprehensive enough to take an intermediate DBA to the Advanced stage.

But for someone like me, who is often called upon to be an 'acting' DBA it serves as an excellent reference; in addition to providing a tutorial on the topics mentioned above.

Even for a beginner like me. This is a great book as a reference or if you learn by experimenting and need a book to look up things here and there. I'm not an expert with SQL Server but it really seems like this book is a must have if you're dealing with SQL Server setup, management, etc..

I used this almost every day now for the past couple months. I used it as a reference with developing in SQL SEVER 2005. It answers about 80% of my questions. Must books answer a little more then half - so I give this five stars.
If you write a lot of code in SQL, I highly recommended this book.

Very valuable when it comes to referencing all the functionality SQL Server 2005 has to offer.
Microsoft(R) SQL Server 2005 Unleashed

There are a lot of typos and grammar errors in the book. Like "or" instead of "for", for example.

This is definitively a must have in the bookshelf of all .NET AD Developers. I have been working with ADAM since .NET 1.1 and have always struggle to find answers to simple questions like how to make an LDAP query to run efficiently or how to define complex queries; this book has that and a lot more.

This book is everything I was hoping it would be. I'm working on a project where I need to get computer accounts from AD (TENS of THOUSANDS of them) and move, delete, enable, disable and set account expiration dates. Everything I need to know is in this book. The AD paged search, useraccount properties, etc. Some of the routines I was able to use as-is (the VB versions from their web site download). These guys do a great job of explaining all the stuff I couldn't find anywhere else. Highly reccomended!

This book is great for anyone who does AD programming with .NET it covers everything from the basics to some pretty advanced stuff and even some undocumented stuff.. a must have for AD Programemrs!

If you are or may be in the future, doing directory services programming then this book is a must have. It also suffices a quick reference as it has code sprinkled around so that you can get up to speed quickly.

If anything, it is sort of lacking on other LDAP directories. It does have the history of LDAP and does show where the differences are between AD and the others.

If your primary focus is other directories, this may not be the end all book for you, but should still suffice as a reference.

If AD is your main focus, buy this now, you won't be disappointed.

This is a very good book for[...] developers who wants to program against Active Directory. There are some good examples in this book that can be very handy. Other than examples in pieces, there is not a project or Web Site codes that a beginner could use.

After 2 days of intense reading of Corba for Dummies, I am still a dummy when it comes to Corba. However, after reading first few chapters, I know I won't be a dummy for long. Will SAMS publish more updated edition (for Visibroker 4.x and Java 1.2)?

This book helped me get off the ground when I was trying to convert some Java/TCP code to Java/Visibroker. Very similar to Programming w/ Visibroker.

I have not yet read this book but, the reviews about these books tells me that this is an excellent book.

This book is the difference between going home at 6 p.m. and 6 a.m.

I've been working with Visibroker for Java for about 3 years now. The documentation that comes with the product itself is so bad that the only way I learned anything about the product was from experimenting with it.

About six months ago, I bought this book. I learned more from reading this book than I did from years of working with the product itself. (Usually it's the opposite.)

If you working on a project using Visibroker for Java, or any ORB for that matter, you must get this book. It will save you hours of frustration and you'll have time to spare to play Unreal Tournamnent.

This is a very good book if you are using and JDK 1.1.x and Visibroker for java 3.x.

If you are using Visibroker 4.0 and jdk 1.2 , you may need to read the Visibroker 4.0 documentation on compatability issues before using this book.

There are also some minor typing errors.

Overall This is a great book.

I already read many Oracle books from Oracle Press & other publications. They are very good. This book takes different approch of How-to Style content which is very much practical & solves day to day administrative needs. Topics are covered in detail. Most importantly examples given are from grounds up. Excellent! This book is also helpfull for all who know a little bit of Oracle Database & want to know more in depth

We all know, especially here in Brazil, the money that one pays to have a good Oracle trainning. If you already have a little knowledge of Oracle and its jargon and are self estimulated, this book will take you to high level of expertise without a pain . Want to know Oracle ? Start with it.

Among all the Oracle reference books, I found this one to be the most useful and practical book. This book is very well written and has an easy to read format. The detailed step-by-step instructions in Q&A section helped me solve problems quickly. This saved me much time and effort than going through piles of other reference books and trying to pull pieces of information here and there together to get a complete picture. I highly recommend this book to Oracle DBA's in all levels.

As an Oracle Instructor and DBA I've had the opportunity to review numerous Oracle texts for DBA's and have to say I've been quite disappointed with most of them. Mr. Yuhanna's book however is an exception. Out of the many DBA texts I have on my shelf this is the one I goto most frequently. Unlike other texts which spend excessive amounts of time covering uncommonly used features and little to no time covering commonly used features this books covers almost all the basics in a hands on approach. The book is setup in a step by step how-to format. Although it doesn't discuss concepts much that is not its purpose and the best concepts book is the Oracle Documentation anyway. I've have yet to see a good how-to DBA book until I came across this one. As a consultant/instructor I recommend it quite frequently.

The book is very useful for both new and experienced DBAs because it has a lot of practical examples. I especially like its Q&A format with scripts which makes reading very interesting.

I've read quite a few of Jim's works over the years, and he has never failed to impress me. This book should be required reading for any project manager!

My initial pre-read perception of this book was that it was going to be just another perspective of agile methods. I was wrong. Coplien and Harrison have dissected development teams to identify the key criteria leading to successful efforts and high-performing teams. Beyond process, this book identifies the organizational structures required to make the processes work.

From an organizational perspective, roles and responsibilities within your development teams are a primary success criteria for your agile (or any other process) adoption. This book presents how and why key roles within your teams work and why teams without these key roles don't work. The way they have presented the material provides for a quick cross-reference when you are looking for solutions to help your teams.

Beyond the organization patterns themselves, I believe some of the richest material in this book is presented in the last few chapters as they present the history and importance of organizational structures, roles and responsibilities in applying process - "Process emerges from structure, and structure emerges from values". There is great value in this book beyond most software development process books.

As project managers, most of us who've been in the field working for a while come to realize that successful project teams are more the result of "good" ongoing social engineering of one sort or another rather than just dumping an almost randomly selected group of people together, coming up with an MS Project Plan and saying "do this" (the Death Star approach, all to common in large traditional process-driven IT shops). After this has happened to you, painfully, you begin to come to the realization that perhaps there's more to project management than the mechanistic "people are interchangeable resources" PMBOK-style approach.

If it hasn't already, it begins to dawn on you that the "soft" side of project management (client relationship building, communication within the team and between teams, team dynamics and team morale, motivation, empowerment, commitment, a human-style of project management) are as important or even more important than the technical work and the technical skills required. Most of us have run across teams with prima-donna's who think they're the cat's whiskers, be they project managers or technical personnel, who have the personal graces of a warthog and who are incredibly destructive to team morale and team performance. They continue to exist, sadly, and because they often deliver, albeit at the expense of everyone who works for them or with them, they continue to survive in "Death Star" style IT shops where delivery is all important and the style of successful delivery means nothing or is short-sightedly disregarded. OK, so that's my rant.

Now for the book. We've all seen successful projects and successful teams (or at least, I hope we all have). Some teams gell and perform way above the norm. What this book does is distil over 100 successfully applied organizational patterns of one sort or another from real projects in real software development groups. These patterns are broken down into logical groups (Project Management Patterns, Piecemeal Growth Patterns, Organizational Style Patterns & People and Code Patterns) which are dissected and explained, with examples provided. What the authors have done is to identify and describe key organizational patterns which are used by successful teams - not processes, but organizational structures of various types that are needed to make processes work successfully. A large amount of practical experience has gone into the content - over ten years of research experience from the authors alone.

I've read a lot of books on Agile, but this is the first I've come across that sets out organizational patterns - and does it so effectively that you'll wonder why all the stuff in here never occurred to you before. As you read through the book, you'll see patterns that will make sense, the kind of "ah-ha, that's what the problem is and this is how I can dom something about it" sense. You'll find this book useful in that the contents can be taken and applied right away. It's easy to pick what is most useful for your team, what can be applied immediately and what would be nice later on, once some of the basics are in place. The content is practical in that you can easily identify what your problems are and what pattern would help fix it, why the pattern is intended to fix it, and there's good advice on how to introduce new patterns.

With over 100 patterns, there are a lot, but they're set out concisely, a page or two to each pattern. There's no fluff, it's well-written, there's no appreciable bias, there's a lot of material, including some good coverage of the importance of effective organizational structures in applying process. As we all know, all the process in the world will not a great project team make. The book's structure is coherent and well-organized, the patterns described can be used individually or as groups and the authors give you some pretty good ideas as to what's immediately useful.

And the pictures all the way through the book are great! A nice humorous touch that helps make the point each time. Overall, I'd recommend this book very highly as a resource to anyone managing a project / team, whether Agile or not. There's a wealth of practical advice in here that any project manager could take and use, although the orientation is towards Agile Projects. An added bonus - unlike many technical books, this one won't date quickly - organizational patterns that work don't change much over the years, unlike programming languages. From a practical point of view, I've applied some of these patterns to teams I work with and the results have been positive - I've also shared the book with co-workers and they've all found it both illuminating and useful.

This book has to be The Grand Unifying Theory of Software with respect to managing the people and processes involved in software production.

To anyone who has worked in the software industry, this book is clearly the product of an enormous amount of practical experience in both management of people and projects as well as the development of software.

Coplien and Harrison have written a book which both the project manager and software engineer will understand and will immediately be able to apply to their respective work environments: This is because the book cunningly captures essential organisational concepts using a framework that is familiar to software engineers. Thus, the concepts will be by recognised by staff trained in business as well as those trained in software and systems.

I strongly feel that the material covered in this book can achieve a common communication basis between managers and engineers, and can help business developers understand the nature of their people and organisation.

If I could insist that all people in software read this book I would; but without the policing power, I can only highly recommend this book to those involved in all facets of software.

OK, I have to admit, this is the first book review I've ever written on Amazon and having read a lot of good books I should probably get off my a** and write more :-)

As a former developer and now a software development manager, I have come to realise that the "soft side" or sociology of software projects (communication with clients, communication with teammates, project management, team dynamics, cultural issues, morale, division of work, remote collaboration, etc) is considerably more complicated than the programming work itself.

Over time, you start to see patterns emerge such as "start a large project with a small experienced group and gradually phase people into a project as time goes on". This book does by far the best job of cataloguing and explaining dozens of these patterns related to (1) software project management (2) structuring, building and nurturing software project teams and (3) organization and division of development tasks to maximize the effectiveness of the team as a whole.

Highly recommended to anyone involved with software development at both the management level and in the trenches. Have fun!

Issues specific to Open Source are well-covered in this book. I found the section titled "Handling Difficult People" especially useful; his advice in this dodgy area is to act eloquent and keep feedback directed at the problem, not the person. If the person *is* the problem, nip in-public issues in the bud and contact the person directly to resolve the personal issue(s).

Fogel presents lots of down and dirty day-to-day details on how to create excellent software. Not just Open Source, either... the transparency built into the processes he describes are also useful within a company firewall.

Fogel places a huge emphasis on development by random unsalaried people, but I feel that most important and rapid development is due to corporate sponsorship.

Overall: excellent. Read it cover to cover, refer back to it often.

If you are thinking of starting/managing a project in an "open-source" model, this is the book you MUST read.

The book is very well written and goes over lessons learned of others that created their own open-source projects. Believe me... every step so you don't have to guess anything!

How to start, how to document, where to deploy the project, what people to invite, whether or not coding standards are necessary, democracy versus dictatorship, all of these questions are answered inside.

A friend of mine has told me that much of the information in this book can be seen for free in video in Google. It's worth looking for.

I read the book in 5 hours and i think my time was very well invested. I now believe that this model is not only suitable for small projects but to larger projects. The complexity of the system will not the an issue if you apply the rules in the book. I still have to try it though... ;-)

Just yesterday I was talking to a friend about this book and we discovered each other very glad with it. First of all, the author has a lot of experience with the theme in question. Furthermore, Karl Fogel is very compelling with words. He knows how to write down his experience in a way that is pleasant, certainly due to a lot of writes he had made through plenties of open source projects.

With this book you will be in touch with topics like the needed infra-structure to setup open source projects, the dinamics of the open source community, strategies for packaging and releasing software, common issues that arise in open source daily development and how to workaround then, a brief about licenses (with properly links for more information on this topic); just to highlight some aspects.

This book was the first hand someone land me into the open source world. It's helping me in three ways: to extract more from open source softwares that already exist, to start my own open source project, and to look at software development through a new, different, and till now better perspective.

Hope this review helps you!

If you have already read pretty much everything that there is to be read about why you'd want to start, manage, fund or participate in an Open Source project, but want to know everything about how best to do it, then Karl Fogel's Producing Open Source Software is the book for you.

Drawing from his extensive experience with the Subversion project, Fogel provides in this book a comprehensive overview of all aspects of Open Source software development, covering technical, social, political, economical, legal, and managerial aspects.

While the book is more aimed at medium-to-large scale projects, especially those involving some kind of corporate entity, there is much in it that is applicable to most projects, excluding maybe only those little, one-man efforts that rarely become successful. But if you are the originator of one of the latter and, should it suddenly attract a wide following, you'd better be prepared to face the unavoidable problems that popularity brings.This book will come in handy in this case.

Here are, in my opinion, the strong points of the book:

* Providing a concise, yet comprehensive, overview of all aspects of Open Source development. This is really the manual of open development.

* Demonstrating that there is much in open development that is similar to more traditional, corporate-style software development (you cannot always rely on good will and volunteers), but also much that is different, in motivation, rewards and objectives.

* Putting the accent on the human aspect of development: mutual respect between participants is often the deciding factor in determining whether a project will thrive or fail. Since even the best of intentions sometimes are not enough to foster a peaceful, productive and collaborative environment, Producing Open Source Software contains a lot of useful, practical advice that you can follow if you want to keep developers happy and motivated.

It's easy to make the mistake of viewing this book as "too fluffy" or perhaps too soft to be of any use to the practical user or developer of open source software. Nothing could be further from the truth: in a classic open source way, the author has compressed man-centuries of OS community experience into a practical working guide for anyone who wants to do something serious in this area.

If you want to understand programming the Flash Communication Server and it's capabilities this is a good place to start.

Although I'm using Flash Media Server 2, this book is still highly relevant as not much has changed. The core objects and language is the same so I would not hesitate to recommend it for anyone looking to use FMS.

This book is all about the design of applications using Macromedia's Flash Communication Server MX. FCS MX enables the building of media-rich web applications by taking care of the basic tasks required in the networking of the applications. Thus, you can focus on the application itself rather than worrying about low-level communication details.

Since this book is concerned with situations where multiple Flash applications will be executing on the same server simultaneously, there is going to be considerable effort involved in coordinating events, which is addressed by this book. You should already have FCS installed and running on your server and you should also have Flash MX available on the client. The following is description of the book by chapter:

Chapter 1, Introducing the Flash Communication Server - Acts as an introduction to FCS and an overview of the whole book.

Chapter 2, Communication Components - How the FlashCom communication components encapsulate commonly needed features such as chat, video recording and playback, bandwidth control,and user configuration. These components implement many basic building blocks for your application.

Chapter 3, Managing Connections - This chapter covers connections in more depth past the SimpleConnect component, including how to write custom code to handle various changes in the connection status as well as different errors.

Chapter 4, Applications, Instances, and Server-Side ActionScript - This chapter describes how to write Server-Side ActionScript and work with the objects that control application instances and the Flash movies that connect to them.

Chapter 5, Managing Streams - Offers a somewhat oversimplified but complete example that shows the basic steps in publishing one live stream and subscribing to a second.

Chapter 6, Camera and Microphone - This chapter explains how to use both the Microphone and Camera classes to record live streams. These classes are at the heart of most communication applications involving multimedia.

Chapter 7, Media Preparation and Delivery - This chapter covers many details for compressing and streaming audio and video.

Chapter 8, Shared Objects - This chapter starts an entirely new subject - shared objects, which provide a mechanism for the transmission of data between client and server.

Chapter 9, Remote Methods - This chapter also shows how to broadcast method calls to every movie and application instance connected to a shared object or stream, or send them to and from individual movies using RMI.

Chapter 10, Server Management API - Discusses the Server Management API and its applications, including monitoring a FlashCom Server, gathering statistics on application instances, and managing the log streams.

Chapter 11, Flash Remoting - Demonstrates how Flash Remoting can be used to add data connectivity to FlashCom applications. Flash Remoting can access web services, server-side scripts, CGI applications, XML files, or the local filesystem with the help of an application server such as ColdFusion.

Chapter 12, ColdFusion MX and FlashCom - Teaches some specifics involved in using Flash Remoting with ColdFusion MX and FlashCom. There are some practical working examples shown that demonstrate how you can leverage the benefits of Flash Remoting in conjunction with FlashCom.

Chapter 13, Building Communication Components - This is the first step in building complete applications, and is demonstrated through an extensive example.

Chapter 14, Understanding the Macromedia Component Framework - How to modify an existing component and how to create a new one. Also discusses server-side framework code and its core features and data structures.

Chapter 15, Application Design Patterns and Best Practices - Describes some of the best practices available to application developers. This chapter provides some useful design options, patterns, and best practices that will help you build better applications.

Chapter 16, Building Scalable Applications - Deals with building multi-instance and multiserver applications that don't bog down as the number of client connections increases.

Chapter 17, Network Performance, Latency, Concurrency - Traditional network design issues affect FCS also.

Chapter 18, Securing Applications - Specifically this chapter examines the three A's of security - Authentication, Authorization, and Accounting.

Excellent book, stuffed of examples very well explained, easy to read and to understand, essential for who desires initiate or even though to profound itself studies on FlashCom.
Obligator reference in projects involving FlashCom, either for fast consultations and advanced tasks.
Excellent approach of subjects as Design patterns and security, yonder a perfect demonstration about audio, video and much more.

If you're a developer looking into real-time server communication using Adobe Flash, this book is a must-have. It guides you thru various levels of application development in an easy to understand format, and provides well documented pieces of code to assist you in the learning process of putting together your project:

Topics covered include:

- learning about components and how to use them
- establishing and managing client connections
- publishing live and recorded streams
- local communication with clients
- remote communication with outside applications

The book also shows how to build and integrate your own custom components, and how to scale your application using the components that you've created. Other highlights include information on how to use shared objects and server management API, as well as ways to improve both design and performance.

This is well written, well organized, and covers the whole core language. It isn't a cookbook, and it isn't an API reference, but for what it is, it's excellent.

The organization makes sense, the index is usable, and the writing is precise enough to leave no ambiguity.

My only complaint would be too much space spent on differences between 1.8.6 and 1.9, and too much attention to text encodings.

For a long time now Dave Thomas' Programming Ruby: The Pragmatic Programmers' Guide, Second Edition (aka. The Pickaxe) has been the standard in the Ruby community as the book to learn Ruby from. Unfortunately the Pickaxe is not the best programming book ever written. In fact, its bulk and slowness almost killed my inspiration to learn Ruby. I respect Dave Thomas a lot for what he does for the Ruby community but the Pickaxe and I just did not click.

Since I didn't find the Pickaxe to be excellent reading material, I had been eagerly anticipating David Flanagan's The Ruby Programming Language to come out and unseat The Pickaxe as the de facto book to recommend to newcomers to Ruby.

I am happy to say that The Ruby Programming Language did not disappoint. I picked up this book solely expecting to just review it since I already comfortable programming in Ruby. However, once I started reading the book I found myself frequently learning things about Ruby that I didn't know before. Not like little things either like, "oh that's interesting". I'm talking significant things like "holy crap that's sweet!".

This book covers both Ruby 1.8 and Ruby 1.9. Initially this concerned me because as impressive as it is, it must have been quite a headache for the authors and was not sure how they were going to pull it off. It turns out to be pretty much a non-issue. The authors make a note of what is 1.8 or 1.9 only and it does not disturb the flow of the book since it doesn't come up too frequently. I do hope though that after Ruby 1.9 stable is released they upgrade the book and tear out all the 1.8 specific material. Since I currently use 1.8 on a daily basis I don't mind having 1.8 material in there but after everything has shifted to 1.9 it would be rather irksome.

The style of the book is fairly straightforward. It starts with an introduction to how Ruby programs work and then goes into an explanation of Ruby datatypes and objects. The later chapters cover advanced topics like reflection and metaprogramming. The authors opted not to go the tutorial route, which I think, was a good approach since the book is not designed to be an "intro to programming" text.

In the preface of the book, the authors state:
> [The Ruby Programming Language] is loosely modeled after the classic C Programming Language (2nd Edition) (Prentice Hall Software) by Kernighan and Ritchie and aims to document the Ruby language comprehensively but without the formality of a language specification. It is written for experienced programmers who are new to Ruby, and for current Ruby programmers who want to take their understanding and mastery of the language to the next level.

O'Reilly is hoping that The Ruby Programming Language becomes the equivalent of K&R's The C Programming Language for Ruby and I hope it succeeds. I think that every language needs their own K&R book for people to turn to as the definitive authority. That's something that I feel like the Java programming language never had and it creates something of a hurdle when browsing for a Java book.

The third edition of the Pickaxe is in beta and will be coming out soon. I really hope it makes a strong showing when it hits the press because after the bangup job Flanagan and Matz did with The Ruby Programming Language, there is no reason to look at the Pickaxe till then.

This is an excellent reference book on Ruby, if you already know Ruby this book will help you a lot, but if you are looking for a tutorial on Ruby this book should not be your first choice.

This book (TRPL) represents a great alternative for those who are not entirely satisfied with the "Pickaxe", as it goes into much more detail in some areas of Ruby. After reading both books, my general impression is that the Pickaxe can be seen as a lighter reference and TRPL as a more in-depth description. In that sense they complement each other. Make no mistake, though: this book is not a comprehensive reference for the standard library (just as "The C programming language" is not a complete reference for the C standard library).

i write in ruby for about a year or two, mostly as a hoby. after i wrote a lot of simple and complex programs, there were still some basic (or not so basic) things that about ruby that were not so clear to me. this book made it all clear. all i can say about this book is that it is a great book and i recommend it to anyone programming in ruby.

I didn't know any significant HTML prior to using this book. This book is a great starting point and will give anyone enough background to put up a pretty good page. I feel like I have gotten a good grasp of HTML from this book and now feel like I should branch out into Javascript to develop my pages further.

Oliver & Morrison offered good advice on what to do and what not to do when designing a webpage, and they also explained why they make those suggestions, which certainly assists in making later judgement calls on topics they don't directly address.

I would also recommend O'Reilly's HTML/XHTML book, which has come in handy in clarifying a few points. However, this book is sufficient for anyone looking to put up realatively simple pages and is easier as an introduction (and more motivating) than O'Reilly's book. That is, buy this book first and buy O'Reilly's book if you have a desire to learn more about HTML.

Having been out of web Development for a couple years, I needed confidence that my basic understanding was up to speed. This book HTML and XHTML in 24 hours, brought me up to date rather quickly. It provided the foundation that I needed both to build some basic web application prototypes, and to be able to begin reading more specialized books on Web Development. Specifically books on CSS.

This text will not make you a wizened internet programming guru... but it doesn't pretend to do so. What it does promise, and deliver, is a solid grounding in the creation of basic web pages. The book starts with the absolute basics; nothing is assumed. Finding someone to host your web site is covered, as is the creation of files using the Windows Notepad text editor and the uploading of files onto a web hosting computer. And, of course, there's a tremendous amount of detail in creating web pages.

It's important to note that there are two approaches to creating web pages today: you can create them by hand, using XHTML code written with a simple text editor like notepad; or you can use a web page authoring package, such as DreamWeaver or FrontPage. Using a program like DreamWeaver (most agree its the #1 program of its type) will allow you to create web pages much more quickly than by hand coding them; and unless you have an innate skill as a design artist, they will likely look better than something you hand code.

On the other hand, you'll never have a clue about how the code actually works, if you don't learn XHTML; and so you'll never be able to modify it. You'll be stuck with whatever the web authoring package can do for you. And there's also the cost factor: web authoring packages cost several hundreds of dollars, but notepad is free; it's part of the Microsoft Windows operating system. (Macs have a similar built in text editor.)

Most internet pros can do both; they regularly use DreamWeaver as a production tool, but know XHTML so that they can quickly modify what the program generates when the need arises. On the other hand, amateurs building simple web pages probably would never be able to justify the cost of a full blown web authoring package, so learning XHTML makes perfect sense.

Either way, learning XHTML is an appropriate way to start your web page building education; and this book is the perfect way to do so. Having read several books on the subject - including some thousand+ page hardcover whoppers - I can confidently state that this book does a spectacular job of teaching you exactly what you need to know. It gets right to the point, and quickly and simply teaches the core material. All the fluff is gone; everything in this book is solid. There's thorough coverage of graphics, animated graphics, even some javascript. There's a lot of reference to readily available tools on the net, and some indication of how they might be used. I was particularly impressed with the clarity of the instruction; the book does a spectacular job of identifying and teaching exactly what needs to be taught, while deftly avoiding extraneous discussion. Most universities don't provide a quality of instruction as crisp and as easily followed as that contained within this book.

So what's missing? Not much. There's no coverage of Flash to speak of, or CGI scripting. I didn't see any mention of secure HTML, so you'll need more than this book in order to start processing credit cards, or conducting commerce. And a few of the web resource links that the author provides are dead links, and haven't worked for years; they should have been caught during the revision process.

But these are mere quibbles; make no mistake, this book gives you an awful lot. If your desire is a really good book that starts right at the very beginning, and gives you enough knowledge to build really good looking web pages from scratch... then this is your book. If you want to set up a simple web page for yourself - or an informational web page designed to promote your home business - this is a great text. And if you plan on persuing a career as a web page developer, but have no previous knowledge of web design or HTML... then this is a great book to start with.

The book is now in its 6th edition, and that says a lot; publishers won't revise a book with poor sales. For a computer book to be revised and released 6 times is a dramatic testament to its popularity, and inherent quality. I can only think of one other book on my bookshelf - Muellers' Upgrading and Repairing PCs - that has shown such a continuing popularity level.

When you invest in this book, you get a lot of value. When you've learned and applied everything in this book, you'll be able to create extremely good looking and well written informational web pages from scratch, without having to rely on a web authoring package; and you'll be completely prepared to learn the intricacies of Java, Flash, and CGI scripting, if you so choose. However, probably 90% or more of the people who read this book, will never need to move beyond it.

For most web pages, this book is all you'll ever need.

I have been using a canned program to manage my company's web site, but I wasn't always able to do fine tune the pages the way I wished. So I decided to teach myself HTML. Working through this book, I was able to learn step by step how to design pages and manipulate the images and text. The book is very clear and concise and the exercises the author gives at the end of every chapter are extremely useful.

Best computer related book that I have ever read. I was somewhat familiar with HTML concepts, but never created my own web page. The lessons are organized well and are so easy to follow! They even go over applets, Active X, and JavaScript. Awesome, awesome book.