Big C++ Review

Average Reviews:

(More customer reviews)Are you looking to buy Big C++? Here is the right place to find the great deals. we can offer discounts of up to 90% on Big C++. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Big C++ ReviewThis is an excellent textbook written by knowledgeable authors. Horstmann teaches at San Jose State University in California. He has in-depth knowledge of C++, having written the Safe STL library. He also writes for the Sun Core Java series of books.
Although the book is large, it can be used for a 2 or 3 semester sequence of courses in software development using C++. After covering fundamentals, the authors cover advanced topics with modern relevance. Chapter 13 on Object-Oriented Design discusses the software development life cycle, Class-Responsibility-Collaboration using CRC cards, and gives practical tips for implementing class associations. Other advanced topics include templates (similar to generics), the C++ Standard Template Library, design patterns, GUI's, Relational Databases (using MySQL), and XML. Appendices cover C++ Language Coding Guidelines, and legacy C/C++ topics.
The authors' writing style is very clear and easy for college freshmen to understand. The Random Facts sections help make the textbook interesting, and cover topics such as: Computing History, the First Bug, the Therac-25 bug (an ethical issue), the Ariane Rocket incident, etc.
Sample code can be found at the author's website at:
http://www.horstmann.com/bigcpp.html
and also at the Wiley publisher higher education website:
http://he-cda.wiley.com/WileyCDA/ (search by author for Horstmann). The book is well organized with a good set of end-of-chapter exercises, programming problems, and references for further reading.
We have adopted this textbook for a 2-sequence course in object-oriented software development. I highly recommend it.Big C++ OverviewThis proven author team combines their professional and academic experience to offer the most relevant and comprehensive introduction to programming and C++. * Authors combine professional and academic experience to offer the most relevant introduction to programming and C++ * Offers comprehensive examination of computer science, programming principles, and the C++ language * Covers advanced C++ topics, such as operator overloading, memory management, polymorphism, and more * Thorough coverage of STL * Integration of current technologies, such as UML and patterns

Want to learn more information about Big C++?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Code Complete (Microsoft Programming Series) Review

Average Reviews:

(More customer reviews)Are you looking to buy Code Complete (Microsoft Programming Series)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Code Complete (Microsoft Programming Series). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Code Complete (Microsoft Programming Series) ReviewAbout previous comments: Verbose? Don't think so, every page has some piece of valuable information
For beginners only? Don't think so, but if you are a beginner this is a good place to start. After several years of programming you'll mostly stop thinking about style and follow your habits... so you better have some good habits!
Insistence on using hungarian naming convention? Not at all, did you read this book? The author did talk about this convention but he also gives examples why this is can be bad (and also why it can be good).
This book covers a wide range of material, from variable declaration to software estimation and probably everything concerning software construction.
Also as this book talks a lot about style, the best thing is it is backed up with hard facts not just because of personal preference.
The examples are written in several languages (such as C, Pascal and Basic). One chapter is devoted to object orientation. Although you're heavily into OOP then in no way should you skip over this book as the advices in this book can be applied to every methodology of programming. So this book is in no way out dated.
Each chapter has a 'recommended reading' section so you know where to go for more. This is extremely handy.
I've read this book several times and I just love it. I own every book written by the author. Check them out also - they are very good too.
Summary: This book teaches you how you can write good and self-describing code. I wished every program I've had to read had been written by programmers who read this book and applied that knowledge.
Thanks, ABOCode Complete (Microsoft Programming Series) OverviewHere is a thorough expert look at the intricate process of commercial software development. The text is rich in example code, contains powerful insights on managing technical yet creative people, and examines each milestone in software development in considerable detail. Ideal for professional, self-taught, and student programmers.

Want to learn more information about Code Complete (Microsoft Programming Series)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Software Testing Review

Average Reviews:

(More customer reviews)Are you looking to buy Software Testing? Here is the right place to find the great deals. we can offer discounts of up to 90% on Software Testing. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Software Testing ReviewOuch -- I see the previous review was pretty harsh and terse. Having written a book myself (also for SAMS, coincidentally), I know that doesn't feel good or help much.
Anyway, I came to amazon today specifically to order this book after I perused it at the bookstore for a while this weekend. I wasn't going to buy it, but then it sank in and I decided I should.
My QA bible is Robert V. Binder's massive tome "Testing Object-Oriented Systems: Models, Patterns, and Tools." That book is the best book out there for hard core software QA engineers. But it's not for everyone. It's huge, it's somewhat inaccessible (even though Bob Binder might not want it to be), and it's more than many people need.
The reason I am buying Ron Patton's book today is that it's relatively short, it covers all the basics in good, solid detail, and it nicely summarizes some of the same stuff you find in Binder. No, Ron Patton's book doesn't include a UML reference or a full blow out of state machines and combinatorial models, but should every QA book do that? I don't think so.
This book has some good stuff and I will use it and recommend it to try to make some things more accessible to new people joining my team and to managers and QA engineers in other departments who aren't ready or willing to digest something like Binder.Software Testing OverviewSoftware Testing is the book for new or aspiring software testers interested in learning about this crucial part of the software development process. The complexity and size of today's software makes writing bug-free code extremely difficult, even for highly experienced programmers. Couple that with our increasing reliance on software for performing everyday tasks and its pervasiveness in the medical, telecommunications, manufacturing, and financial industries, and a software bug can spell disaster. Quality software can't be created with an ad- hoc, part-time, bug hunt. It requires a methodical and disciplined approach to preventing, finding, and reporting bugs. Software Testing will show you what it takes to be a successful software tester, assuring that you discover those nasty bugs before your customers do.

Want to learn more information about Software Testing?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Software Engineering (6th Edition) Review

Average Reviews:

(More customer reviews)Are you looking to buy Software Engineering (6th Edition)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Software Engineering (6th Edition). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Software Engineering (6th Edition) ReviewSommerville gives a keen view of the entire breath of this broad topic. His text is filled with easy to understand illustrations and chapter summaries. The examples are end-to-end because he provides the needed preliminaries (concepts and foundations) to understand the results. His treatment of requirements engineering and formal specification methods is quite good. In addition to the key points (of each chapter) he provides pointers to other resources on each subtopic. I find this text better for use in the classroom than the other leading text (which I use as a reference) because Sommerville's presentation provides a more logical flow and organization (i.e., its easier to read). I used the slides that are available (.ppt) from his web site to supplement my lectures.Software Engineering (6th Edition) OverviewSoftware Engineering presents a broad perspective on software systems engineering, concentrating on widely-used techniques for developing large-scale software systems. This best-selling book covers a wide spectrum of software processes from initial requirements elicitation through design and development to system evolution. It supports students taking undergraduate and graduate courses in software engineering. The sixth edition has been restructured and updated, important new topics have been added and obsolete material has been cut. Reuse now focuses on component-based development and patterns; object-oriented design has a process focus and uses the UML; the chapters on requirements have been split to cover the requirements themselves and requirements engineering process; cost estimation has been updated to include the COCOMO 2 model.

Want to learn more information about Software Engineering (6th Edition)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Object-Oriented Software Engineering Using UML, Patterns, and Java (3rd Edition) Review

Average Reviews:

(More customer reviews)Are you looking to buy Object-Oriented Software Engineering Using UML, Patterns, and Java (3rd Edition)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Object-Oriented Software Engineering Using UML, Patterns, and Java (3rd Edition). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Object-Oriented Software Engineering Using UML, Patterns, and Java (3rd Edition) ReviewMany SE books tell you about SE (eg., Sommerville). Those kinds of books equip you to win in a software engineering version of the trivia game Jeopardy! but will hardly impart any skill and will not make you a better software engineer, only more informed.
In contrast, this book tells you how to do software engineering. They tell you what, Bruegge shows you how. Rather than cover all the concepts in SE, Bruegge picks the most essential ones, gives you a brief but thorough explication of those and then proceeds to teach how they are used.
Professor Bruegge's approach to teaching his SE students is by having his entire class work *together* as one team on *one* real-life project during the term (that's one project for the whole class).
Typically, this project is an upgrade of the previous class's project. Stop and imagine how realistic this approach is -- modifying a system created by engineers who are no longer available for interview, working with as many as 50 different people, working with designs that do not match the code anymore, working with code of varying quality, etc.
Bruegge distills the lessons learned from these practical projects and illustrates practical (not idealistic) approaches to solutions.
Expect German thoroughness and a lucid, unpretentious prose that heeds Strunk and White's dictum: "Omit needless words".
Highly recommended.
-vjaObject-Oriented Software Engineering Using UML, Patterns, and Java (3rd Edition) OverviewFor courses in Software Engineering, Software Development, or Object-Oriented Design and Analysis at the Junior/Senior or Graduate level. This text can also be utilized in short technical courses or in short, intensive management courses.

Object-Oriented Software Engineering Using UML, Patterns, and Java, 3e, shows readers how to use both the principles of software engineering and the practices of various object-oriented tools, processes, and products.

Using a step-by-step case study to illustrate the concepts and topics in each chapter, Bruegge and Dutoit emphasize learning object-oriented software engineer through practical experience: readers can apply the techniques learned in class by implementing a real-world software project.

The third edition addresses new trends, in particular agile project management (Chapter 14 Project Management) and agile methodologies (Chapter 16 Methodologies).


Want to learn more information about Object-Oriented Software Engineering Using UML, Patterns, and Java (3rd Edition)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Data Structures and Program Design In C (2nd Edition) Review

Average Reviews:

(More customer reviews)Are you looking to buy Data Structures and Program Design In C (2nd Edition)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Data Structures and Program Design In C (2nd Edition). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Data Structures and Program Design In C (2nd Edition) ReviewI just finished an online course on data structures at UMass, Lowell (secured an A grade without any problem) and this is the textbook used for this course. I agree with some of the comments made by the reviewers here - that typedef's are used beyond reason, code is presented in fragments. I must strongly disagree with the reviewers who said - the book is not worth the money (it's cheap if you buy a used one), it is a bad book, useful only as a paper weight. The strong plus point for this book is that it presents theory well - there are many figures using which it is easy to understand complicated stuff. The other plus point is that it also analyzes the performance of algorithms and I felt the book does a great job of explaining this part in clear terms. The main drawback is that the code is fragmented and spread out, which is certainly frustating. Also, in order to get the code to work on a compiler (I used Microsoft VC++ version 6), you will need to "fill in the gaps" as most code examples (I tried 90% of the examples in the text on MVC++ compiler) are by no means complete but this was not difficult. You can download the code from the publisher's website and the code is actually not organized into different files (sorted by chapter and example) but it comes in a few files where examples from different chapters are mixed. You will have to search and find the part you need. I do agree usage of dummy functions creates confusion. This book has a rocky start with the life game example, which was not very easy to follow with the explanation provided. While I was frustated with the first two chapters, the rest of the chapters are presented well. To the reviewer who said that the code has bugs (which certainly isn't true), my guess that the gaps are not properly filled. I patiently tested most of the code on the computer (after filling in the gaps of course!) and find absolutely no problems with it. This however took lot of time since significant effort is needed from the student to fill the missing code to make it work. I have supplied working code to my fellow students who were facing difficulties in getting the code to run. In a couple of places in the text, the author surprised me with C syntax I did not know was legal (I consider myself intermediate programmer).
I suspect the reason why many readers have problems with this book is two-fold: 1.The code is not available in a format that can be tested on the compiler. Having read a lot of CS books which supply with readily usable code, this book gets annoying. I was wondering why the authors did not give downloadable working code for all examples in the text (which is a definite minus point) 2. The reader will have to go back and forth between the chapters as some functions developed in former chapters are used in later chapters. This does get irritating. I have read books that do this to a ridiculous level but this book stays with in tolerable bounds.
I will not rate this book as the best one on the subject out there but it is definitely good enough to learn data structures. I have used another book as a supplement: Data Structures & Algorithms in Java (Mitchell Waite Signature Series) (Hardcover) By Mitchell Waite, Robert Lafore ISBN: 1571690956. This book has lot of applets that show step by step how algorithms work. I am a visual learner and this helped tremendously. However, I felt that Waite Series book did not present the theory as thoroughly as Robert Kruse's text.
In summary, I consider this book as "decent". I was very much concerned when I first purchased this text because of so many bad reviews. As it turns out, those that can understand C and are willing to sit in front of the computer to make the code samples in this book work need not have any fear. As I said earlier, the theory is presented well, and all it needs is patience and diligence from the student to go through the code examples on a compiler. I believe that I now have a good understanding of the subject and I can move on books that deal with it at more depth. There are a plethora books on this topic out there and there may be better books than the ones mentioned in this review.Data Structures and Program Design In C (2nd Edition) Overview Progressing from the concrete to the abstract —and using numerous, substantial case studies and sample programs —this book explores structured problem solving, data abstraction,software engineering principles, and the comparative analysis ofalgorithms as fundamental tools of program design. Emphasizes principles of top-down refinement, programdesign, review, and testing. Uses the C programming languagethroughout. Offers Internet access to the source codefor all the programs and program extracts printed in the book.

