No comments about C# Concisely.

5 comments about Programming Python, Second Edition with CD.

1. I bought this book a few years ago, and I think I have finally given up getting anything of use out of it. It has been with me through my entire Python learning experience, so you might think there would be a point at which I would have found it useful, even if that may not presently be the case. Unfortunately, I can say that this is easily the least useful Python book I own. In fact, out of the 6 or so Python books I own, it is the only one I wouldn't miss a bit.
   
   It's just that it never seems to have anything even close to relevant for me, when I'm working on something. I can remember several times where I thought to myself, "What's a good way to solve this problem in Python?", or, "Where can I get some background on why Python does things this way?". Invariably I have either found the answer in one of my other Python books, or on the web. It's not that I haven't tried to like the book, in fact each time a problem comes up, I think "well ok if the book can shed some light on this for me, I'll consider it a value", and yet after 3 years... nothing.
   
   Anyway, I don't want to be all negativity, so to anybody reading this, here are the other Python books I have gotten more value out of:
   
   The Quick Python Book by Harms/McDonald (Old, and yet, still really valuable beginning book)
   Python Essential Reference by Beazley (A great reference book)
   Python Cookbook by Martelli et al (what Programming Python seems like it wants to be, but in half the size and twice the value)
   Python Standard Library (I don't use this much, but it still has some value)
   Python in a Nutshell (I think that's the name, it's at work right now. Another decent reference)
   
   Finally, it pretty much goes without saying, but I'll say it anyway. This is just my experience. I am sure this book has been right on the money for other readers, and that's great, but for me, I think I may be donating this behemoth to my local library soon.



2. One thing I really wish O'Reilly would have made clear on the cover is the version of Python which was current at the time of publication. In this case, it's 2.4, so if you're looking for information on things like function decorators or the new generator abilities that 2.5 brought along, you're going to be as disappointed as I was.
   
   Aside from the fact that some of the information is dated, it's still a good overview of practical solutions to realistic problems which can be solved in the language. It does tend to spend way too much time developing TkInter GUIs (which I do not personally care about one bit) and overusing the usual array of extremely unfunny Monty Python references (which I personally stopped caring about around 1984). If you cut out both of these things the book would probably require about half as much paper per copy, and it'd be a good deal more digestible to boot. There's also lots of Windows-specific silliness and the author continues to operate under the assumption that OS X does not exist (every mention of the Mac platform refers to information that hasn't been accurate for nearly 10 years at this point).



3. This is not a terrible book, but I don't know what it's good for. The code examples are too long. This reminds me of the old programming tomes from the days before CD-ROMs and the Internet, where all details had to be shown in print. There is just too much code. If you find a chapter that matches exactly what you are trying to accomplish, then maybe this book is good for you. It is vastly improved in readability over the first edition, but The Python Cookbook is a much smarter purchase (even though part of that is available online).
   
   If you are just trying to learn Python, then Lutz's other book, Learning Python, is an excellent choice.



4. Whenever I try to look something up about Python with this book, I end up using Google. this book is *horrible*. Lutz must be the ultimate geek nerd.
   Instead of things in the table of contents like "strings", "regular expressions", "maps" - you have "Here's Looking at You, Kid!" or "Roses are red, violets are blue". Does this guy put flowers in his hair and dance barefoot in a park?
   Instead of short examples, he starts writing a program; you have to study it and keep reading in order to keep up. A total disrespect for one's time.
   The topics he presents are obscure, unnecessary, or have no consistent audience: What's OOP?; moving stacks to C modules; and endless discussion about GUIs.
   This book has 1 readeeming quality: FIREWOOD.



5. Very big, not always very useful. I find in this book a brevity of many things that deserve more space and too much space allocated to many things. The book has an intro section on Stepping up to OOP; looks promising but then immediately leads you down the track of adding persistence and on to using OOP for GUIs. To me, this is not a well thought out approach. Think the reader would have been better served with an overview of OOP in use in Python, expanding the concept generically to OOP and then referring to some specialized instance of where OOP either comes in real handy or is a must. Part III GUI Programming is pretty much a mess. Granted I think it is a good idea to have a basic idea of Tkinter - but there is more out there that I would rather read about. I also think a book of this size should have some inclusion of Agile Development concepts, a section on Refactoring, etc. With all the subjects, just about any framework or methodology would be a prudent interlude to help congeal the sprawl of information. I am also a little biased toward scientific programming, but think many readers would appreciate an intro to numpy, pytables, or at least a simple primer on array manipulation and how it can extend the basic functionality of python and take it to a new level. I find, more often than not, that I have reached for this book and then gone back to something that is supposedly marketed as "more basic" like Learning Python or the Python Cookbook and get more what I am looking for there. Come on, something like XML processing deserves more than 3 pages of reference and if you are decked out at over 1500 pages it just seems like the book's priorities are amiss.

