Programming Books

As a professional db developer, I found this book from Rick Dobson to be an excellent guide to getting you on your way with Access using SQL Server as the back end. This a rite of passage for many Access developers, like me, who find SQL Server kind of intimidating. Rick takes you through every step of the way very logically, preparing you for your next benchmark. He thoughtfully anticipates your next question with a paragraph or two that explains the reasons why you're doing what you're doing and how to do it. No smarmy digressions, bad jokes or confusing examples. Highly recommended reading for IT developers who want to get to the next level of database development. Great job, Rick!

By far the best book I have seen regarding the difficulties encountered when moving an Access application to SQL Server. Until reading this book, I couldn't figure out why my Access queries that were 'converted' into Stored Procedures could not reference each other, why my forms would not work, why the tables weren't updateable (primary keys weren't copied during conversion), etc.
All these and many more perplexing issues are clearly explained here. For quickest results, read Appendices B and C, then the first 7 chapters before trying to convert your first Access database to SQL Server.

Having spent a number of years using Access to develop commercial solutions I recently moved on to Access projects and found this book a real find in getting up and running in a short space of time. Covering each topic in logical chunks I found it to be more than a good grounding in the subject. It is also well written in plain English and avoids the unnecessary complications that are often found in such books and I would thoroughly recommend it to anyone who is considering developing Access projects.

I have years of experience in programming but knew nothing about Access, SQL or VBA when I got my latest assignment. I can't stand those 1000 page books that want to hold me by the hand while I build some simple-minded application through eight chapters. I just need to know the basics quick and then see a few examples of some typical tasks. This book is just what I needed to quickly get me up to speed and working on my own application. There are a few minor differences with Access XP (like changed menus) so you'll need a good XP reference also. I recommend this book to any developer that needs to come up to speed quickly on either SQL or Access.

I just received this book so I cannot comment on its technical merits. However, I have noticed the book is littered with spelling errors and errors in general. Examples are (1) On page 11 "As but this architecture won't be specifically considered furhter".. and yes, I included all the spelling typos. (2) On page 19 "if you had an Access poject" instead of "project." Isn't this what spell checkers are made for? There is at least one more error that I glanced over but did not record. And I have only read to page 19! My experience has been when a book contains many typos then then code should be suspect. I hope not, because a good Access 2000 to SQL book is needed. Caveat emptor!! Paul

... a horrible Prolog tutorial.

This is not a good first book on Prolog. If you are new to Prolog and Logic Programming, you should read 'Art of Prolog' first.

Prolog is quite different from other languages, and you'll need some time to get it. This book doesn't give you that time: after briefly introducing the basic concepts, Bratko dives at breakneck speed into recursion and list processing.

Don't get me wrong, this is a magnificent book on how to do AI with Prolog, but it shouldn't be your first Prolog book. It's an excellent second book.

I remember contacting with Mr.Bratko via mail as I was a university student and I couldn't beleive that this book came from such a modest personality.
The most challanging language, the most challenging programming book I have ever faced with.
Force your IQ with this one.

I find the book does not adequetly explain the more complex code examples. First of all the code is not adequetly commented. Secondly, it does not explain the code well for programmers. First when introducing a program like in the expert systems shell chapter it should first define an interface for the program, and explain each goal listed. It should adequetly explain what each goal and clause should hope to achieve. Also, for the more complicated programs it should draw some type of diagram, maybe a flow chart or something that explains the concepts involved. It leaves too much figuring out and guessing for the reader. It is not very user-friendly!
On the positive side, it does an adequate job of explaining concepts when complex code is not involved. I found that I could follow along on even the more advanced chapters mostly everything at least until code was suddenly introduced. Then it became a guessing game as to what it was trying to do.
The author does not seem to realize that it is more difficult to try to understand somebody else's program than it is to write your own program from scratch. As a consequence the reader wastes a lot of time trying to guess what his program is doing.
Note: this review is of the 2nd edition and does not necessarily reflect the 3rd. But, then again, every other review on this page prior to mine is about the 2nd edition as well!

Although this text is always mentioned in the same breath as other introductory textbooks on prolog, I don't think I've ever seen it described as "the best."
The book which usually takes the palm in such comparisons is "Art of Prolog." While "Art of Prolog" is an outstanding book, I think that now, in 2006, it has been eclipsed by the 3rd edition Bratko's book. Why?

Simply this: Bratko's textbook is (as far as I'm aware) the _only_ textbook on prolog which treats the language as a living, developing language! Other textbooks are great for their time, but they are unfortunately stuck in their time. Its as if nothing has happend to the prolog language since February 16, 1987. But this isn't true at all!

The biggest case in point: constraint logic programming! Bratko's text is the only introductory prolog textbook to even acknowledge the existance of CLP. And Bratko gives very lucid descriptions of it, along with very helpful examples and challenging exercises.

Another case in point: inductive logic programming! An entire new branch of machine learning theory has risen, based on logic programming, and NONE of the other introductory prolog textbooks cover it? Come on guys!

I would love to see a 4th edition of this book, because since this one has been published, logic programming has moved even further ahead. Constraint handling rules (CHR), logical functional languages (like Curry), using prolog for the semantic web, etc etc etc. It might be the best kept secret in computer science, but logic programming is really still one of the most exciting areas of programming, and Bratko's book does the best job of staying abreast of, and conveying the excitment of, this living and dynamic field.

