Internet Books

Photoshop CS3 is a very "deep" application, and I think that this book can be an excellent resource for virtually any CS3 user (especially those who classify themselves as intermediate users of Photoshop). The author does not assume that you have already read a user manual or other book. He covers in detail many of the tools in detail that are frequently used to color correct, mask and composite images, and do many other common tasks. "Hints" and "Notes" can be found throughout the book in small green boxes, and I found them very helpful. For example, in Chapter 10, the author explains in a Hint box how to apply sharpening settings from one image to a batch of images in Bridge.

Weinrebe supports his lessons with good screen shots throughout the book. Just a small selection of the tools that he covers very well (in a step-by-step fashion) are the Healing Brush, Lens Correction tool, History Brush, the Bridge and Camera Raw (including a suggested Bridge/Camera Raw Workflow), tinting with a color layer, batch renaming, converting to DNG, creating contact sheets, creating panoramas with Photomerge, and actions.

One of the most interesting parts of the book are the artist interviews. These Q&A sessions with such luminaries as John Paul Caponigro, R. Mac Holbert, Pedro Meyer, Graham Nash, Maggie Taylor and Joyce Tenneson generally run from about 4-7 pages and include fantastic imagery and insight about the artists' background, their art, what motivates them, and how they approach and use various technologies. I believe that this series of essays could easily be a very strong coffee table book on their own. They are a really special.

I also like the Chapter Reviews questions and Exercises at the end of each chapter, which can definitely help people to learn more about the Photoshop techniques that were covered in the chapter. Having all the exercise files on a CD in the book is also a nice feature. Also, it really helps that Weinrebe is a professional photographer who has been preparing files for clients for years. His work really shines throughout the book.

As a long time film photographer making the move to digital this book was a life saver. The step by step approach took the mystery out of photoshop.
The language was clear and the examples relevant.

The development of pigments by chemists changed the art of painting in the Renaissance. The development of film sensitivity changed the art of movie making in the 20th century. How will Photoshop and other image processing software change the art of photography?

This book provides instruction in the use of Photoshop, in an unorthodox manner. Most Photoshop books are organized along workflow lines, although a few work their way through each of the Photoshop tools and menus in order. Weinrebe follow his own order, dealing with light and shadow, curves, black and white processing, color tools and so forth before dealing with the tools used when first bringing images into Photoshop. Often a chapter introduces important techniques not related to the main one, as in the author's discussion of the use of the history brush in the chapter on curves. The author recognizes his approach is unusual, and suggests that readers go through the chapters in the order the reader needs.

The chapters include practical exercises that use images provided on an included CD.

The book recognizes the version 4.1 update to Adobe Bridge which is a component of Photoshop CS3, although I expect that the update was made available at too late a date for the author to do much exploration of its potential. (There has been a 4.2 update, but the changes seem to have improved code, without adding tools.) How else can one explain the author's dismissal of the new sharpening facility that allows for input sharpening, which is different from output sharpening?

Besides the instruction on using Photoshop, each chapter concludes with an interview with a famous photographer. Most of these photographers seem to specialize in montage, that is, the creation of pictures by combining images.

My biggest question was what happened to "the Art of Photography" mentioned in the title? Nothing in the material on technique goes further than to describe what controls and sliders create what effects on an image. No advice is presented in how to use Photoshop to create a picture that is more "artful" (whatever that means). The interviews are interesting but they don't include any information on how the artists used Photoshop to make their pictures more artful. I suspect that even Rafael received some instruction from his teachers on how to use the new pigments beyond how to apply them to canvas. Certainly, a few books on Photoshop have covered this terrain. I particularly found Rob Sheppard's "Outdoor Photographer Landscape and Nature Photography with Photoshop CS2" to be useful.

I also have some small complaints about the book. The text always appeared to be one or two pages behind the related illustrations, leading to a lot of page flipping. Some instructional areas seemed to scant the tools being discussed. For example, the chapter on Adobe Bridge mentions how customizable Bridge is, but neglected to provide any details in how to do this.

Still, a photographer looking for an introduction to Photoshop will be able to get started with this book. On the other hand, those looking for a more detailed introduction might want to look at a favorite of mine, "Photoshop Artistry: For Photographers Using Photoshop CS2 and Beyond" by Barry Haynes. It doesn't cover all the changes made to Photoshop in its later versions, but it will provide an understanding of the software that may even include a little bit about injecting the artful into one's images.

the book is well worth the cost: it is well organized and presents all of the capabilities of Photoshop in a pseudo-textbook fashion that are easily understood. At the end of each of the 12 chapters, the author presents a review: questions that the reader should be able to answer and exercises covering the CS3 capabilities that had been explained in that specific chapter. Also, the author includes interviews with 12 noted creative photographers such as Maggie Taylor and Lois Greenfield.