2 comments about C#Builder Kick Start.

1. "C# Builder Kick Start" is not just an intro to the subject, but the standard text that no one should be without. I was attracted to this author because of his previous great book entitled "C# Unleashed". If you desire the power and quick development of C# Builder, then this is THE book to take you by the hand and lead you into tremendous productivity. I highly recommend it!
   Going through this book carefully, you will not only learn, but you will "own" the technologies of C#, the .NET platform and C# Builder. I appreciate the foundational concepts that are established and then built upon step by step. The following subjects are comfortably dealt with; basic and advanced C#, ASP.NET, ADO.NET, Debugging, Forms, Security, Events, Web Services, XML, with many others.
   The code samples are thought out and well written so that you will probably use them with your own projects. I can't imagine a book better written, more concise or able to make you more productive. Kudos once again to author Joe Mayo!



2. Recommended Reading

   After having taken the time to learn C# and create the first .NET training offerings for Borland in 2003, I relied heavily upon both the Microsoft documentation as well as hefty tomes like Jason Price's "Mastering Visual C# .NET". For this reason, when Joe first contacted me and asked me to read his book, I was skeptical. After reading it however, I feel that it is one of the better books on using C#, let alone Borland's C# Builder. I found the coverage of WinForms, Web Forms, ASP.NET, and even related security concerns to encompass material that I had to painstakingly dig up from over six (6) other sources when I first learned .NET.

   Book Overview: After the required orientation to .NET and C# Builder, Joe begins his book with an easy to understand explanation of .NET that anyone not already familiar with the language should enjoy. His propensity to clearly segregate topics that he considers to be "beginner" or "intermediate" is encouraging. (The segregation is a good way to help people avoid being intimidated by more complex topics, or to concentrate on the basics that they might first need to build some experience in before tackling more advanced topics. Nice job!)

   I found the evolutionary style of subject presentation to be very good as well. By beginning to delve into areas such as how to use the command-line compiler, as well as how to configure C# Builder, the first time C# Developer will defiantly be able to find some morale boosting victories early on in this read. If you are new to C# but have some other programming experience, then I recommend working the example as you encounter them, and then playing with them to make them into something more. This approach will yield some excellent surprises when you return to the book to see what Joe is cooking up next.

   In general I found the presentation to be reminiscent of the training that I created for Borland with some pleasant surprises. For example, while errors with the initial release of ADO.NET prevented us from covering too much Borland-specific database know-how in Borland's first training release, Joe's coverage of Borland's support for ADO.NET arrived after the bugs had been squashed. Like Borland's training, Joe's book is up to date with the latest practices.

   I believe that this book stands a good deal higher that the rest of the C# training pack at the moment. Moreover, being that the trail to creating a book such as this one is never an easy one to brave for a 1.x product release, I can easily round my initial 4.5 stars up to the amazon-supported 5. I appreciate the work that Joe had to put into this book!

   In short, if you are going to brave the new .NET world using Borland's tools, then I recommend buying this book.

   Randall Nagy
   President, Soft9000.com
   (Former Principal Trainer for Borland Software Corporation)

4 comments about Component Based Development With Visual C#.

1. Highly recommended for serious software developers.
   One of the best books I have read.
   Part one is almost biblical to software development process.
   This is not just for .NET, the same principles are applicable to Java or Windows developments.
   I have good understanding on VC++6.0, but facing VS.NET I feel daunted.
   My experiences with the Windows system, MFC class lib and VisualStudio are not much useful.
   This book helps a lot. .NET is very rich and deep, so you should not expect
   realizing .NET with a signle book. Yet this book is a must on your reading list.



2. After trying numerous .Net books I found that this one was extremely helpful in getting to know the most important parts of the .Net framework. The book covers a lot of ground, since anything can be a 'component'. The discussion is split into front end, middle tier and back end components. So the scope is big. This book assumes you know .Net, and have played with VS.Net, so don't expect an introductory level text. I think the author does a great job of picking out the most important parts of the .Net framework and demonstrating their practical use in short but useful examples.

   I have been disappointed at numerous books that spend ages covering the same ground like introduction to .Net and using windows or web controls, leaving meatier issues untouched. In contrast, Faison treads quickly, and clearly, through major topics in .Net such as (not in order): using windows & web controls, user windows & web controls, Crystal reports, database access & data grids, session management in ASP, security, web services, and so on. Many other areas of the framework are covered in passing; for example a handy section on using the web browser control in .Net.

   The discussion of UML in the beginning is a bit fast, particularly the terse presentation of numerous design patterns, but the author's use of UML sequence diagrams through the book is excellent.

   My main criticism is that the author tries a bit hard at humor with the quotes before each chapter. Otherwise, it's a great book.