Professor Bratko has done a tremendous job of putting all the fundamental concepts of Prolog and its applications in various areas of AI. Although this book is focused on Prolog, the concepts that he has discussed are so fundamental that they can be implemented in other languages like Java as well.

I recommend this book to everyone who wants to learn Prolog. I would also recommend the readers to use a Prolog system to work out the examples and exercises as s/he goes through every chapter. A DEC10 Prolog system (like SICStus Prolog) would probably be the best companion for this book.

I've been using QuickTime for nearly ten years, and have often been frustrated when trying to explain to people that it is not just for video and sound any more. The frustration stems from the lack of examples and explanations to use these powerful features for non-programmers. This book changes that. It explains clearly and wittily how to use QuickTime to enhance your website or CD-ROM, and take advantage of over 10 years of cutting-edge digital media technology for free.

[Full disclosure - I work for Apple on the QuickTime Engineering team, and know the author - believe me I wouldn't endorse this book if it wasn't great]

This book is a must have if you plan on working with QuickTime to make multimedia content available! I call this book 'a rare find', as it is great for beginner through master, leaving few questions unanswered or stones unturned. The text is a good mix of "how to" information combined with "tips and tricks" to get your implementations to work.

I purchased this book for its material regarding steaming content over the Internet, and learned a great deal in the process. The chapter on QuickTime VR answered my "how do they do that?" questions, and has led me to explore the use of this technique for my upcoming projects.

The QuickTime VR chapter is a good example of the depth of knowledge used to develop this text, as it gives in-depth information on photography techniques that only a mid- to experienced photographer would know.

My only criticism of the book is that it only begins to explore about half of the knowledge needed to set up your own streaming web server, but I can hardly fault the authors for that -- it says right on the cover "A Hands-On Guide for Webmasters, Site Designers, and HTML Authors." It says nothing about being aimed at System or Network Administrators. If your main interest in this book is the setup of streaming servers, you might want to consider another book (or better yet, purchase this book along with another to round out your knowledge).

With the ... QuickTime Pro included, I can say without reservation that this is one of the best computer book values I have ever purchased. The book paid for the rest of the cost by showing me how to trick Microsoft Internet Explorer / Windows Media Player in such a way that it will not try to open your .mov files (great in a Windows-dominated environment)!

Highly recommended, even if you have only a passing interest in QuickTime.

This is an important resource for anyone who is serious about maximizing the potential of Quicktime. At Rayhawk.com we have been using this book to enhance our web productions and the results have been noticable, not only to us, but to our clients (KFC, Taco Bell, BMW, Porsche).

The book is full of useful info and the author is fun and helpful. He assumes we have little prior knowledge with either QuickTime or HTML and by the end of the book, he teaches us how to produce some amazing content.

Mastering QuickTime is essential to quickly and easily building exciting, dymamic and interactive web sites. This book (QuickTime for the Web) is essential to mastering QuickTime for the web. It has saved me more time and energy than any book I've bought in the last two years.

This book is a must have! From how to create VR with interactive sounds and sprites - to getting your video or photos streaming on the web - this book shows you how. As a web master of a site with over 100 different Virtual Reality and QT movies, I found this book (and the free tools and interactive sprites for my use) to be invaluable. I reccommend it without hestitation. Luke Wonderly, Web master - vrbakersfield.com

When OS 9 Classic was retired, it forced a radical transition to reorganize and manage fonts without the ATM.

This book is the clearest and simplest guide for OSX users to understand how font functionality has altered in the OSX environment. Also vital to crossplatform users, the author Zardetto Aker simplifies the complex nature of sharing fonts between two platform radicals (Windows and APPLE).

Those who earn their living in computer design using real world situations would benefit from buying this book.

One analogy that describes it best:

Any graphic project is like the recipe for a perfect pot of "CHILI"
FONTS are the spices going into that pot.
If you don't manage the spice in your chili, like not managing the fonts in your project .... You wind up with disaster.

MUST READING ... Zardetto Akers' Font Management in OSX takes the confusion out of the font dynamics restructured on OSX.

I love my Mac, & I love typography. What I don't love is the mind-numbing complexity of OSX's font handling. Although I don't lament the passing of the ever-crashing OS9, it's framework for fonts was beautifully simple. There's a price for progress.

This book provides what's needed to understand the foundation concepts and terminology, and to deal confidently with common font issues. Thoroughly explained, it's made apparent that the font framework of OSX is not so incomprehensible after all. For any tech-savvy graphic artist or designer, an indispensable volume for your reference shelf.