Want to learn more information about Data Structures and Program Design In C (2nd Edition)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Agile Software Development Review

Average Reviews:

(More customer reviews)Are you looking to buy Agile Software Development? Here is the right place to find the great deals. we can offer discounts of up to 90% on Agile Software Development. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Agile Software Development ReviewEvery fifteen years or so, a great book pops up that describes what
projects are really like. There was Brooks, then DeMarco and Lister,
and now there's Cockburn.
Why is there such a gap between these great books? Possibly because
the message they contain isn't the easy-to-digest dictate: "run your
project this way and everything will be fine." Instead these books all
focus on the fundamentals of projects: people and the way they work
together. These books treat people as people, and not replaceable
parts in a process. The books accept people's foibles and
inconsistencies, and work out how to work with them, rather than how
to try to stamp them out. The books ask: how can we help these funky
people work better together to produce great software?
Agile Software Development has some great answers, which makes it a
significant book. It deals with the issue that programming is
essentially communicating. It looks at the success factors of
individuals, and how to help align the project with these. It
discusses practical ways to reduce the latency of communication (do
you know how much each extra minute taken finding things out costs on
a 12 person project? How do you line your walls with information
radiators?) The book mines the metaphor of development as a
cooperative team game, and looks at development organizations as a
community, where good citizenship pays.
So how _do_ you organize all these people, these team players, these
citizens? The answer is with methodologies. But not with something you
buy off-the-shelf. Cockburn argues that teams should work to define,
and then refine, their own methodologies, bringing in standard ones
where they fit. To help the teams, he has a wonderful section
describing what methodologies _are_, and how to build them. This is
good, solid, practical advice. He talks about when it's good to be
light, and when you need to be heavier, when laissez-faire works, and
when you need ceremony to reduce risks. Then, not content with helping
you create a methodology, Cockburn explains how to adapt what you have
to a changing world.
If you work in or with a team developing software, then you owe it to
yourself (and your team) to read this book. You'll come away with a
far clearer understanding of the dynamic at work in your team, and
with lots of ideas for improving it. And that's the whole point.Agile Software Development OverviewLightweight methodologies are exploding in popularity because their flexibility is ideal for today's fast-changing development environments. In Agile Software Development, legendary software expert Alistair Cockburn reviews the advantages and disadvantages of lightweight methods, synthesizing the field's key lessons into a simplified approach that allows developers to focus on building quality software rapidly, cost-effectively, and without burnout. Ideal for managers seeking to transcend yesterday's failed approaches, the agile movement views software development as a cooperative game. As players move throughout the game, they use markers and props to inform, remind, and inspire themselves and each other. The goal of the game: to deliver a working software system -- and to use the lessons of each project to build a new, smarter "game" for the next project. For every IT executive and manager, software developer, team leader, team member, and client concerned with building robust, cost-effective software.

Want to learn more information about Agile Software Development?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Software Engineering (7th Edition) Review

Average Reviews:

(More customer reviews)Are you looking to buy Software Engineering (7th Edition)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Software Engineering (7th Edition). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Software Engineering (7th Edition) ReviewSoftware engineering is to computer science what engineering is to physics, as the author suggests. Here, the emphasis is on a higher level than, say, the crafting of algorithms. The scope is for systems analysis, design and implementation. He explains that the traditional waterfall method had many shortcomings. Its monolithic stages often proved unwieldy.
The book goes into alternatives. It also gives a good overall treatment of such ideas as formal specification and architectural design. With an entire chapter focusing on the key ways to have distributed systems architectures. Unsurprisingly, CORBA gets the most extensive description. A reflection of the amount of effort that has gone into using it since the late 80s. However, there is scant mention of its drawbacks. Most important of which has been that the exchange of binary data has been very brittle.
He mentions p2p and Web Services, as contrasting approaches. Where the latter uses XML to exchange data in a readable format. This has been widely seen as a big advantage over CORBA, but the book doesn't mention it. Given the continued rise in Web Services, perhaps a future edition of the book could give it more coverage?
The most controversial part of the text might be the section on Extreme Programming. Its characteristics are well described. But perhaps not enough on its disadvantages. Like the idea of collective ownership of code. Not all programmers have the same ability or expertise. Some programmers are far better than others. It is very bad to have a tyro unwittingly change code for which she has insufficient understanding. While the author may not necessarily agree with this, he should at least describe it.
Other sections of the book, especially on testing software and validating critical system parts, are quite lucid and should excite little disagreement.Software Engineering (7th Edition) OverviewSoftware Engineering presents a broad perspective on software systems engineering, concentrating on widely used techniques for developing large-scale systems. The objectives of this seventh edition are to include new material on iterative software development, component-based software engineering and system architectures, to emphasize that system dependability is not an add-on but should be considered at all stages of the software process, and not to increase the size of the book significantly.To this end the book has been restructured into 6 parts, removing the separate section on evolution as the distinction between development and evolution can be seen as artificial. New chapters have been added on:Socio-technical Systems discussing the context of software in a broader system composed of other hardware and software, people, organisations, policies, procedures and laws.Application System Architectures to teach students the general structure of application systems such as transaction systems, information systems and embedded control systems. The chapter covers 6 common system architectures with an architectural overview and discussion of the characteristics of these types of system.Iterative Software Development looking at prototyping and adding new material on agile methods and extreme programming.Component-based Software Engineering introducing the notion of a component, component composition and component frameworks and covering design with reuse.Software Evolution revising the presentation of the 6th edition to cover re-engineering and software change in a single chapter.The book supports students taking undergraduate or graduate courses in software engineering, and software engineers in industry needing to update their knowledge.