Photoshop is incredibly feature-rich software, and frequently perceived as overwhelming. Weinrebe breaks it down into easily understandable bits while still providing useful tips for very experienced users.

And the interviews with renowned photographers add a unique element, opening - at least a little a bit - a window on their varying perspectives and workflows.

Well done. This book is a valuable addition to every photographer's reference library.

It's simple, really: If you're programming with Rails you should buy this book. Let's face it, one recipe that shows you how to do something is all that it takes for this book to pay for itself.

Some of the recipes are meant to be looked at on an as-needed basis, e.g. searching using Solr, Sphinx, or Ferret, and sending email via Gmail. But most of the book can be simply read as a way to learn more about Rails, e.g. customizing error messages, testing with RSpec and Shoulda, and caching strategies and tools.

I just got my copy yesterday and am having trouble putting it down! This book reads better than a novel/story if you have even a remote interest in Ruby on Rails. Mike Clark has done an outstanding job of putting together really interesting recipes contributed by Ruby on Rails enthusiasts from all over the world and an equally good job of quality assurance. I really hope that he works on producing a sequel as soon as possible.

This is not only a phenomenal reference, but it is great for whetting your appetite when embarking into new Rails territory -- the book is full of ideas, that Rails devs of all levels can benefit from. Reading this book gave me an additional perspective on items I practice and those I am learning -- specifically enjoyed the parts on REST, CC payment processing, scalability, testing. Highly recommend.

I went through this book cover-to-cover every few pages saying, 'Wow, I could have used/need that now!' If you're a RoR developer, you really should have this book on your shelf. I marked maybe 75% of the recipes as something I could use--worth it's weight in gold!

This book is a must have resource for anyone developing Rails applications. Mike Clark, the Ruby community and the Pragmatic Programmers have once again delivered a set of recipies you'll find immediately usable. I'm already using four in an application I'm working on, all of which have helped me reduce code, increase readability and reduce maintenance.

The book is thoughtfully organized with each recipie being both well written and concise.

No matter what type of Rails application you are writing, or your level of experience, I think you'll find something in this book to make you say "Thats a great idea" and rush to the keyboard to try it out.

If you understand Agile and your team adopts all the practices with success overnight, then this book is not for you. If like the rest of us you have an understanding of Agile, but need some help to go beyond a few superficial practices, then buy the book and use it!

Amr starts with the fundamentals of Agile, from its deep roots in team dynamics and individual attitudes, and then guide you towards building a strategy for Agile adoption - not a generic strategy, but one that is adequate for your team and your objectives. Once the strategy is defined, we can put the Agile patterns to good use, one at a time, in good order, while minding the impacts, consequences and pitfalls.

This was exactly the book I was looking for. For my longer review, please refer to: http://freedomforideas.wordpress.com/2008/09/16/agile-adoption-patterns-1-2-3/.

Proven patterns for succeeding with Agile in an organization are presented in a series of case studies and hands-on exercises in Agile Adoption Patterns: a Roadmap to Organizational Success. Here are the most common stumbling points teams face in implementing strategy, along with tips on how to teach, train, and bring customers on board to an agile environment. Any Agile project manager will find this an excellent series of tips, making this perfect for software engineering collections.

There are many books about the theories and practices that are encompassed in the word "agile". Quite a number of them are quite good in terms of addressing the specific practices and how to implement them. It you want to learn Scrum or XP, there is no shortage of books and how-to materials, along with plenty of advice.

This book, however, addresses the goal of agile adoption from a new perspective - patterns of behavior and thought, and how to specifically leverage and/or address them. It addresses this from the organizational/team perspective, rather than the individual perspective, which makes it particularly valuable for those of us who are working in an organizational transformation/agile adoption environment.

While it might seem that "patterns" would appeal to the techies in its audience, my experience is that Amr has managed to frame his work in terms and concepts that are readily understood by all. This book is readily digestible by non-technical managers and staff, as well as by those of us who have spent/currently spend our time in a technology environment. It is not necessary to understand what design patterns are, for instance, to understand the patterns in this book.

For those who are either anticipating agile adoption or actively engaged in it, or even those who are struggling with what seems to be a failed adoption, this book is required reading. The way in which the patterns are presented, the clear and pragmatic exercises described to help work through them, and the suggestions for ways to approach it all are just what's needed.

Real world, pragmatic, easy to read, and easy to digest - that's what this book is all about.

It will be on my desk and heavily thumbed in short order.