What a splendid guide! Even if you are content to use TIMES ROMAN all the time, you should still look at this book to see a model of how to write a computer guide. None of the breezy self conscious humor you find in some books (the Dummy series or Scott Kelby's otherwise informative PhotoShop books). But friendlier and more attuned to the reader's anxieties and potential mistakes than the standard dry guides (e.g. the Missing Manuals series, which are not bad). Aker seems to sense exactly what you might need to know at just the right moment, but yet does not overwhelm you without a lot of detail all at once.

I recently switched from a PC (since 1980)to Mac, which is as everyone said so much more elegant, stable and better in almost every respect. But the font system is just as complicated and eccentric in OS X as in Windows XP. You need to do some housekeeping even if you are not a font maven. Follow the steps carefully laid out in Chapter 2 (rather tedious but precise), and your system will run more smoothly and you will know a lot about where your fonts are, and how to keep them behaving well.

I am almost never moved to write reviews here, and certainly not of computer books. But this is an exceptional contribution.

Face it - you'd think just putting your fonts in the FONT folder would be sufficient. But, strange things do happen. And, for me it is never at a good time. Like when you upgrade Adobe CS ... which made half my fonts DISAPPEAR.
Thanks for the info and instructions about AdobeFntXX.lst alone - made this book a must have in my library.
And, that was just one small enlightened moment Aker's offered

I do graphics and own Macs from October, 1985. I passed thru all the font technologies that were done into the computer... from enlarging 72pt bitmaps and correcting them, the early times of Adobe's ATM and so on.
But --maybe I'm getting old-- with the introduction of Mac OS X, typography went almost out of control for me. Althought I do not use per se Office I need to install it to open others files... and it destroy any organizated fonts folders that you had managed,
Then, in a desperate move, I bought Zardetto's book!
And everything came back to order: clear instructions lead me in a clever and consistent way. I confess I did it twice. First time I said myself: "I'm an old macintoshian..." But then I realized that following the step-by-step instructions was more inteligent. Then, with everything in order, I was back "in control".
So, my advice --for newbies and oldies-- follow the instructions and then personalize your fonts. OK, first buy and read the book!

Even though there is not a single line of code in this book, it is one that all people who are involved in the process of managing software development should read. In most cases, investment professionals will have an easier time understanding it than software developers will. The decision to invest organization resources in a software development project is treated as an investment and the point of the analysis is to determine if it is a sound one.
Part one starts with the fundamental concepts of how business decisions are made. Cash flow diagrams are used to illustrate how the flow of money relative to your organization can be visually modeled. Entire chapters are devoted to the various ways interest can be computed, the formulas used to compare the net worth of two different proposals and how to develop mutually exclusive alternatives. A large number of formulas are used, so if you are unfamiliar with the mathematics of finance, you will probably have a difficult time understanding them.
Parts two and three deal with how to make decisions in for-profit companies. Decision analysis, economic life, replacement decisions, salvage value, factoring in inflation/deflation, depreciation, cost accounting, and the impact of income taxes on business decisions are all examined using formulas, charts and diagrams. At times it gets very technical. To give you some idea, here are the titles of some sections:

*) Calculating after-tax cash-flow streams.
*) Inflation and after-tax cash-flow streams.
*) Gain or loss when selling or scrapping depreciable assets.
*) Comparing financing methods in after-tax cash-flow terms.

Part four deals with making decisions in government and nonprofit organizations. This is a very short section, less than twenty pages in length. Since these organizations generally cannot lose money either, the main focus is on the different ways government and nonprofit organizations finance their expenditures. Part five covers present economy, how to do break-even and optimization analysis. The primary focus is on how to perform various types of break-even analysis.
Part six examines estimation, risk and uncertainty. How to recognize and model the level of uncertainty and how to make decisions in situations with a great deal of uncertainty. This requires some knowledge of the fundamentals of probability and expectation. The last section covers the situation where there is more decision criteria than just the basic cost. This of course can be rather difficult, as it can enter the area of personal opinions. It is often due to the ordinal form of the data, where the range of assignments can be something like, {very poor, poor, average, good, very good}. While all can agree that poor comes before average, what one person will consider average, another would categorize as good. Fortunately, it is fairly easy to assign numeric values to the categories for standard numerical analysis of the data.
This is probably the hardest "computer" book I have ever read. I know a reasonable amount of financial mathematics, but it was still difficult to wade through all the equations, charts and diagrams. Despite this difficulty that you will most likely also face, I strongly encourage all managers to thoroughly study the contents. There is a set of self-study questions at the end of each section and solutions to most of them are included in an appendix. The software development industry has a (largely deserved) reputation for lax financial planning and the person who reads and comprehends the material in this book will have an enormous competitive advantage in the battle for jobs, revenue and profits.

Published in Journal of Object Technology reprinted with permission

Engineering is the practical and economical application of science in building products and services. So it puzzles me how financial aspects are so often neglected in teaching Software Engineering or Computer Science. What a big mistake! This is a skill that no Software Engineer should left unmastered. By the way - this is very useful even if you're not dealing with software and for your private life as it allows you to make informed decisions based on a sound rational. Steve Tockey writes in a very concisive and interesting way and provides several examples for each topic. I highly recommend it!