Want to learn more information about Software Engineering (7th Edition)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

The Practice of Programming Review

Average Reviews:

(More customer reviews)Are you looking to buy The Practice of Programming? Here is the right place to find the great deals. we can offer discounts of up to 90% on The Practice of Programming. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

The Practice of Programming ReviewIn computing, the learning curve is doubly steep. Not only do we have to learn very complex operations, but we have to learn them at a pace unrivaled in any other field. Furthermore, the equipment improves at a rate that simply boggles the mind. In this frantic environment, we rarely have time to read our code twice, much less read a book about code. Therefore, when we do read, we must make every minute count. This is one book where your count of wasted minutes would be a very small one.
Some of the tips in this book are obvious in retrospect, yet ones that you probably would not think of. My favorite is the fact that due to the changes in processors, a double precision floating point arithmetic operation can be faster than the equivalent one for integers. In the "old" days, the gospel was that you must avoid floating point operations unless absolutely necessary, to avoid the degradation of performance.
Other tips, such as methods to assure you comment what is necessary, taking a few minutes to learn simple performance features, debugging and testing guidelines; portability issues and basic algorithm analysis should cause you to pause for a moment. Even in our hectic development environments, stopping and analyzing your code is a necessity.
It is difficult to conceive of someone who will not find a tip in here that will justify the cost of the book. Unless of course, you are one of the authors. I listed it as one of the top books of the year in my On Books column that appeared in the September, 1999 issue of _Journal of Object-Oriented Programming_.The Practice of Programming Overview

Want to learn more information about The Practice of Programming?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

A Discipline for Software Engineering Review

Average Reviews:

(More customer reviews)Are you looking to buy A Discipline for Software Engineering? Here is the right place to find the great deals. we can offer discounts of up to 90% on A Discipline for Software Engineering. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

A Discipline for Software Engineering ReviewThis book's title contains two key words that are woefully missing from most development projects: "discipline" and "engineering". With this book Mr. Humphrey introduced the personal software process (PSP), which subsequently spawned the team software process (TSP). Although the material is over 6 years old and does not seem to have gained wide acceptance in commercial development and project environments, it provides a roadmap to effectively integrating the increasingly popular extreme programming (XP)approach that was developed by Kent Beck.
How does PSP align to XP? Both approaches focus heavily on project planning and estimating, and controlling quality, cost and schedule. Both approaches also use metrics as a baseline and past performance to predict future productivity and quality during the planning and estimation phases of new projects. Moreover, both approaches impose a rigorous discipline at a low level in the development process - PSP at the individual level and XP at the 2-person paired team level. An excellent book on XP that supports this premise is Planning Extreme Programming by Kent Beck and Martin Fowler.
The methods that Mr. Humphrey proposes in this book are the building blocks of an effective XP organization because much of the metrics he proposes for capture, analysis and tracking are the very ones that are key to XP. These methods add the "discipline" into the development process, and "engineering" into the quality approach to any development effort, regardless of whether the methods are aligned to XP or any other methodology. Further, the disciplined engineering approach will provide organizations striving for capability maturity model (CMM) level 4 (managed) or 5 (optimizing) with some valuable tools and techniques with which to achieve these higher levels of maturity. Of course, this is also useful to organizations that are implementing SPICE (Software Process Improvement Capability dEtermination), organizing software process engineering groups, or implementing mature project management methods for development projects.
I agree with a previous reviewer that development is also a social and cognitive discipline, but it is not solely those. The social and cognitive approach will only get you so far. The same is true of the disciplined engineering approach. You need both, and this book is a valuable work for the latter.
In my opinion this book is probably more valuable today then when it was first published because the approach required too much rigor for most organizations to adopt. However, with the growing movement towards XP I believe that this book will add details and techniques that are only superficially addressed in the XP body of knowledge and literature. If you are a proponent of XP this book provides some proven, concrete techniques. If you are striving for higher levels of capability maturity this book (and the companion, Introducing the Team Software Process by Mr. Humphrey) will give you the tools to get to managed, and from there to optimizing. I believe this book is a 5-star classic that was ahead of its time.A Discipline for Software Engineering OverviewThis book from Watts Humphrey broadens his disciplined approach to software engineering. In his earlier book, Managing the Software Process, Humphrey developed concrete methods for managing software development and maintenance. These methods, now commonly practiced, provide programmers and managers specific steps for evaluating and improving their software capabilities. In this book, he scales down those methods to a personal level, helping software practitioners develop the skills and habits they need to plan, track, and analyze large and complex projects more carefully and successfully.

Want to learn more information about A Discipline for Software Engineering?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library Review

Average Reviews:

(More customer reviews)Are you looking to buy Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library? Here is the right place to find the great deals. we can offer discounts of up to 90% on Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library ReviewThis is a truly useful book. It explains lots of little "gotchas" that I didn't know about previously, and Scott does his usual excellent job at explaining *why* it's important to do things a certain way (and no other). One part that I found particularly interesting is about the futility of writing container-independent code; not only does that section show why this is a bad idea, it also serves as a splendid illustration of the idiosyncracies of the various containers. The chapter on iterators is priceless, as are the tips about writing comprehensible code and debugging.
The presentation is very much up-to-date (even to the point where it anticipates some of the forthcoming updates to the C++ standard). The writing style is clear and precise without sounding academic or condescending, and the book has an index that actually works.
"Effective STL" is every bit as good as "Effective C++" and "More Effective C++". No C++ programmer should still be writing code without the STL, and no-one writing code with the STL should be without this book. Buy it!Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library Overview"This is Effective C++ volume three – it's really that good."– Herb Sutter, independent consultant and secretary of the ISO/ANSI C++ standards committee"There are very few books which all C++ programmers must have. Add Effective STL to that list."– Thomas Becker, Senior Software Engineer, Zephyr Associates, Inc., and columnist, C/C++ Users JournalC++'s Standard Template Library is revolutionary, but learning to use it well has always been a challenge. Until now. In this book, best-selling author Scott Meyers (Effective C++, and More Effective C++) reveals the critical rules of thumb employed by the experts – the things they almost always do or almost always avoid doing – to get the most out of the library.Other books describe what's in the STL. Effective STL shows you how to use it. Each of the book's 50 guidelines is backed by Meyers' legendary analysis and incisive examples, so you'll learn not only what to do, but also when to do it – and why.Highlights of Effective STL include:Advice on choosing among standard STL containers (like vector and list), nonstandard STL containers (like hash_set and hash_map), and non-STL containers (like bitset). Techniques to maximize the efficiency of the STL and the programs that use it. Insights into the behavior of iterators, function objects, and allocators, including things you should not do. Guidance for the proper use of algorithms and member functions whose names are the same (e.g., find), but whose actions differ in subtle (but important) ways. Discussions of potential portability problems, including straightforward ways to avoid them.Like Meyers' previous books, Effective STL is filled with proven wisdom that comes only from experience. Its clear, concise, penetrating style makes it an essential resource for every STL programmer.

Want to learn more information about Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Software Architecture: Foundations, Theory, and Practice Review

Average Reviews:

(More customer reviews)Are you looking to buy Software Architecture: Foundations, Theory, and Practice? Here is the right place to find the great deals. we can offer discounts of up to 90% on Software Architecture: Foundations, Theory, and Practice. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Software Architecture: Foundations, Theory, and Practice ReviewSoftware Architecture: Foundations, Theory, and Practice is a landmark text that will become an essental introduction to the discipline of software systems architecture. If you are a student, tester, manager, methodologist, developer, or simply an architect, and want a holistic understanding of what real software architects think software architecture is and why it matters, this is the place to start.
I bought this after Roy Fielding (of REST and HTTP fame) mentioned it on the rest-discuss mailing list. Roy is one of the industry's top architects, and I wasn't disappointed. The book is timely - architecture is coming to be accepted as an important activity, especially for distributed, and large scale systems. What many people don't realize is that drawing pictures, writing documents no-one reads, meta-modeling, and pontificating on "concerns" are not software architecture. Software architecture is about introducing constraints via principled, objective design to achieve particular system properties. Architecture is difficult and exhausting work, but done well can offer immense value to users and stakeholders. This book, along with Rozanski and Woods' "Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives" makes that explicit.
The book is unapologetic about software architecture's standing in the industry. SAFTAP positions architecture as the primary design activity for software - not development, not requirements analysis, not testing, not methodology, but architecture. That will make for interesting debate.
My single criticism of this book is that it does not do enough to treat user experience (Ux) and informatics as architecturally significant, but not enough to take away a star. I'm hoping a future edition will rectify that.
Some noteworthy chapters in the book (there are 17 chapters in all):
* The Big Idea: explains what architecture is and why it matters. The building metaphor (often heavily criticised in the industry, see the excellent "Software is not Bricks" by Raganwald) is dealt with calmly and then put to one side.
* Architecture in Context: explains how architecture fits into the overall lifecycle and process of software systems.
* Connectors: this is one of my favourite chapters. The concept of a connector is vital to a software system, but is rarely if ever discussed in programming or engineering texts.
* Modeling: probably not what you think. This chapter emphasizes communication, clarity and disambiguation over notations and diagrams.
* Implementation: programmers hate the quip "implementation detail", but in truth many things in a system are just that and it does not mean they are unimportant. This chapter covers those details and why they matter.
* Deployment and Mobility: good architects understand that a systems have a life well beyond initial delivery, which is where most developers, managers and stakeholders tend to focus attention. This was one of favorite sections as the running system simply doesn't get enough attention in most projects today.
* Applied architecture and Styles: covers some examples of architectural styles, notably REST and SOA, which are certainly the best known architectures in my part of the industry.
* Designing for non-functional properties: many non-functional concerns don't start to matter until the system is deployed and there isn't always agreement among technical specialists over what's truly important. If you are technical specialist this should help you articulate the cost/benefit of looking at the "unfeatures" of a system.
* Security and Trust: software is increasingly distributed, and increasingly a super-system of components interacting over the Internet and Mobile Networks. So it's good to see a text that makes security a first order concern and not just a non-functional ones.
* Domain Specific Software Engineering: I'm trained as an industrial designer where the notion of common modular components with standard interfaces acting as a platform for product development is a known Good Thing in domains such as the automotive and consumer electronics industries. This chapter gives a good overview of modular design focusing on the software product lines approach. The example given is from Philips, but it could as easily have been from Toyota.
* People, Roles and Teams: software architecture, like other architecture disciplines, has a strong social dimension. This chapter explains how the architect role fits into an organisation and where they can add value and exert influence.Software Architecture: Foundations, Theory, and Practice OverviewSoftware architecture is foundational to the development of large, practical software-intensive applications. This brand-new text covers all facets of software architecture and how it serves as the intellectual centerpiece of software development and evolution. Critically, this text focuses on supporting creation of real implemented systems. Hence the text details not only modeling techniques, but design, implementation, deployment, and system adaptation -- as well as a host of other topics -- putting the elements in context and comparing and contrasting them with one another. Rather than focusing on one method, notation, tool, or process, this new text/reference widely surveys software architecture techniques, enabling the instructor and practitioner to choose the right tool for the job at hand. Software Architecture is intended for upper-division undergraduate and graduate courses in software architecture, software design, component-based software engineering, and distributed systems; the text may also be used in introductory as well as advanced software engineering courses.