There are plenty of excellent books available that explain agile practices. What has been missing until now is the guidance to apply them. Amr's approach to achieving agile practices is filling a need that has been felt by many for several years now. Amr takes an excellent approach to identifying the best means of applying agile techniques based on a combination of business needs and project pains. This approach stays focused on delivering business value to the enterprise as they move towards agile practices.

Amr has an excellent writing style that is both concise and entertaining delivering information in a manner that can be absorbed in bite-sized chunks and applied as needed based on the initial needs assessment. After identifying the business needs or pains the best agile practices to deliver the value or reduce the pain are described in a manner that determines which practices will deliver the best value to meet your identified needs.

I highly recommend that you pick up this book if you are either planning to adopt agile practices, struggling to adopt agile practices or are looking to enhance the agile practices that you currently employ. Well done Amr.

There are many things I like about this book, not the least of which is that it is true to the "spirit" of patterns and agile -- it does not promise easy answers or quick fixes but offers down-to-earth advice based on experience. The patterns do a good job of capturing that experience but the way the patterns are written, with "threads" of stories throughout is not only convincing but enjoyable reading. I like being able to follow the real-life adventures of the same developers who struggle to solve real problems across several patterns. I also like the case study in Chapter 46 where a real company with real problems does a pretty good job of moving forward, but it's not a "and they all lived happily ever after" scenario. We're overwhelmed with books and advice these days, so it's nice to see someone who offers help and hope but not hype!

Very comprehensive... a lot of bang for your buck in a little book. I keep it in my laptop bag 24/7 now.

I, incredulously, bought this book not expecting to refer to it because I know everything ( ;-P ). I have found that it a most invaluable resource. If you know (and love) Apache, this is the synopsis you need sitting on the left hand side of your keyboard.

For material that's mostly already online, this book is a good investment. I get really tired of window-switching references, and sometimes I like to sit away from the computer while I'm looking up stuff on directive syntax or whatever. For that, this book is worth the price.

I'd still like a more suitable binding for a small book with a font chosen for density. Lord, won't you make me said book so it will lay flat? That would make this dealie a five-star pick for me.

This little book covers the latest version of Apache, and was packed with info for its size. If you're already familiar with other releases of Apache, then this is the perfect book for you - and all you'll ever need!

A large system of configuration commands and syntax is a useful and powerful tool for allowing people to easily control complex pieces of computer software.

Large configuration files have one major problem; you tend not to look at them often enough to get the language and syntax down pat. You find yourself making too many tiny errors in command name or syntax and struggle with one window editing the file and one or more windows open displaying the documentation.

With Apache I have this problem in spades. The configuration system may be well designed and the syntax as easy as possible, but most people will still struggle to keep every detail in their head. I know what I need to do, have a fair idea how to do it, but the details elude me.

That's where this little volume comes in immensely handy. I have several of O'Reilly's pocket references and find the PHP, Apache and Perl ones never stray far from my computer. This one provides a wealth of reference information packed into a small, inexpensive little volume. It has enough information about the exact name and sytax of the Apache configuration directives that I don�t need to go to a larger book or delve into the manual.

Oh, and for those that want this volume to lay flat. I ran my copy through a paper cutter and trimmed the spine off. After punching holes in the pages I then had a loose leaf version that allowed me to add my own pages of notes in various spots and lays perfectly flat. It only took a few minutes. Sorry, O'Reilly - but it is more useful if it can lay flat and being able to add notes is great.

Hi, when I heard about this book, I said I worked so hard with parenting links on my online Baby to Toddler store, when this book would be also a great resource too. Every new parent should have it by their computer-side! The thing is, new parenting sites happen all the time, so don't be complacent, buy the Next Addition(s) too, if you can*! or visit regularly the Publisher's website to see the New sites to be Listed in the next addition!
* My experience it sells pretty quickly! ...

If you have a baby, or need to purchase baby items, or need information about babies, then this is the RESOURCE to get it from. Gretchen Nalley has carefully placed all the websites that pretains to babies, from baby gifts, to parenting to care of baby and everything in between. A quick reference guide to take you to where you need to be without having to search and search. Thank you Gretchen for a job well-done!

I am one of the unfortunate ones who had their kids too early for this book, if only it had been around when they were younger. But that hasn't stopped me from buying this book - I have given it as gifts! The time saved in not having to search the web for the websites & information that is in this book is invaluable for parents that already find their time at a minimun with the demands of a new baby.

This is a must have!

Never has a book been more useful! This directory is a parent's dream. Have you ever looked up "baby" in the yellow pages? There sure isn't much there. My only regret after buying The Baby Web is that it wasn't available with my first two kids! I love it, and the pictures are adorable! No new parent should be without The Baby Web (I keep mine in my purse!).