First, a confession, I know Steve Tockey. I work with Steve. That may bias my review a bit depending on how much I like Steve. One thing about Steve is that he home brews many nice beers and brings them into work where we get to share. I like Steve.
I also like his book. Now, I will admit that this is no thriller where you are excited to turn the next page (though I did get a little worked up on Analytical Hierarchical Process). It is designed to be an entry level economics text for the world of software engineering. The world of computer science and software engineering needed a book like this and didn't have one. So, Steve brewed this one up.
Part one (chapters 1-9) contain the basic economic theory you would find in most basic economic books. The topics are based around making decisions to make the most money (for profit companies) or to deliver the most benefit (non-profit). The text in these sections tends to get acronym heavy and Steve had to use the equation editor to type all the fancy mathematical formulas needed for things like interest for equal-payment-series capitol recovery. If you have had a basic economics course in college you can probably skip the first part without any pain. If you haven't or had forgotten (like me), then reading them is warranted. I found Steve's prose on this very dry subject to be reasonable.
Parts two through five carry on in the same way (chapters 10 - 20). Part two in decision making in for-profit companies and part three is advanced decision making in for-profit companies. Again, if you have concepts like Minimum Attractive Rate of Return, Cash-Flow Streams, Planning Horizons, Sunk Cost & Salvage, Inflation & Purchasing Power, Depreciation, Modified Accelerated Cost Recovery System, etc. then you can skip these sections. Same sort of story for part four, decisions in non-profit companies and part five, present economy.
BUT WAIT, there is part six! Estimation, risk, and uncertainty. Now here is a section that everybody should read, at least a couple of times. In my work and consulting, I find I am recommending to my clients that they read this section carefully. People building software seems to really miss these economic concepts. Steve does a very good job here in explaining how estimation, risk, and uncertainty work together (often against) on a work effort. He then provides several decision making strategies that work within the reality of uncertainty.
Part seven completes the teaching part with working with multiple-attribute decisions with a good discussion on number theory and how to rationally make comparisons. This is another section that I find most people don't understand too well and highly recommend that everybody reads this part.
There is a part eight but it is a summary and conclusion.
So, my bottom line is that some parts of the book are a must read. So parts are a could read. If you don't mind skimming the parts that you know or are not applicable for the current situation, this book should work out fine. It is also one of those books that you will actually pull off the shelf next time you are asked to lead the selection of a new Commercial Off The Self (COTS) system, choose between two competing project ideas, or just want to make a better personal finance decision.

How I was introduced to this book:
About nine months before this book was published I was researching the return on investment of software projects. While doing my research, I was introduced to Steve Tockey who asked if I might be interested in reviewing his book.

My background:
For almost 10 years I've worked in the software and consulting industry. Currently, I work at one of the leading CRM software companies worldwide where I spent three years advising customers on how they can get the most out of their investment in our software. At the time of my research, it was imperative that our division understood how software investments are impacted by certain business decisions and related financial considerations. Today, I am responsible for planning, implementing, and measuring the outcomes of investments and projects within our marketing organization.

Comments on the book:
This book does an excellent job covering the financial aspects of investing in software systems (or really any investment) as well as covering decision-making and risk management techniques. If your career path includes the development of any business case for software systems, this book explains many of the concepts you will have to use. While the introductory portions of the book explain how financial principles generally apply to software, the book goes far beyond an introduction - honestly, it's depth in content will give it a home on my bookshelf as a trusted reference for years to come. Besides clear explanations and good fundamental examples, the accompanying self-study questions, website, and tools will help readers truly understand and use what is being taught.

If you are familiar with Steve McConnell's books on software, you will not be disappointed with this one (as Steve Tockey works at Construx Software).

There are hundreds of books on topics relevant to various aspects of software engineering. However, when we analyze what went wrong with so many of our large practical software projects, one of the leading culprits is a misunderstanding of the business, economic and financial aspects of the projects. Where are the books and courses to help us with this major problem?
University engineering programs often have a course such as Fundamentals of Engineering Economy. What Steve Tockey has done with his book is to apply these general engineering economics topics specifically to the field of Software Engineering and set a standard for the subfield of Software Engineering Economics. His is not the first such book (see, e. g., Barry Boehm, Software Engineering Economics, Prentice Hall, 1981 or Leon Levy, Taming the Tiger - Software Engineering and Software Economics, Springer-Verlag, 1987) but it is the most thorough and up-to-date one that I know. It is an excellent book on a very important subject. Every professional software engineer, whether CTO, group manager or programmer in the trenches, will benefit considerably from reading this book.
Return on Software is divided into several major parts: general concepts of business decision-making, interest and the value of money, and cash flow streams; business decision-making at for-profit companies; decision-making at government and not-for-profit organizations; estimation, risk and uncertainty; and decision-making based on criteria other than money such as reliability, quality, speed, and other important features (strict economists might argue that all of these other criteria could be equivalenced to money considerations but I think considering these other criteria on their own seems more natural to me).
Judging from the topics listed above, Steve believes business decision-making to be the key ingredient of successful software engineering. I could not agree more. The crucial chapter in the book is #4: The Business Decision-Making Process. The key topics in this chapter include understanding the real problem, defining the selection criteria, identifying all reasonable technically feasible solutions, evaluating those proposals, selecting the preferred proposal, and monitoring its performance. The remainder of the book is an elucidation of those topics.
Each chapter closes with a summary and a set of self-study questions supporting the book to being used as a textbook. My university will offer a course around "Return on Software" in the spring quarter for our Master of Software Engineering students and I expect the course to be offered regularly. The last time I checked, Steve's company was not offering a short course on his book's topic but it would not surprise me to see one soon.
To prove that I am not from the publisher's marketing department, I would like to suggest that the next edition include at least two more topics: buy-or-build decision-making and outsourcing (whether offshore or not).