Want to learn more information about Software Architecture: Foundations, Theory, and Practice?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Head First Design Patterns Review

Average Reviews:

(More customer reviews)Are you looking to buy Head First Design Patterns? Here is the right place to find the great deals. we can offer discounts of up to 90% on Head First Design Patterns. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Head First Design Patterns ReviewAt first I didn't understand how they would apply the Head First formula to design patterns. I'd read two head first before this one and I was impressed with those so I took a look and now, not only is it clear how they approached the topic, it's also clear to me that this is the best way to learn design patterns.
The Gang of Four book laid out the basics. Here is the pattern, here are some examples. The head first book goes a lot further. They show you good and bad examples of the pattern. They give solid reasoning behind the pattern. It's great.
There are times when I would look at a piece of code and have the author explain to me that it was based on one of the GoF patterns. I would come away thinking, if that's the pattern, then that pattern sucks. It's clear that patterns can be misapplied. So understanding the the how design patterns are applied, and how they are commonly applied wrongly, or to an extreme, is just as important as understanding the basic mechanics of the pattern itself.
The example code is in Java, but I think this is an ideal book for anyone passionate about patterns.Head First Design Patterns Overview
You're not alone. At any given moment, somewhere in the world someone struggles with the same software design problems you have. You know you don't want to reinvent the wheel (or worse, a flat tire), so you look to Design Patterns--the lessons learned by those who've faced the same problems. With Design Patterns, you get to take advantage of the best practices and experience of others, so that you can spend your time on...something else. Something more challenging. Something more complex. Something more fun. You want to learn about the patterns that matter--why to use them, when to use them, how to use them (and when NOT to use them). But you don't just want to see how patterns look in a book, you want to know how they look "in the wild". In their native environment. In other words, in real world applications. You also want to learn how patterns are used in the Java API, and how to exploit Java's built-in pattern support in your own code. You want to learn the real OO design principles and why everything your boss told you about inheritance might be wrong (and what to do instead).You want to learn how those principles will help the next time you're up a creek without a design pattern. Most importantly, you want to learn the "secret language" of Design Patterns so that you can hold your own with your co-worker (and impress cocktail party guests) when he casually mentions his stunningly clever use of Command, Facade, Proxy, and Factory in between sips of a martini. You'll easily counter with your deep understanding of why Singleton isn't as simple as it sounds, how the Factory is so often misunderstood, or on the real relationship between Decorator, Facade and Adapter. With Head First Design Patterns, you'll avoid the embarrassment of thinking Decorator is something from the "Trading Spaces" show. Best of all, in a way that won't put you to sleep!We think your time is too important (and too short) to spend it struggling with academic texts. If you've read a Head First book, you know what to expect--a visually rich format designed for the way your brain works. Using the latest research in neurobiology, cognitive science, and learning theory, Head First Design Patterns will load patterns into your brain in a way that sticks. In a way that lets you put them to work immediately. In a way that makes you better at solving software design problems, and better at speaking the language of patterns with others on your team.


Want to learn more information about Head First Design Patterns?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

The Business Analyst's Handbook Review

Average Reviews:

(More customer reviews)Are you looking to buy The Business Analyst's Handbook? Here is the right place to find the great deals. we can offer discounts of up to 90% on The Business Analyst's Handbook. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

The Business Analyst's Handbook ReviewThis book has solid reference material that experienced Business Analysts can utilize on virtually any assignment. This is not the best book for a new Business Analyst and is really geared towards a practitioner that understands their craft and appreciates additional guidance. Coverage of techniques and models is very comprehensive.The Business Analyst's Handbook OverviewThe Business Analyst (BA) plays an important role as liaison between business stakeholders and the technical team (software developers, vendors, etc.), ensuring that business needs are reflected in any software solution. Despite the importance of the job, there is currently no book specifically designed as a comprehensive reference manual for the working BA. The Business Analyst's Handbook solves this problem by providing a useful compendium of tools, tables, lists, and templates that BAs can use on-the-job to carry out their tasks. For example, you might be preparing for an interview session and use the book's checklist of interviewees to verify whether there is appropriate coverage of business stakeholders. Or you might be asked to review some diagrams and refer to the Glossaries of Symbols (organized by diagram type) for guidance. Or you may be asked to prepare textual requirements documentation and refer to the Business Requirement template for a list of artifacts and table of contents. Whatever your BA needs, the Business Analyst's Handbook places the necessary information right at your fingertips.

Want to learn more information about The Business Analyst's Handbook?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Java/J2EE Job Interview Companion Review

Average Reviews:

(More customer reviews)Are you looking to buy Java/J2EE Job Interview Companion? Here is the right place to find the great deals. we can offer discounts of up to 90% on Java/J2EE Job Interview Companion. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Java/J2EE Job Interview Companion ReviewIt's a long exam, by some standards. The questions range very widely, and offer a strenuous test of your java knowledge. The relatively easy section comes first. Where the questions are about standard java. The java that is usually denoted J2SE. Many java programmers should breeze thru it. Anyone with fluency in writing vanilla java won't have any problems. Perhaps in recognition of this, the author has kept this section relatively brief.
The meat of the exam is about Enterprise level java. J2EE. Much of this relates to running an enterprise program on a server. What type of server? Some questions concern when you have a web server. So brush up on Java Server Pages, Servlets and Beans. Speaking of beans, you also need to cover EJBs.
Another type of server is when you have to hook up to a SQL database. And there are questions about how to do this. Plus, interacting between a java program and XML is an important practical topic. Also covered. Along with running unit tests, via JUnit, and implementing a logger.
More is covered. Good revision before a job interview.Java/J2EE Job Interview Companion Overview
400+ Java/J2EE Interview questions with clear and concise answers for: job seekers (junior/senior developers, architects, team/technical leads), promotion seekers, pro-active learners and interviewers. Free download