Everyone knows that the Internet is a great resource for information and a great alternative to traditional catalog shopping. Unfortunately, weeding through literally millions of sites can be both time-consuming and frustrating. Since time is a precious commodity when you have young children, getting someone else to do the weeding is a welcome shortcut, and that is what this book delivers. Think of this book as the yellow pages for baby websites.  The 1,200 sites are listed by category and also in an alphabetical index. Categories include: Announcements, Baby Care Products, Baby Gear, Baby Names, Bedding & Furniture, Clothing, Food & Feeding Supplies, Gifts and Gift Baskets, Health & Safety, Parenting Advice, Pregnancy & Breastfeeding, and Toys. Many of my favorite sites were listed, and some new ones that I have since bookmarked.  This book is a great starting point for a new parent or someone new to the web, but it is also a good resource for anyone interested in finding new websites for parenting tips and products on the Internet.  There are a couple of sites that I probably would not have included if I were making a list since they offered only one or two items or were intended for dealers rather than consumers, but out of 1,200 sites that's a pretty good track record.  You will need access to the World Wide Web and a basic understanding of navigating the web to get the full benefit of the book, although many of the sites listed also include a customer service phone number.  --Reviewed by Teresa Burgess

For someone who started teaching in the days of spirit duplicators, long before copiers, computers, and the internet, I found this book to be both useful and very inspiring. It is clearly written, full of clear illustrations, tips, and resources. I've been looking for ways to incorporate more technological tools into my U.S. history course, in ways that further my teaching and my students' understanding. This book provides a clear path to follow. It is, by far, the most practical text on the use of technology in the classroom that I've read. As I work on new course materials and lesson plans, Best Ideas is always close at hand.

This book does a great job of giving ideas that are both practical but still ambitiously tackle some of the most exciting trends in ed tech today. Inviting tone and supporting resources. Great work.

As a teacher, nothing frustrates me more than knowing tools exist, even what the tools are, but not knowing how use them to increase students' learning. Daccord and Reich, both top-notch teachers, have done a superb job of solving this problem through clear but imaginative explanations and suggestions for recruiting the extraordinary possibilities presented by recent developments in technology, especially via the Internet.

Rather than being daunted by all these possibilities, picking just one or two great ideas from this book and folding them into one's teaching practice can have salutary effects on student learning and teacher enthusiasm for new ideas and approaches, and once those become habitual, one can return to dip again into this cornucopia of great ideas, exercises, and activities.

If you are a teacher or educator looking to develop ideas to utilize technology into your classroom this is a must have book. There are 10 chapters ranging from Enhancing Teaching and Learning with Multimedia to Class Management. Each chapter features one or two tools with specific directions (simply written) on how to use the tool as well as hundred's of web site's that are relevant to education. If you are someone who is looking to take technology into the classroom or want to learn more this is a well written, well researched book. I highly recommend it, you won't be disappointed!

The title of this book says it all. This book provides great background information and simple strategies for teaching WITH technology. As a professional development provider, I often see teachers struggle with how to use technology in their classrooms. Best Ideas for Teaching with Technology not only gives the background knowledge that teachers need, but it also shows teachers how to use technology as a tool to engage students in the classroom. Even better, the book is well-organized and an easy read - a great time saver for all busy teachers!

Those who are about to read this book need to keep in mind that in it, Robert Bly shares his thoughts about what blogs cannot do (nor be expected to do) as well as what they can do. Over the years, he has earned and deserves his reputation as a master of reasoning, reading, and writing skills...whatever the given genre may be. Among his previously published books, my own favorites are The Copywriter's Handbook, his Guide to Freelance Writing Success, and most recently, The White Paper Marketing Handbook. In his latest book, Blog Schmog, he focuses on "the strategy of using blogs as a business-building and marketing tool, explaining how your time is best bent on strategy, not fooling around with programming or design." Bly then goes on to explain, in the Introduction, that his book "is written from the point of view of a blogging skeptic and doubter, not one who has bought into the whole blogging fad without holding it up to close scrutiny... And my conclusions about blogging, unlike those of [blogging consultants, enthusiasts, and evangelists], are not always favorable; my positions on blogging are highly controversial within the blogosphere." He urges those who read this book to share their comments ideas, techniques, and/or success stories with him at rwbly@bly.com or to visit www.bly.com.

Who will derive the greatest benefit from this book? Probably, those in need of expert advice on how to start their own blog, and, those who have done so and are dissatisfied with the results thus far.