Without question, this is one of the most outstanding books covering SQL Server Administration I've ever owned. It is written simply with a minimum of word clutter. A majority of the topics are pertinent to SQL 2000 as well as SQL 7.0 (SQL 2000 is more or less SQL 7.5 in my eyes).

I recommend this book to any experienced DBA's out there who need a virtual DBA within arm's reach.

Postscript... I had the pleasure of meeting the author as a student in one of her SQL Server Performance Tuning classes. Sharon is outstanding.

I had the privelege of working as a consultant alongside Sharon on a SQL Server project in '93-'94, and she was an expert way back then. (I was writing the VB front-end, and new to SQL Server.) She taught me more in the first month I was there than I had ever learned in any job before. She is not only one of the smartest & nicest people I've ever met, she is also absolutely the best at explaining *why* certain things should or shouldn't be done. This is a must-have, must-read book.

Sharon Dooley does a fantastic job in the reference book. This book is the expert sitting in the chair next to you when you have a DBA task to do and you need help. If you're new to SQL Server, this guide isn't for you YET. Sharon Dooley covers the how, the why, and the when. She assumes you already know the what, so learn the "what", and then you'll LOVE this book for many crises to come.

-MCSD from the NW

This book helped me when I was moving databases from one machine to another and I had to fix some orphaned users. How many other books would even address this issue? None, I think. Most other SQL Server books seem to be outlines of BOL and little else. This author has obviously taken a different approach, that of a working DBA with problems to solve.

Ms. Dooley is among just a handful of people who can write about SQL Server at such an experience level. She shares her deep expertise and wisdom gained through hands-on use of SQL Server and real-world implementations. I also enjoyed generous warnings and tips which appeared throughout the book. They make the book fun to read and vividly illustrate technical points. As I read the book I kept thinking, "This is so useful and practical!" Ms. Dooley does an excellent job in presenting the information in a way that is best to learn and remember. Obviously, the author's experience as a prominent SQL Server trainer helped her to organize the book in such a great fashion.

I recommend this book to a wide range of SQL Server administrators and developers. The book covers SQL Server 7.0, has some mentions of SQL Server 2000, and also refers to older versions that may benefit users who have experience with prior releases. Developers, especially advanced ones, will also benefit from the best coverage of DMO I've seen in any resource.

I would recommend this book to anyone looking to learn good old C. And wow, look at how cheap it is! This book teaches EVERYTHING you will need to know. It even goes into a little C++ intro. But if I were you (or if I could go back) I would skip learning C all together - C++ makes C obsolete.

I love this book. Everything is made so clear and easy to understand even though the book moves at a fast pace and is very specific and thorough. If somebody told me they wanted to start learning C I'ld tell them to get a new revision of this book. The book features helpful does and don'ts that seem to read your mind and present to you the answers to your questions. 5/5 hands down. I'm going to add "Teach Yourself C++ in 21 days" to my shelf because I have strong faith in SAMS. Also don't be intimidated by C and buy a book that includes "beginner" in the title because they won't be advanced enough for any inteligent human. Buy thick books and read those.

This book gives you the very best learners guide and reference book I've ever seen.

This book has captured the perfect method to teach someone the C programming language. Many beginner books are very fluffy, others much to advanced. This book explains everything you need to know in a very simple, and extremely thorough manner. An excellect purchase.

This is the defunct standard for learning C in the quickest amount of time possible.

If you have any previous programming experience you'll find that you'll learn it even quicker. I read the book in 3 days and was already writing programs equivalent to what I was doing in Pascal only 3 days prior.

For anyone that tells you that you can't so solid code and script development on a Mac, they haven't been introduced to the application TextMate. There are several good options for doing power editing on the Macintosh and TextMate is one of those POWER options.

'TextMate: Power Editing for the Mac' by James Gray is a perfect companion manual for all TextMate users that want to lift the hood off of this power app and get to the nuts and bolts. If you develop on a Macintosh on a daily basis for work or fun and want to learn more about what you can do to make your life easier, pick up this book and you won't be disappointed. Written well and coming in at ~200 pages, there are 12 chapters which will teach you goodies in TextMate like how to create and use Macros, using Find & Replace to quickly edit text, and much, much more!!

The Mac is a great tool for developing code and TextMate is a great app for writing it, make yourself a more efficient coder today!!

***** HIGHLY RECOMMENDED

Visuals:
The font size in the Pragmatic Programmers books is a little larger than say the O'Reilly books, which I personally like. Easy on the eyes. Screenshots are clearly printed.

Readability:
I found the reading style conversational and easy to follow. Of course, with this type of book which includes many keyboard short-cuts you really need to be at your computer and using them to commit them to memory. Even a reading of the book will give you insights into the power available at your finger tips with Textmate.

Practicality:
If you spend any amount of time in Textmate, this is really a no-brainer. This book will help you be more productive and get more out of your chosen text editing tool.

Audience:
The book does not list an intended target audience, but if you use Textmate at all I would say you have a bulls-eye right on you.

Overall:
If you use Textmate get this book.