Lulu top 100 best seller. Increase your earning potential by learning, applying and succeeding. Learn the fundamentals relating to Java/J2EE in an easy to understand questions and answers approach. Covers 400+ popular interview Q&A with lots of diagrams, examples, code snippets, cross referencing and comparisons. This is not only an interview guide but also a quick reference guide, a refresher material and a roadmap covering a wide range of Java/J2EE related topics.


Want to learn more information about Java/J2EE Job Interview Companion?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Case Studies in Object-Oriented Analysis and Design (Bk/Disk) Review

Average Reviews:

(More customer reviews)Are you looking to buy Case Studies in Object-Oriented Analysis and Design (Bk/Disk)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Case Studies in Object-Oriented Analysis and Design (Bk/Disk). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Case Studies in Object-Oriented Analysis and Design (Bk/Disk) ReviewThis book is great. It starts from a description of the case studies and it ends with the implementation. With this book, you can make your first object oriented project a GOOD one with ease! A must have for a beginner on object-oriented projects. I've tried other books, but none compared to this. Really great!Case Studies in Object-Oriented Analysis and Design (Bk/Disk) OverviewAlthough there are numerous books on object-oriented programming, few go beyond a presentation of terminology, notation and the structure of a unique model. Written by a co-developer of one of the most popular OOA/OOD methods, this exceptionally practical and authoritative casebook shows how object-oriented analysis and design are actually practiced in developing real systems-i.e., shows the insight (rather than the technique) that was applied at each step in a solution-false starts and all. Presents two very realistic case studies-one with a predominant reactive view and one with a predominant data view-and shows how the principles of object-oriented analysis and design are applied to them.

Want to learn more information about Case Studies in Object-Oriented Analysis and Design (Bk/Disk)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Software Requirements Review

Average Reviews:

(More customer reviews)Are you looking to buy Software Requirements? Here is the right place to find the great deals. we can offer discounts of up to 90% on Software Requirements. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Software Requirements ReviewKarl Wieger's book is destined to be classic in software requirements. It delivers a large set (over 40) no-nonsense best practices in highly readable, non-nonsense manner. I believe every project manager, IT (Information Technology) and business analyst, and IT account manager should read this book. Further, developers would do well to read it to gain critical insight into the 'big picture' of requirements engineering.
The book is broken down into three sections: the case for requirements engineering best practices ("What and Why"), the requirements discovery, verification and validation process ("Software Requirements Engineering"), and the essentials of requirements management ("Software Requirements Management"). Throughout, the dual necessities of doing requirements right (verification) and doing the right requirements (validation) is addressed. Wiegers has thoroughly delved into the literature in the software requirements field. The text is liberally spiced with tidbits of data to support the business case for implementing these best practices. I found myself making notes in the inside cover and folding back pages to reference again as I read through the book.
Early in the book, Wiegers presents a set of software engineering best practices which are classified into priority (high, medium, low) and difficulty (high, medium, low). Although you may disagree with the specific rankings for your shop, this table is an excellent example of modeling appropriate requirements engineering practices - prioritizing requirements! Other goodies abound. For example, a partial case study flows throughout the book which gives the reader enough of an idea of what a use case, dialog map, text requirement, etc. looks like to get the concept being resented. Each chapter ends with a concise list of suggested next steps, providing the reader with concrete actions to take to implement the practices covered in that chapter. In addition, there are numerous sample templates (e.g. Risk Item Tracking, Software Requirements Specification), several excellent checklists (e.g. Inspection Checklist for Software Requirements Spec, Software Elements Affected by a Proposed Change,), visual models (e.g. Requirements Traceability Links, Change Control Process) and a wonderful "bill of rights" for the software customer which boldly and directly asserts both rights and responsibilities of the customer.
A set of example models is provided in the chapter called "A Picture is Worth 1024 Words". You will need to read other books or take training on the mechanics, notations and semantics of these models for visualized functional requirements. But the author covers the key models and their purpose succinctly.
This book is easy to read, cuts to the chase, and provides a bounty of information that will wet our appetite to take action. This book is not a requirements engineering method or methodology, which would prescribe step-by-step protocols of task, roles, and techniques. Rather, like the classic cookbook The Joy of Cooking, you will find well-proven, sensible, and reusable practices. In Software Requirements, you will find the right ingredients and essential practices needed to 'cook' tasty requirements.Software Requirements Overview
Without formal, verifiable software requirements-and an effective system for managing them-the programs that developers think they've agreed to build often will not be the same products their customers are expecting. In SOFTWARE REQUIREMENTS, Second Edition, requirements engineering authority Karl Wiegers amplifies the best practices presented in his original award-winning text?now a mainstay for anyone participating in the software development process.

In this book, you'll discover effective techniques for managing the requirements engineering process all the way through the development cycle-including dozens of techniques to facilitate that all-important communication between users, developers, and management. This updated edition features new case examples, anecdotes culled from the author's extensive consulting career, and specific Next Steps for putting the book's process-improvement principles into practice. You'll also find several new chapters, sample documents, and an incisive troubleshooting guide.

Discover how to:

Set achievable expectations for functionality and quality
NEW: Incorporate business rules into application development
Employ use cases to discover user requirements
Arrest creeping requirements and manage change requests
NEW: Deal with requirements on maintenance, outsourced, and package solution projects
Curb the impulse to "gold-plate" your programs
NEW: Grow effective requirements analysts
Cut revisions-and costs-dramatically
Produce better software!

No matter what kind of software you build, or what your role in the development process, SOFTWARE REQUIREMENTS, Second Edition, delivers expert guidance and field-tested techniques for engineering software success.


Want to learn more information about Software Requirements?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

SQL: Practical Guide for Developers (The Practical Guides) Review

Average Reviews:

(More customer reviews)Are you looking to buy SQL: Practical Guide for Developers (The Practical Guides)? Here is the right place to find the great deals. we can offer discounts of up to 90% on SQL: Practical Guide for Developers (The Practical Guides). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