Time Out: There are significant differences between personal blogs and institutional blogs. Therefore, those who are about to launch either a personal blog or an institutional blog should first answer the six questions posed on Pages 55 & 56 in Chapter 2, "How to Start Your Own Blog." (Bly cites Elisa Camahort's Worker Bees as their source. Her Web site is workerbeesblog.blogspot.com.) Moreover, I think that those who have already launched a blog and are not satisfied with results thus far should also answer these six questions. For those with a special interest in institutional blogs, Bly provides an insightful analysis of do's and don'ts in Chapter 7. Then in Appendix E, he identifies "Business Blogs Every Blogging Newbie Should Know" and provides links to them.

To me, some of the most valuable information and counsel are found in Chapter 3, "Blogetiquette: The Rules of Blogging." He shares his responses to a number of frequently asked questions. For example:

Is "selling" a person, a company, or a product acceptable in the blogosphere?

How to treat copyrighted material in a blog?

Why are corporations afraid of blogging?

What is the "bloatosphere" and what's wrong with it? (Note: Bly cites Steven Streight, president and CEO of Streight Site Systems, as his source for much of the response provided.)

What is "ghost-blogging' and why does it occur?"

What about other types of blogs such as "simulated," "drivel," "sleazy link," "fictional persona," and "link farm?" What does Bly think of each?

Throughout his narrative, Bly inserts a series of "Rules"(also listed in Appendix B) and provides a context for each. (I highlighted each of them to expedite periodic review of them later and suggest that other readers do the same.) He concludes this chapter with Rule 8A: "To be effective marketing vehicles, blogs should be relatively free of marketing. They should contain useful content and the truth, not hype or sales talk. To violate this rule not only costs you sales and credibility, but it also incurs the disdain and wrath of the blogosphere." He makes essentially the same assertion about white papers in an earlier book, The White Paper Marketing Handbook.

In the final chapter, He shares a number of opinions whether or not blogging has a future and many of these opinions are certain to generate controversy. (Bly urges those who disagree with any of them to contact him at rwbly@bly.com. He plans to share feedback with readers of the next edition of this book.) I strongly recommend, however, that the first nine chapters be read with great care, first. I cannot think of a better way to conclude this review than to share the conclusion to Bly's book:

"So blog if you want to. If you don't like blogs, don't bother. And if you think the advice in this book is great, and you want to let me know, or if you think I don't know beans about blogging and that my advice is useless, you can certainly say so - on my blog.

"Best of luck to you in the blogosphere - and outside it!"

I just finished reading Bly's book and as a direct response writer, I found his observations on the "blog scene" to be dead on.

When blogging first starting coming up on my radar, I looked into it briefly and didn't understand the fuss people were making over it. It seemed very much like what people used to do on BBSs (I used to be a sysop of a BBS back in the late twentieth century). Anyone could access a BBS and anyone could comment on the author's writings for all the world to see. So, what do I see on blogs? Much the same thing. People read what you write, choose to comment, link to you or you link to them. Same thing, different year.

I also echo Bly's observations that many blogs are unreadable and do little to further marketing goals. Many I've read have interesting things to say, but they're written in long, unbroken blocks of text, which cause me to stop reading part way through out of boredom.

But, the main reason I don't like blogs is because of the toffee-nosed way it's being promoted. That, and I just hate the word "blog." It sounds like something a cat coughed up--which, now that I think about it, might just be an apt description for much of what passes for content out there in blogland.

Many blog evangelists talk about blogging like it's something new and revolutionary. Psh. It's old technology with a facelift! I've heard that "blogging is all about having conversations!" Someone in Bly's book said this very thing. This same guy spoke of blogging in a weird Jack Kerouac-ish way that made me want to reach for an air sickness bag. I envisioned him wearing a tie-dyed shirt, a grateful dead headband, and little John Lennon glasses--typing furiously with two fingers in some off-campus "Café Nervosa."

A great read, Bly's book. I'd recommend it to anyone contemplating blogging so that they can avoid the hype and not be taken in by dewy-eyed blog-angelists.

I enjoyed reading this book. It confirmed what I already knew about blogs and blogging. I highly recommend anyone interested in exploiting blogs for financial gain get a copy of this book and read it.

The overall message of the book is that blogs help increase a marketing-focused Web site get favorably ranked with search engines. Therefore, indirectly they help in marketing. But blogs are not a marketing tool in and of themselves unless one treats article writing as a marketing tool.

Building Web sites has always been pretty easy. And blogs are Web sites. What has always been somewhat hard is designing a Web site and filling it with content so visitors to the Web site will be inclined to buy a certain product or service. Since blogs by definition are not seriously researched or planned, their ability to convince visitors to buy is limited. And, as a result, their marketing value is not that great. However, Web sites do not exist in a vacume. They rely to some extent on getting traffic from search engines on the Web. And blog entries help in a few ways with getting a Web site some traffic. First, they provide content in a Web site that search engines index. At least this is the case when the blog entries are stored on Web pages within the blogger's main Web site for marketing purposes. Second, blogs are possible "hit pages" surfers will click through to when trying to find information. Such pages will then direct the surfers to "marketing pages" in the blogger's main Web site set up for marketing purposes. And third, if the blogs are freestanding, then they can provide external links directing Web surfers to the blogger's main Web site which has marketing umf. Search engines rank a Web site more favorably when other Web sites direct traffic its way.

The book also points out that the best blogs from a business' standpoint are "topical blogs." And the businesses that usually benefit are service oriented (as compared to retail oriented). For example, a consultant who counsels small business owners might have a blog that only includes entries about small business. A life coach might have a blog that only includes entries regarding life coaching issues. Or a bankruptcy attorney might have a blog that only includes entries regarding Chapter 7 personal bankruptcies. The blogs will probably help boost surfer traffic to their main Web sites, but they will also help build credibility for their respective services. Assuming the blogs have accurate and timely content, then the bloggers arguably will be viewed as "experts" even though they haven't gone through the hassle of getting a book published or passed some professional exam.

But there are many blogs out there that are not topical, are not accurate and timely, and don't really say anything worth reading. Those are the blogs that the author says are not worth producing. And I agree. 5 stars!

Finally a business book that is unpretentious. Blog Schmog is not one of those books that takes one good idea and then tries to stretch it beyond its boundaries just to get a specified page count.

Bob Bly is a direct mail copywriter and by his own admission does not buy into the blogosphere hype. But he decided to delve into the world of blogging and find out what it was all about (probably so he could write a book). The fact that Bly is not a blogging expert is exactly what makes this book valuable to someone thinking of starting a blog.

This book gives you an unbiased view of starting a blog from scratch and leaves out the sales pitch you would get from a blogging guru trying to sell you the latest patented system for starting a blog.

BS is short on technical advice but does give you resources and plenty of website addresses to get you started. What you will get out of this book is why you should start a blog (if you should) and what is the most effective way to write a blog. If you are already a seasoned blogger, this book is probably not for you.

If you are thinking of starting a blog, or just trying to get more comfortable writing one, I recommend this book. You won't be an expert after you read it, but you will have a better perspective of blogging.

Robert Bly's BLOG SCHMOG is a balanced, openly honest, "no pie-in-the-sky" assessment of the craze which has swept across the internet, namely blogging. In short, the book's subtitle "The truth about what blogs can and can't do for your business" tells the buyer exactly what to expect if they buy and read this book. In fact, that is exactly why I purchased this book because I am on the cusp of setting up my own blog. I was not disappointed.

In conceptualizing and framing his book BLOG SCHMOG, Robert Bly has targeted a wide audience: new bloggers, blog enthusiasts thinking about designing and launching their own blog, and internet surfers who have been blogging for awhile.

BLOG SCHMOG is a three-tier crash course in how to realistically analyze blogging application and effectiveness, how to measure the effect of blogging on current marketing and media trends, and how to create your own effective blog that will lure in readers and participants. The back matter or appendices of BLOG SCHMOG contain invaluable information: detailed notes from each chapter, blogosphere rules & etiquette, a comprehensive list of blogging books & guides, blogging consultants with their emails and phone numbers, blog software, blog search engines, a litany of successful business blogs covering an array of topics, and a glossary of blogging terms so the newbie does not remain a newbie.
.
A word to the wise should be the mantra for this book. In other words, underscoring all of the above is a golden thread that runs through his book, namely, do not miscalculate or overestimate the effect that your blog will have on your business. Do not live in the fantasy world of blog. Be very clear about what your blog can do for you, in terms of a return on your investment ROI, whether it is financial, advertising, or just broadening your reputation via the web. Your ROI is always a balance between weekly time invested in your blog versus what do you get in return for giving up that time. What Robert Bly makes clear in BLOG SCHMOG is that blogging is a new phenomenon whose long-term effects are yet to be measured in the commercial marketplace. He does cite instances where bloggers have influenced politics; they have fanned the flames of a sweeping news story; and, through the mainstream media, blog designers and analysts have attempted to alter the path of the meandering river of public perception.

All-in-all, though some critics view Robert Bly's perspective and tone more akin to a parent who negatively discourages his child by undercutting his child's goals, I found Robert Bly's BLOG SCHMOG to be an informed primer that encourages the newbie blogger by giving him all the tools he will need to succeed, but Bly does so with words of caution. BLOG SCHMOG reads with experience and careful consideration. In short, it informs. As a writer and businessman, Robert Bly blends his knowledge of writing, marketing, advertising and persuasion into a most pleasing and rewarding work. BLOG SCHMOG is worth every penny.

John M. Weiskopf
Author, The Ascendancy
[...]

This book is essentially an overview of the development and evolution of the Internet, ending with the browser war between Netscape and Microsoft. It was initially published in the UK in 1999, then in the US in 2000. There is some discussion of the intellectual backstories such as Norbert Wiener's cybernetics and JCR Licklider's ideas on interactive computing, but the book is mainly about the birth and growth of the Net. This book lacks detail - and is in that sense superficial - but it works well as the general overview the author meant it to be.

What does the Internet mean for the future? An answer partially depends upon an analysis of the past, and John Naughton's Brief History of the Future is the first book to cover the entire history of the Internet's development, from those who first thought of it in the 1940s to the scientists and engineers who brought it to life. Anecdotes blend with history to provide an intriguing blend of personal and scientific observation.

Reads like a sci-fi novel while providing a solid understanding of how and why the Internet works. At times the detail is almost overdone but this only adds to the credibility of the author. I started with a Timex Sinclair computer and have lived through the period covered in this book without really understanding just what made the internet work. Now I know!

Next time you take a transcontinental flight to a technical conference, skip the airline movie and just read this wonderful book cover to cover. I wish history class in high school had been this much fun. Naughton has written the definitive history of the Internet so far. For example, when the Pentagon asked AT&T to build an early prototype of the Internet for them, AT&T pooh-poohed packet switching as a worthless idea concocted by some young whippersnapper (Paul Baran of the Rand Corp.) who knew nothing about proper telephone engineering. The book is full of anecdotes and funny stories. Great reading for old fogies and young fogies alike.

I've worked in the software industry for twenty years, and now I finally have an entertaining, enjoyable book to give to friends and family who don't really understand what I do all day. If you've ever struggled to explain how the internet works, or why anybody would use it. This is the book. I gave a copy to my 77 year old flight instructor, he loved it.

I bought this book for general project evaluation purposes, for a project that I was called in on that was in trouble.

Well worth the read - a lot of it is just good common sense, straightforward project management process, but it provided a great roadmap for validation of my plan to put the project back on track.

Definitely would recommend it - it's an easy read; I finished it in under 5 hours on the flight out, complete with note-taking. Kudos to E.M. Brennatan for writing this in a straightforward fashion.

It is a law of nature, grouped under the general name of entropy, that it is easy to mess things up and very hard to straighten them out. In fact, it is the natural state of nature to tend towards increasing disorder. This law also applies to software projects, since they are naturally very complicated entities; they easily reach a point where difficulties compound to the point of dysfunction. The author calls this state a catastrophe, although in my opinion that is an overstatement.
A catastrophe is a major disaster, far beyond what most software development projects actually are. Granted, there are problems, but most of the situations described in this book are ones that can be recovered from with more effective planning and focused execution. The author puts forward a ten-step plan for disentanglement:

1) Stop the project - not permanently, just long enough to examine the project in detail before things get worse.
2) Assign an evaluator - a disinterested party is assigned to perform an honest and unbiased appraisal of the project and what is going wrong.
3) Evaluate the project - the evaluator takes the lead in doing a complete dissection of all aspects of the project, what is being done right and what is going wrong.
4) Evaluate the team - examine the people working on the project and determine if all are suited to their jobs and if all are performing at the appropriate level.
5) Define minimum goals - determine what is considered to be the minimum level of achievement that will be considered a success.
6) Determine if the minimum goals can be achieved - if the minimal level of success is not possible, then the decision must be made to terminate the project.
7) Rebuild the team - this step has two basic components. Personnel changes if necessary and reinvigorating those who are going to remain part of the team. One of the greatest tasks is to overcome the defeatist mindset.
8) Risk analysis - attempt to identify all possible risks and assign a reasonable probability of occurrence to all of them.
9) Revise the plan - as circumstances change, modify the plan to reflect the different conditions.
10) Create an early warning system that will flag the appearance of problems when they are not yet serious.