Books on editors are tricky things... I'm (still) a big fan and user of vi, but textmate is my tool of choice for more project level work for its capabilties. This book has brought me closer to to the keyboard level of productivity that vi allows for with its two modes.

"TextMate is actually a thin shell over a personalized team of robot ninjas ready to do your bidding."

The funny thing is, to people who have never used TextMate for more than a few minutes the above phrase sounds like an exaggeration. It's not. (As long as you can accept the analogy of "really awesome code running on a Mac" = "robot ninjas"...)

Anyway, this book targets a pretty specific market: 1) Humans, 2) who own Macs, 3) and use TextMate. I'm here to tell you that, if you're human you should have a Mac; and if you have a Mac you should buy TextMate; and if you have TextMate you should buy this book. So there, now it covers everyone.

As with all of the Pragmatic Programmer books, I found this book to be concise without missing anything important. You may be thinking, "200 pages about a text editor!? That's crazy talk!" But you would be wrong, my friend. The amount of functionality built into TextMate is incredible, but I didn't even know the half of it until I started reading this book!

I don't want to give away the ending, but:

Three of my favorite simple features I didn't know about until I read this book:
- Pressing [ESC] to complete the word you're typing.
- The built in TODO list functionality (so crucial!!)
- [Cmd-Enter] to add a new line below this one and go to the beginning of it.

Things I wouldn't have been able to do without TextMate and this book:
- Edit some of my Bundles to make TextMate work even more how *I* like
- Complete an after-hours Web Site project *way* under time and budget

Seriously. TextMate is the One True Editor for Mac (it makes me loath using any other editor on any platform) and this is a great book for learning how to *really* take hold of its power.

This book is the perfect primer for what I have found to be one of the most indispensible Mac OS X applications - TextMate. If you are a software developer or web designer or anyone else that edits text on a frequent basis and you have not already discovered TextMate, stop right now and visit http://www.macromates.com.

The Pragmatic Programmers' book, TextMate Power Editing for the Mac is a thorough introduction to TextMate. Edward Gray II has written a very accessible book, that covers the product very well.

The first third of the book is devoted to the basics - things you do every day in your text editor. The second third of the book dives into the details of some really sweet features of TextMate that you'll find yourself using all the time: bundles, snippets, macros and UNIX shell commands.

TextMate ships with over thirty 'bundles'. Each bundle is a directory of related files that provide additional functionality to TextMate. Let's say you're working on an HTML file. The HTML bundle will help you with loads of things related to your document: validate the syntax of the document, open the document in the default browser, refresh the document in the current browser session, insert open/close tags for the current word, strip all HTML tags from the document - just to name a few. Each bundle provides functionality that applies not only to the syntax of the language you're currently working with, but repetitive tasks that would apply as well.

As I mentioned, a couple dozen bundles ship with TextMate and many more are available for free download from various websites. You can even create your own bundles to extend the product in ways that only you can imagine. Here are a few of the bundles that ship with TextMate: Blogging, CSS, HTML, Java, Markdown, Objective-C, Python, Rails, Ruby, SQL, Subversion, Text, Textile, Xcode and XML. Bundles provide you with lots of help editing files and performing related tasks.

Snippets are a smart completion mechanism that go way beyond the simple concept of 'finish this word'. For example, if you are editing a Ruby file and you type array_object.ea followed by the TAB key (where 'array_object' is an arbitrary Array object), the snippet feature will automatically fill in the skeleton of the 'each' iterator, including the opening and closing curly braces, the text '|e|' with the letter 'e' highlighted. You simply type the name of the variable you want to represent the next element (or simply leave it as it is), hit the TAB key again and the cursor will be placed between the closing '|' character and the closing '}' character, ready for you to type in an expression. Very cool. This same trick works for dozens of different scenarios in your Ruby code. And that's just the snippets that apply to Ruby code. There are snippets that apply to a large number of file types.

You've probably seen macros in other editors and TextMate's macro facility works as you might expect: you start recording a macro, perform some actions and save the macro. TextMate saves the macros as XML files, so it's a snap to edit a macro after recording if you need to tweak it a bit.

The ability to fire off UNIX shell commands from within TextMate gives you another powerful tool to use while editing files. You can fire off one-liner shell commands by simply pressing the ^R key on a line containing a shell command. You can also use shell commands to act on all or part of the current document.

For the advanced TextMate user, the tail end of the book shows you how to create your own language syntax for use in TextMate, including how to describe the grammar of the language in terms TextMate will understand. So, if you program in some far out funky language that TextMate doesn't support out of the box, you can add the language grammar to TextMate and program away!

Overall, I found this book extremely useful and easy to read. TextMate ships with an excellent help system that will answer many of your questions. The TextMate Power Editing for the Mac book will take you beyond the built-in help and give you an in-depth guide for this great Mac application.

This is a handy little reference for a variety of time-saving tips and tricks. You'll definitely be able to economize your daily activities if you keep this book near you when building your reports and analyses. Don't be surprised if you dog-ear quite a few pages.

JR

An Excel User doesn't need to spend years in learning Excel, thus to get the most of it. An Excel User needs to know how to "kill the time" through Excel's Abilities. An Excel User just needs a book as "This isn't Excel it's Magic". It is a friendly Piece of Advise submitted in a gracious manner by the Excel Magician Bob Umlas,Microsoft Most Valuable Professional.This book will become "A Daily Excel Encyclopedia" to everyone who looks for Excel proficiency in job accomplishment.
A 21 century Excel User deserves this book. Do not miss Bob's Excel CLEVERNESS!!!
Pavlina