SQL: Practical Guide for Developers (The Practical Guides) ReviewThis would have been a fair book for a developer's quick reference. It covers many of the broad topics (select, update, nested queries, joins) and does so in a decent fashion. I originally bought this book so that I could have a quick reference nearby that I could look up UNION or other statements that are not used as much.
I was pretty happy with the book as I read through it... that is until the day that I actually had to find a statement in it. I have quite a large collection of computer books and I have never seen anything like it. If you turn to the index page to look up SELECT (I mean... really?) there is no entry there. In fact.. all you see is one page with three columns that have about 20 items per column. And all of this fills about half of the page. Oh wait! There is a little sticker up at the top of this ridiculous page that says "See such and such a webpage for full index".
The worst thing about this index is that it doesn't even have useful entries. It is as if some typesetter had about five minutes before the presses started up and someone said "Hey!!! Billy! We don't have an index! Why don't you randomly look up about 50 words in the book and make a real quick index! No one will know!" Well.. sadly.. Billy didn't have any idea what SQL was except that it starts with an 'S'.
The only reason I give two stars instead of -1 is that it seems that the author made a decent effort to make a simple introduction to SQL for a poor developer who needs a quick source for answers. The only problem is the index will not help someone find that quick answer.
So... I would stay away from this book unless you know that the index which has been posted on the publishers website is actually part of the book.
Bah to MK publishers! All they needed to do was spend two days making an index instead of scrambling and they would have had 4 stars and I wouldn't have tossed this book into the corner behind all of the other disappointing books I have.SQL: Practical Guide for Developers (The Practical Guides) Overview

Want to learn more information about SQL: Practical Guide for Developers (The Practical Guides)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

The Art of Project Management (Theory in Practice (O'Reilly)) Review

Average Reviews:

(More customer reviews)Are you looking to buy The Art of Project Management (Theory in Practice (O'Reilly))? Here is the right place to find the great deals. we can offer discounts of up to 90% on The Art of Project Management (Theory in Practice (O'Reilly)). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

The Art of Project Management (Theory in Practice (O'Reilly)) ReviewAfter many years as project manager in product development, I embarked on two software development projects, a new area for me, and found that some of my management skills were not relevant. After the first project stumbled, I purchased several software project management books and, after working through them in a disciplined way (taking notes on salient points and scaling them on their helpfulness for my work) found this to be the best. It is comprehensive - perhaps a little too wordy at times - and packed with practical advice. The lists of questions which come up regularly in this book can be turned into management check lists. Scott Berkun's points anticipated many of the problems I have since encountered; I am now reading this book for the second time and noticing things that were missed on the first read. As my experience has grown, I have come to recognize the voice of greater experience speaking through this book. Recommended for novices and experienced software project managers.The Art of Project Management (Theory in Practice (O'Reilly)) Overview
The Art of Project Management covers it all--from practical methods for making sure work gets done right and on time, to the mindset that can make you a great leader motivating your team to do their best. Reading this was like reading the blueprint for how the best projects are managed at Microsoft... I wish we always put these lessons into action!" --Joe Belfiore, General Manager, E-home Division, Microsoft Corporation "Berkun has written a fast paced, jargon-free and witty guide to what he wisely refers to as the 'art' of project management.It's a great introduction to the discipline.Seasoned and new managers will benefit from Berkun's perspectives." --Joe Mirza, Director, CNET Networks (Cnet.com) "Most books with the words 'project management' in the title are dry tomes. If that's what you are expecting to hear from Berkun's book, you will be pleasantly surprised. Sure, it's about project management.But it's also about creativity, situational problem-solving, and leadership.If you're a team member, project manager, or even a non-technical stakeholder, Scott offers dozens of practical tools and techniques you can use, and questions you can ask, to ensure your projects succeed." --Bill Bliss, Senior VP of product and customer experience, expedia.com In The Art of Project Management, you'll learn from a veteran manager of software and web development how to plan, manage, and lead projects. This personal account of hard lessons learned over a decade of work in the industry distills complex concepts and challenges into practical nuggets of useful advice. Inspiring, funny, honest, and compelling, this is the book you and your team need to have within arms reach. It will serve you well with your current work, and on future projects to come. Topics include:

How to make things happen
Making good decisions
Specifications and requirements
Ideas and what to do with them
How not to annoy people
Leadership and trust
The truth about making dates
What to do when things go wrong


Want to learn more information about The Art of Project Management (Theory in Practice (O'Reilly))?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

97 Things Every Software Architect Should Know: Collective Wisdom from the Experts Review

Average Reviews:

(More customer reviews)Are you looking to buy 97 Things Every Software Architect Should Know: Collective Wisdom from the Experts? Here is the right place to find the great deals. we can offer discounts of up to 90% on 97 Things Every Software Architect Should Know: Collective Wisdom from the Experts. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

97 Things Every Software Architect Should Know: Collective Wisdom from the Experts ReviewHeavy on keywords and low on actual content / value.
Imagine your Dad rings you up and says, "Be sure to go to work bright and early..." or "The early bird gets the worm" and proceeds to ramble on for 5 minutes about why that is important. We have all been through this kind of lecture. For politeness sake, you bite your tongue and zone out.
Now replace Dad with Bill Gates/ Steve Jobs/ some famous architect. However the advice being doled out is similar. eg. "Be sure to have a decent UI for every component/ blah blah blah".
How would you feel if you had to read 97 articles by famous architects / tech gurus, each 2 pages long and the entire content of the article is in the first introductory line itself. The rest is fluff.
I don't know about you, but when I am paying 20+ dollars for a book, I expect more than simple fluff.
-V97 Things Every Software Architect Should Know: Collective Wisdom from the Experts Overview
In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de hOra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as:



Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar)
Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm)
Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards)
Simplicity Before Generality, Use Before Reuse (Kevlin Henney)
For the End User, the Interface Is the System (Vinayak Hegde)
It's Never Too Early to Think About Performance (Rebecca Parsons)

To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.


Want to learn more information about 97 Things Every Software Architect Should Know: Collective Wisdom from the Experts?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...