These ten steps are each the topic of a chapter. Exercises for further practice are included at the end of each chapter, although no solutions are given.
I enjoyed the book; it contains a lot of sound advice on how to right a rudderless software project. Most of the advice will work only on a project that is not yet seriously out of control. Quite frankly I don't believe that a ten-step plan like this is powerful enough to get the most dysfunctional death marches back to a point of potential profit. Therefore, while I believe that the advice is sound, it is limited in scale, where the measurement is of the level of dysfunction in the project. On that basis, I can recommend the book.

Catastrophe Disentanglement : Getting Software Projects Back on Track teaches the kind of skills you hope you never have to use. It's something like taking a CPR class for project management. You hope you never have to administer CPR in real life, but when you do get put in that position, you're really glad you have that training to fall back on. That clear, logical list of steps can mean the difference between life and death. In the world of project management, the skills taught in this book can save projects and careers.

This book differs from traditional project management books in that it focuses on corrective rather than preventive measures. The author teaches two critical things. First, he presents a set of criteria used to recognize a project that is in need of rescue. This is an important step! Once a project is identified as seriously out of control, you can apply the steps presented in this book to bring it back on track and guide it to a successful completion. This book will give you the reasoning and courage necessary to make hard decisions.

Table of Contents
Chapter 1 An Introduction to Catastrophe Disentanglement
Chapter 2 When Is a Project a Catastrophe?
Chapter 3 Step 1--Stop
Chapter 4 Step 2--Assign an Evaluator
Chapter 5 Step 3--Evaluate the Project
Chapter 6 Step 4--Evaluate the Team
Chapter 7 Step 5--Define Minimum Goals
Chapter 8 Step 6--Can Minimum Goals Be Achieved?
Chapter 9 Step 7--Rebuild the Team
Chapter 10 Step 8--Risk Analysis
Chapter 11 Step 9--Revise the Plan
Chapter 12 Step 10--Create an Early Warning System
Chapter 13 Epilogue: Putting the Final Pieces in Place