This book is full of quick hints that can save you time and frustration when working with Microsoft Excel. Many functions were identified that I never knew existed. This book is definitely worth the price. Enjoy!!!

What a handy little book chuck full of hints, tips and techniques by Bob Umlas. Bob Umlas is a Microsoft MVP and has held that honor since 1995 for his dedication to various online groups

The book is organized into 6 categorizing chapters: Features, Formulas, Keyboard Shortcuts, Printing, Miscellaneous, and VBA. It contains 142 pages with 84 tricks, tips and manipulative techniques, some of which are quite useful.

Some of the techniques covered are ones that you probably learned at some point but have forgotten. Others will be old tricks applied differently that will give you a new perspective. Plus there are many advanced features that are explained to stretch your skills. What impresses me the most is the practicality of what is presented in the book. The majority of the techniques are useful hints that can be put into practice rather easily.

This isn't Excel, It's Magic! is a fantastic book. I thought I knew a lot about Excel; but I now realize how little I did know. It is hard to pick a favorite because there are so many great head spinning, jaw dropping tips & tricks.

The book is well written with easy to follow examples. It makes unlocking the power of Excel an amazing experience. 85 great topics ranging from using advance filters to using vba bookmarks. A must have for beginning and expert users everywhere.

Thanks for a great time saving book, Mr. Umlas. You are a true magician!!

This book is amazing, I didn't expect a book on software engineering to be so easy to read and understand.

Most of the other software engineering books I read are too academic and detached from the industry.

The case studies provided in this book are things I can totally relate to as a software developer. Question/Answer sections are great.

Overall this book is very well written, it is a true masterpiece.

The knowledge I gleaned from this textbook was directly responsible for my getting a high paying software engineering job immediately after leaving college - that alone should be a testament to its value. It gives a wide reaching survey (yet certainly not lacking for details) of the latest cutting-edge methods for software engineering as well as the tried-and-true methods that have been in use for decades, while placing a primary emphasis on writing software that is trustworthy on time and within budget. In a software engineering world where ethics have fallen out of favor and the "almighty schedule" has become more important than quality and security, this textbook is an extremely refreshing view of how to apply modern principles and process to produce not merely programs but supportable, trustworthy programming systems products. And best of all, Bernstein shows you how to do it ON-TIME and WITHIN BUDGET by performing quantitative cost and time estimation prior to and during the development process. If software engineering is to reach the level of professionalism long associated with other engineering disciplines, we must all embrace the methods and principles discussed in Bernstein's book.

It's important to note also that there are many case studies in this book from Bernstein's distinguished career at Bell Labs, and they are extremely valuable in learning what "works" and what should be avoided. Software engineering as a discipline doesn't learn from its mistakes as well as other engineering fields, but this book takes 35 years of hard-earned experience and the latest research by Bernstein, Boehm, Parnas, and others, and condenses it into what I consider the best software engineering textbook on the market. This is a must-read for any computer science practitioner who wants to consider himself a true engineer and a professional.

This book does a great job of covering the key tools and techniques used in the development of software systems. It is very readable, and is suitable as a course text or an informative reference guide for practicing programmers and managers. A wealth of case study material provides insights into how to develop reliable software, on time and within budget. Sprinkled throughout are pragmatic rules of thumb and metrics. A good read and a good addition to any reference collection!

The most commendable single aspect of this book is the extensive set of real case studies. The main author (Bernstein) comes from decades in high tech industry and this permeates the entire book. The book is extremely broad in scope too, so the prospective reader or student gets a tour of a vast array of related subjects. The quantitative basis for the entire book constantly reminds the reader of the usefulness of a quantitative approach to all sorts of aspects of software engineering. Prospective buyers can dive in to the text at Amazon and make up their own mind about the usefulness for their own purposes. Take a look!

Well, this is certainly a much different type of software engineering textbook than I have seen in the last score of years ☺! I was a reviewer of early editions of Pressman, and a user of every edition since the second one at four different universities. Shooman's classic 20+ years ago is another early data point for a graduate course. The Software Engineering Lectures of Tom DeMarco and Ed Yourdon from 1979 are still shelved six feet away from me, and have been referenced in every undergrad and graduate software engineering related course I have taught since 1984. The same shelves contain Pfleeger, Leach, Lethbridge, Peters, Watts & Humphrey, Sommerville, Thayer and many others within the combined 12 foot lineal span. They obviously are used, but not to the extent of Pressman.

That may be about to be changed! Larry Bernstein's new text states on page 32 ".. none of these [principles of sound organizations] will work unless our profession recognizes the next core element in the evolution of software processes as a fundamental principle. Software trustworthiness is the next major area in which academic and industry must focus -- both for national security reasons as well as to ensure that the U.S. software industry maintains its leadership. The three attributes of software reliability, security and safety comprise trustworthiness."