3. This is a comprehensive book on component-based development (with C#). It's ~1000 pages thick and packed with code and developer information that is well referenced. A bit short on component "packaging" frameworks. This book also complements well Groove development(GDK with .NET)...



4. I absolutely enjoyed reading the book. This is a book that covers some very advanced topics in a way that it seems so easy to comprehend. I liked the way author uses examples and explains not only the technology but the use of the development tools as well. This is just one the best technical books that I have ever read.

5 comments about Learn to Program with C++.

1. With all the reviews I expected a great book to start programming with. However, after reading the first 50 pages I have learned not one single thing about Programming but I have learned A LOT about the students in his class. This book is a total drag and a big waste of time. It never gets to the point! I returned it and you'll probably do the same. I dont see why everyone is reviewing this book to be so great.



2. Let me begin by saying that I'm the author, so let's get that out of the way.

   I'm posting here to point out that the book has a tremendous amount of support materials that have never been advertised. Each of my books has a support page containing a current list of errata, downloadable files (completed exercises from the book), extra links to extra materials I have written and my email address in the event you have problems. I also run a series of online classes so that if you would like to learn with me in a more structured setting, you can do that also. You can access those materials via this link

   http://www.johnsmiley.com/books.htm

   I should also say that this book isn't for everyone---and you can read through some of the other reviews posted here to see why and why not.

   I wrote this book for beginner level programmers, and the book is written in a unique style.

   You (and I) can thank the now defunct Wrox Publishing house for the style of the book that some people absolutely love and others (primarily hotshot programmers with lots of experience) hate. The book is written as if you are participating in an actual classroom---many people, particularly those learning on their own or in an Independent study setting find comforting.

   My thanks to the many people who have written to me to tell me how much they've enjoyed my books and how they have helped them achieve their goals of learning to program.

   John Smiley




3. This book is simply put, a good base for learning C++, however, you won't walk away from it knowing enough info to start programming.
   
   First, what is good about the book. The book is truly for beginners, and John Smiley has a way with explaining concepts. The book gives a great base for C++ and object oriented programming. The classroom format works well, and all in all it's a great book.
   
   Now for the bad. The thing that was a major dissapointment is that after reading the book, you really don't have enough knowledge to build your own programs. I mean I wasn't expecting to be programming Xbox games, however, I can do hardly anything. This is due to the fact that rather than teaching new coding techniques (building a graphical user interface would of been great), he simply shows better ways of using the same code. This is why I say it is a great base, it shows you a lot of the important concepts in C++, however, it fails to deliver a lot of usefull code.
   
   Another problem is that it tends to go too deep into explanations sometimes. It's great that he explains things, but sometimes he just goes too far. Another problem I had was the choice of topics, like he went into some things that seemed like advaced topics(inheritence for one), and while they may be usefull in the long run, they seem like something a "beginner" would have no need for. Some info on building GUI's would have been a nice replacement, something people will use right away, unlike inheritence which would take time to find uses for. Another thing I didn't like was the huge intro to the Systems Development Life Cycle. It is good to know, but this is a beginner's book, no one will read this book and then do projects that would have any use for the Life Cycle. It seems that the author can't decide if he really wants this to be a beginners book. At times it seems as though this is an introduction to object oriented programming (using C++ as a model language), as opposed to a book on C++
   
   So, what I recommend is to buy this book, as you will learn lots about object oriented programming and the basics of C++, but then immediately buy a more technical book with lots of content, take a course, etc. Just don't read this book and expect to be able to write (even simple) C++ programs, and if you do, they will just be little Command Prompt Programs. (not a whole lot you can do in it)
   
   Now that I want to learn Java, I've decided not to get John Smiley's JAVA book. I'm getting Sam's Java 2 book. It's simply that it looks like Sam's has way more content, and since C++ is similar to Java, I know all the basics of object oriented programming from this book, as well as the main coding techniques, therefor I don't need a book with John Smiley's great explanations and would rather go for a book with lots of content.



4. I can't compare Learn To Program with C++ to any other C++ books, because this is the only one I have read so far. All in all, unfortunately, the book has turned out to be a failure. I simply didn't get out of the book what I wanted: an elementary introduction to the language.
   
   At times, it seemed the author was using phrases that he had never used before, as if he had explained them before at some point. Bizarre, yes. He made the assumption that some of his terminology was either very simple to pick up on, or was already covered. It wasn't simple or already covered.
   
   Also, perhaps equally bothersome, the author talks too much about the students in his fictitous class. Make note that there actually no classroom with the students he is always talking about. What is probably most bothersome is that he often repeats the same things over such as "I waited to see if anyone else had a question." He is the one writing the book, of course he knows if one of his characters is going to ask a question or not! Remarkable. The interaction between him and his students may upset some people just because there are no actual students.
   
   As far as the book being easy to read, well, the introduction is, but you may get lost after that. I did. It is possible that C++ is to blame, or may be it is how the author presents the language.



5. Professor Smiley writes books (and teaches courses) which are designed to bridge the gap between the layperson and the professional (degreed) programmer. I orginally read (and used) his LTP for Visual Basic, and was able to parlay the knowledge he provided into a management position at a top F500 company.
   
   Now, I had a lot of previous knowledge of databases and excel to go along with what the course provided, but the book(s) provide a great resource for any level of anyone desiring technical programming knowledge, I'm so impressed with the way Prof Smiley personalizes what can be a very difficult and abstract subject that I plan on taking more in-depth classes from him.
   
   Best Regards,
   
   Jim

No comments about Professional K2 [blackpearl].

2 comments about Pro Visual C++ 2005 for C# Developers (Pro).

1. If you are a C# programmer interested in C++/CLI, look no further. I felt like the book was specially written for me :-)
   It is written in a very clear and pragmatic manner. I am glad that the author kept the book short so that you can read through all the main points and explore further on your own. Excellent book.



2. Swimming upstream is never easy.
   
   Learning C++ if your primary language is (and has always been) C# is exactly like swimming upstream: C# is, in a sense, a much simplified version of C++. So, you're going to have to learn how to do easy things a harder way.
   
   One (traditional) way of learning C++ is to grab a good book and kinda learn a new language. But it might take a while to figure out how to apply the programming knowledge you already have to the language which is new for you.
   
   This book makes the process of adjusting your existing C# knowledge to be able to do the same things in C++, far less painful and time-consuming.
   
   The book starts with a brief overview of the main differences between C# and C++/CLI (C++ 2005) syntax, and shows how to convert a simple (but not as simple as "Hello world"!..) console application from C# to C++. The subsequent chapters dig deeper into more advanced stuff you need to know about C++/CLI.
   
   By the way, the author is one of the world's leading experts in C++.
   I don't know if he has ever taught any classes, but the fact is, this book is unbelievably easy to read.
   
   Also, unlike many other books on programming, this book does NOT bore you to death by a 100-pages introduction and history of the language. A few pages of introduction... and you're already starting up your Visual Studio!
   
   I highly recommend this book.
   
   I only wish it was twice as big...

5 comments about C# Programmer's Cookbook (Pro Developer).

1. I too feel compelled to disagree with the 'Bad Review' that dismissed this book as being for beginners and just a repeat of the MSDN material.

   I've been using .NET C# for years and I am not not a beginner to OO and have been a professional programmer for more than 20 years. I've spent many hours in the MSDN help files and searching the internet for esoteric answers. This book contains many succinct solutions to everyday problems. It's not supposed to be a `big picture' book or only focus on the esoteric. Sure, some of the recipes do qualify for trivial.
   
   Before I bought it I was able to scan the table of contents and see solutions to tricky problems that I had solved and many others that I had interest in or could reasonably see needing. By scanning the solutions I was familiar with, such as cryptography, threading, and networking, it was clear the authors had a clear understanding of the problems and were able to boil it down to real solutions for real problems. While MSDN does contain many good examples, many times it misses the mark when it comes down to relevancy for solving a real problem.

   If you are like me, and want solutions at your finger tips, and are willing to pay a little to save a lot of time, this book is a great tool to have available.




2. This book remains at my fingertips at all times. It's perfect as a reference for those little problems which we, as programmers, face every day.

   Some examples of problems which the book covers are:
   - Prevent People from Decompiling Your Code
   - Sort an Array or an ArrayList
   - Store a Serializable Object to a File
   - Instantiate an Object Using Reflection
   - Synchronize the Execution of Multiple Threads
   - Use XML Serialization with Custom Objects
   - Apply Windows XP Control Styles
   - Reuse Data with the ASP.NET Cache
   - Show a Dynamic Print Preview
   - Calculate the Size of a Directory
   - Download a File over HTTP
   - Communicate Using TCP
   - Host a Remote Object in IIS
   - Restrict Which Users Can Execute Your Code
   - Create a Cryptographically Random Number
   - Use an ActiveX Control in a .NET Client
   - Create a Windows Service

   This is only about 5% of what the book offers. If you've ever wondered how to do any of the above or have ever needed to reference a short snippet of code for any of the above then this book is for you. The code snippets are all full complete programs so there's no confusion as to what references were used.




3. this book follows a "problem/solution/code" format that really helps to cut down the amount of fluff you always get in other books. it covers a wide range of subjects (including "beginner" topics) but in a very efficient way. even though all these topics could be dug up thru web searches, the quality of info here is far more consistent and reliable. i hope to see more books take this approach.



4. Context: I've been developing software for 12 years (C++, Java, JavaScript, PERL and more). I've been using .Net (VB) for 2 years and C# for about 1 year.
   
   Another guy I know from work bought this book. He seemed to like it because of the short descriptions for each of the recipes.
   That is exactly why I don't like the book.
   
   Okay, short descriptions would be okay, except many of them don't even provide example code or completely explain the solution.
   
   I'm looking at recipe "1.14. Manage the Global Assembly Cache" right now and there is nothing about the winnt\assembly directory in there. Why not? Instead the author only explains gacutil /i and /u. Okay, but what does that do? How is it significant? Why do I want or not want my assembly in the gac?
   
   Recipe "1.8. Create and Manage Strong-Named Key Pairs" is the same thing. He tells me how to use the sn.exe tool, but he does not tell me anything more about why or how. Very weak.
   
   But the ones that really kill me are the ones where the author has a chance to really describe the thing using a code example, but then fails to do so.
   
   For example, "Recipe 1.4. Create and Use a Code Library" begs to have some sample code, but none is provided.
   
   "1.3 Create and use a code module" was the same thing.
   
   The section titles promise so much, the text delivers so little.



5. If you need to know how to do one of the items contained in this book it is an excellent source. Some of the examples were overly simple, but others were very insightful.

No comments about Learn C# Now Toolkit (Step By Step).

2 comments about C# Programming Interview Questions, Answers, and Explanations: Programming C# Certification Review.

1. Indeed, this book is not for everyone. If you have all of the time in the world, you should probably search the internet. Here are some reasons
   why this book is for you.
   
   1. This book has information you can use right now.
   It has code snippets and detailed information.
   This book is an answer to your need for instant information.
   
   2. This book was written and edited by an IT practitioner
   and expert author who has 15 years of varied and vast experiences
   in the world of information technology.
   
   3. Rather than being a textbook-sized or voluminous
   reference guide, C# Interview Questions includes only
   the information that can be used immediately by the reader
   in their job search or IT career. In this regard, this
   book is relatively short. Rather than providing more information,
   this book focuses on providing the right information.
   
   
   4. C# Interview Questions can also be thought of as a
   "cook book" in the traditional sense in that it provides
   the reader information in a very concise and useable manner,
   not unlike a recipe. In this way it should serve you
   by saving you time - by helping you understand what
   is important, and what you can safely ignore.
   
   
   5. For instance, you might find this book particularly useful
   for gaining knowledge and understanding of a completely
   unfamiliar area of programming - C#.
   
   6. By skimming the table of contents and index, you may quickly understand the most important aspects of a particular area, and
   also have access to the accumulated knowledge of the author. It is the unique "Question and Answer"
   nature of this book that makes it so valuable.
   
   7. It can be said that, "If you can't find the right answers,
   maybe you're not asking the right questions..." This book not only helps the reader understand the answers, by providing explanations
   where applicable but also provides the right questions. This book
   also includes code listings and command references which sets it
   apart - and keeps it close at hand at work rather than collecting
   dust on the shelf.
   
   
   8. Finally, this book is published with several goals in mind which
   I believe sets it apart from other sources of information. Its
   mission is to provide the reader with timely, useful information
   that will increase your technical literacy, increase the
   awareness of careers in information technology, and challenge
   readers to question the status quo.
   
   
   I know that this book offers a great deal of value to our readers - I hope you find it as useful as I do.



2. I expected to receive a book in interview question format. The format was like "I did this" then it would give some code or the questions sounded more like a test question and the explanations were lacking. It might be better for people needing certification, but I was looking to get some insight into actual interview questions. If that is what you are wanting, please don't bother wasting your time and money on this item. In addition, the book is really NOT worth the money. There are a lot of books out there that are high quality, with much more information and costs slightly less. I was very disappointed.