I would recommend this book to anyone involved in software projects.

Good book, good subject, well covered. The book builds an organized process around the rescue of a failed (or failing) software project. The steps are easy to read and understand, and seem well thought out. Some good methods for identifying projects headed for serious trouble. Also, some useful guidance on how to handle political (not just technical) problems. Obviously, the result of significant experience. Well recommended.

There are plenty of books that try to help you keep your project on track. But what happens when you are sitting on a catastrophe and you don't know how to salvage it? E. M. Bennatan fills a necessary niche with the book Catastrophe Disentanglement : Getting Software Projects Back on Track.

Contents: An Introduction To Catastrophe Disentanglement; When Is A Project A Catastrophe?; Step 1 - Stop; Step 2 - Assign An Evaluator; Step 3 - Evaluate The Project; Step 4 - Evaluate The Team; Step 5 - Define Minimum Goals; Step 6 - Can Minimum Goals Be Achieved?; Step 7 - Rebuild The Team; Step 8 - Risk Analysis; Step 9 - Revise The Plan; Step 10 - Create An Early Warning System; Epilogue - Putting The Final Pieces In Place; References; Glossary; About The Author; Index

If you're in IT for any length of time, you'll be part of a project that is massively over budget or late. Rather than just continue the death by 1000 cuts or a quick mercy killing, Bennatan presents a ten step process that allows an organization to take a (hopefully) objective look at the project and decide what can possibly be saved from it. I was impressed that it wasn't a long drawn-out procedure either. The plan calls for an evaluator (or a small team for huge projects) to come in and quickly assess the environment... what's been done, the climate of the team, and what could be redefined as a "minimum system". At the end of this process, the organization should be able to either kill it off with the knowledge that it can't be saved, or continue on with a redefined set of deliverables that are achievable. It won't be everything that was originally wanted, but it will be more than you'd get by letting it die. I was also impressed with the "What Can Go Wrong (And What To Do About It)" section in each step. He doesn't present this as some cut and dried panacea that will flow smoothly every time. It may not be an easy task, but the book will give you the help you need to make it all work.