I totally agree with the belief about where we should focus our attention in coming years, but not for the reasons that Larry cites. Let me explain:
* Having worked as a software/knowledge engineer on the Space Shuttle program for Rockwell International for four years, including the maiden flight of Discovery within a few months of my hire date in 1984, I am a very firm believer that the trustworthiness of the software in the shuttle and all the support effort was a gold standard at the time. I was also a full-time professor of CS concurrently, so could bring such issues to all of my classes. Although I have given up my dream of going to the moon, hatched when my small team of high school students fired off rockets in a farmer's field prior to Sputnik, I still hope to make it to the international space station, so a trustworthy system is not only of academic interest! In the last 20+ years, the ubiquity of computing, particularly embedded systems in all modes of transportation, makes such a standard a MUST, not just "nice to have" in our cars, trucks, planes, etc. When a team of Ford software engineers showed up in my office 10+ years ago, asking for help in developing safe software systems for next generation side impact sensors, I could not brush off their concerns! Obviously, software systems pervade the lives of many of the 6.6 billion people residing on this planet today, not just the billion or so who access the Internet. It is irresponsible, not to mention a direct violation of codes of ethics for computing and software engineering, NOT to develop such trustworthy systems.
* I cannot agree with Larry's rationale about the leadership of the U.S. in software. Trustworthiness of software systems knows no national boundaries! Other engineering artifacts do not know such artificial boundaries - do we want the bridges and high rise buildings of Europe, Asia, the Middle East, South America, Africa, etc. to be less safe, reliable and secure than those in the United States? I think not, if for not other reason than millions of our citizens travel to and live in those countries every day. Clearly, the lives of people across the world are just as valuable as those fortunate enough to live in our 50 states. The state-of-the-art in engineering methods is being advanced on a world-wide basis - why should we think software engineering education is somehow an exception? I would hope that this new text would be published in many languages and used by students and practitioners worldwide. I had first met Professor Bernstein on November 30, 2000 during my sabbatical to set up an International Software Engineering University Consortium (www.iseuc.org). So Larry clearly knows of my penchant for the world-wide importance of software engineering ☺!

Why do I think this new text is different from earlier ones and would recommend strongly that all current faculty and practitioners consider it carefully, especially for an introduction? The rationale includes the following. The text:
1. Focuses on the increasingly vital role that trustworthy software systems will play in the lives of current and future generations. Consequently, it is quite easy to engage or "hook" students in an introductory software engineering course about the importance of the topic - they see the impact of the lack of such systems on a weekly, if not daily, basis. Many of them will be able to share personal and professional experiences. The marvelous column by Neumann in every copy of ACM's SIGSOFT Software Engineering News provides ample examples, in any case.
2. Is cleverly written with excellent and realistic case studies with real questions and answers
3. Draws on the demonstrated expertise of the primary author when he was the CTO for Bell Labs
4. Truly demonstrates the rationale for the role of quantitative software engineering methods throughout the development life-cycle, beginning on page 4!
Reliabilty = e-k?t, where k is a normalizing constant, ? is complexity/(effectiveness x
staffing) and t is the time the software executes from its launch.
5. Emphasizes the "why" as well as the "how"
6. Includes excerpts from student teams related to the growing use of Real Projects for Real Client Courses - RPRCC-in software engineering and other courses
7. Covers most of the topics in a traditionally-structured software engineering text, but does so in a more contemporary and intuitive way. Some of the topics in other texts that wind up at the end, hence often not covered, are main-line chapters in the Bernstein text*. The newest edition of Sommerville's text does indeed have a 20-page chapter 3 on "Critical Systems" and a complete 120 page Part 4 on the same topic, but this is certainly an anomaly among current texts. The Bernstein text emphasizes trustworthiness as a continuing theme throughout, with the continual use of quantitative measures - witness the large number of "Magic Number" boxes for empirical results and heuristics contained in virtually each chapter. I admit that there would be a "learning curve" for most of us, but hey, aren't we supposed to be paragons for "life-long learning" that we espouse for our students?
8. Has fewer pages than virtually every other text. This is a real advantage. Students (and faculty) feel they have a "prayer" of being able to use the material in one course!
9. Has nice on-line support site.
10. And, finally, Larry will go to great personal lengths to support his text ☺!

A couple of possible sources of improvement for the second edition would include the following:
1. Include Failure Mode Effect Analysis (FMEA) as a major component when designing critical systems. This is a common engineering tool that was used in the design and testing of the Space Shuttle Main Engines (SSME) over the last 30 years.
2. How can the vital concept covered in the text be applied to the massive task of rendering trustworthy the extant base of millions of software systems? The text does a superb job for developing such systems, but can trustworthiness be "bolted on" existing systems? I doubt it, but cannot see an easy answer here.
3. A friendlier website for both instructors and students would be helpful, ala those for other software engineering textbooks

*Topics in the text
Part I. Getting Started
1. Think Like an Engineer - Especially for Software
2. People, Product, Process, Project - The Big Four

Part II. Ethics and Professionalism
3. Software Requirements
4. Prototyping
5. Architecture
6. Estimation, Planning, and Investment
7. Design for Trustworthiness

Part III. Taking the Measure of the System
8. Identifying and Managing Risk
9. Human Factors in Software Engineering
10. Implementation Details
11. Testing and Configuration Management
12. The Final Project: By Students, For Students