Customer Reviews

Simple Program Design

5 star:		(6)
4 star:		(7)
3 star:		(2)
2 star:		(2)
1 star:		(0)

 

 

This is the best book I have found about learning how to program. I have read lots of books about specific programming languages but I never felt like I understood how to program until I read this book.

This book is great because it explains the fundamentals of programming in a way that makes it easy to learn any other language. If a person wants to learn to program they should get a reference for whatever language they intend to program in such as one of the O' Reilly or WROX books on Visual Basic or Java and a copy of this book.

I have been doing a lot of database related programming and I found that the way this book explains program design helps in database oriented applications as much as it does in desktop VB or Java applications.

This book is good in that it explains in simple terms what designing programs is about. Design tools such as pseudocode, Nassi-Schneiderman diagrams, flowcharts, etc. which is good for the procedural way of thinking. Only two chapters that teaches the reader about object-oriented. As such, this book will help the reader more in the traditional approach of problem solving than the object-oriented way. I do not see two chapters as providing a solid, practical grounding for developing object-oriented solutions. Furthermore, there are no "Suggested solutions to selected questions". While it is true that there are different ways to solve a problem or expressing the solution, providing some "Suggested solutions" may, in effect be also providing further understanding if the solutions points out possible pitfalls or aspects which the student may overlook and thus produce something that isn't quite correct.

I think the book is not good at covering desk-checking. It is constructed in such a way that allows the checker to make mistake as to which step is under consideration or inspection. The first column of the desk-check table (or dry-run table) is labelled as "Statement" and under this column, "Read", "If", "Print", etc. appears. It would be better to number the lines in pseudocode (which can easily be done) and label the 1st column of the table as "Step No." so as to allow easy, and less error-prone cross-checking.

The other area that can be improved is "Appendix 3: Special Algorithms". It attempts to explain Bubble Sort, Insertion Sort and Selection Sort without using examples. Unsorted arrays with numbers and diagrams to show the swaps in the passes would be useful. This is done in many programming and algorithm design books. It is a pity that it is not done here. It would certainly support the textual explanation.

With this minor blemishes, it is still a very good book to teach people who do not know programming to get a good feel of how to think to solve programming problems in a computer language independent way. The teacher is the key to making this book useful as a concise text to the topic of program design. For example, the teacher can show a example of improper identation in pseudocode which may not be obvious to the beginner and explain why it is incorrect the consequences of it. Things like an "else" belongs to the nearest "if" should be highlighted. The book does not show an example, it merely states that it is important to indent pseudocode properly.

Overall, it is still a good text.

The problem with most books that purport to teach how to program, is that they really only teach the syntax of the programming language their book is about.

If you have never programmed before, you must FIRST learn how to think like a programmer before delving into the intricacies of a particular programming language. This is where this book excels. This books starts you out on the right footing and gently leads you to develop the proper frame of mind and method to become a programmer. Once you master how to think like a programmer, then you are ready to learn ANY procedural programming language.

If you rush into programming, you could develop bad habits that are almost impossible to break. A little patience now, and the road ahead will be much easier.

This was a requirement to read in my CS1 class before we ever stepped foot into a C++ book. Now several classes later I can understand the importance of the good algorithm design that this book enforces. This book required no experience in programming what so ever. Those with experience may find it a little boring to read but may also find themselves referring back for examples.

While taking a required course in college, I found myself at an impasse with the school's textebook for this class. While talking with my Academic Advisor, he gave me the title of this book to try to explain what was being said in a more technical language without a breakdown. I will be recommending this textbook to my next programming Professor as a supplemental text for our class. There are people that do not have much programming background in this class and could use a clear concise text that will help them understand the basics of programming. This book breaks it down in a logical order instead of being all over the map like the required textbook.

If you are looking for a good text to help you clarify information in another programming textbook then this is the book that is a must to help anyone from the beginning tech to the advanced learner. This text is a definite must even for the casual programmer.

I used this book in an introductory programming class shortly after it was published. It provided the most "bang for the buck." It covers the basics of programming in a thorough manner, providing coverage of basic control sturctures and arrays. I highly recommend this book. Its value lies in the fact that it can be adapted to any programming language, since the topics covered are germain and found in all programming languages. It is an excellent introduction to programming and computer languages. Master the topics covered here, and you will have a handle to program in any computer programming language.

This book clearly explains the steps in designing programs and provides language for the reader to understand programmers jargond. One thing to remember that the text does not "drive home" is the need to initialize variables. This is a vital part of pseudo programming because it translates into nearly every programming language used today. Good book if you can remember that initialization is key to programming.

Ms Robertson's book is an excellent first text in program design problem solving. It offers easily understood techniques, in an almost cookbook fashion, to employ in analyzing and designing a program. Taking you from the basic steps to designing a simple program to modular construction in larger programs, the text guides the student step by step to success. On the negative side, while there is mention of object oriented programming in the text, very little is developed in this area. I would truly like to see a modest improvement of the text in this area. A step by step approach to object development and interaction in program design is sorely needed. In addition, while pseudocode is thoroughly explored as a valuable tool in program design, and N-S diagrams are addressed in a supplemental section, little is addressed vis-a-vis flow charts. All-in-all, however, this book's value far exceeds its modest price.

For half the price listed in my school bookstore, this was a good, cheap alternative.

I bought it used, so I knew what I was paying for, but I wasn't at all disappointed. In some places, the writing actually gave nice hints for the problems. Your mileage will probably vary however.

Reviews about the item itself aside now, the book is actually rather useless.
It seeks to standardize your use of pseudocode, and make it a formal language which, let's face it, defeats the purpose of pseudocode.

You remember all that dumb prewriting stuff your 7th grade english teacher made you do? You know, those dumb webcharts, outlines, and tables? This book has all that stuff, but tailored for programming.

Save yourself the money, and don't buy this if you don't need it.
This is one book I don't plan on keeping at the end of this quarter.

I highly recommend you do not read this book if you want to keep any of your sanity. One of the worst textbooks I have ever had. The examples in the book have LOTS of missing pieces and just take wild assumptions. It's hard to tell what the author is trying to get you to program and what to get you to not program. The concepts and ideas are there and easy to understand, but when you try to apply those concepts and ideas to paper with the problems you are assigned... well, you just lose it. It simply doesn't make sense for a lot of these programs with the examples she supplies. For instance, why is she still using "DOWHILE more records exist" if we already have covered arrays and how to know if more records exist or not? Do we need to write the lengthy version of how to find out if more records exist or not? What assumptions are we taking this time?

The problem with this book is that it's not about an actual programming language, it's about pseudocode which isn't defined very well. I think if you want to learn how to program, get a book that is based on an actual language and not some gibberish.

The book is horrible. I definitely do not recommend it. Very boring to read, examples that are missing parts, and problems that demand things that one doesn't know how to do because they were never defined well in the first place.

Instructors: Do not get this freaking book! If you want to teach a programming language then try Python. (Python Programming by Zelle is great!)

People who want to learn: Learn an actual language.