Definitely a book that is worthy to be on every IT project manager's bookshelf, as you *will* need it some day...

This book is good for Call Mananger version 4.0+, but the latest IPT guide is probably Implementing Cisco Unified Communications Manager, Part 1 from May 2008. It covers Unified Call Manager version 6.0+, so be sure which version you need.

This is one of the best books, easy to read and understand. There are questions at the end of each chapter (which are short and to the point) that help you test yourself on what you learned.

As a technical instructor I have used this book for class lecture. This book has great organization, and coverage of the material. I reccomend this book to anyone looking for study material for CIPT.

This is the best Ciscopress book that I have read, and I have read a few. It explains everything very nicely from designing to implementing VOIP network, Cisco CallManager to handsets. I read this book and was then able to successfully implement VOIP/IPTEL network for the company I worked for. 100% worth the buy.

This book is first a general introduction to voice over internet protocol (VOIP) and to the specifics of the Cisco approach. The basic concept is simple, send your voice communications over the internet using packet switching is a lot cheaper than the traditional Bell system approach of circuit switching where your circuit is vastly underused.

Cisco has put their products together into a product line around their Cisco Unified CallManager product, a part of the Cisco direction called AVVID: Architecture for Voice, Video, and Integrated Data.

While this book has the obvious goal of getting you to pass the Cisco IP Telephony (CIPT - 642-444) exam, it goes beyond what most 'exam cram' books do and will make you much more knowledgable about actually working with the equipment and software. The book gives you a complete background rather than just a list of questions and canned answers.