 | 
Author : Dr. Taylor Hartman
Edition : Rev Upd
Number of Pages : 336
Publisher : Scribner
List Price : $16.00
Amazon Price : $4.79
Used Price : $3.99 |
Product Description
In his life-changing book, Dr. Taylor Hartman introduces you to the People Code and why people do what they do. The concept of Motive is a fresh method for analyzing your own innate personality as well as that of those around you. You then have the ability to utilize that knowledge to improve workplace and personal relationships. As an author, psychologist, and leadership coach, Dr. Hartman offers a remarkably astute system for segmenting everyone into specific Motive-types denoted by a color: Red (power wielders), Blue (do-gooders), White (peacekeepers), and Yellow (fun lovers). He then explains how to ensure that all possible alliances between them function at optimum effectiveness. If you struggle with self-acceptance and have questions about why you and others act the way you do, Dr. Hartman and
The People Code can help you maximize your life success by improving your day-to-day relationships.
Customer reviews
Very Beneficial! 
by .. R. Rowley (Texas)
The Color Code has been so beneficial that I purchased it after borrowing and reading the library copy. Identifying my color helps me understand my strengths and weaknesses. I also keep it handy to help me understand other people. By understanding their color, it helps me relate on their wave length. I have used other personality tests before, but The Color Code was clear and easy to apply. Dr. Hartman keeps you engaged with humor and real life application you can relate to.
Excellent Resource into Relationships and Self-Awareness by .. Book Lover (Fort Mill, SC)
I use this book all the time to understand myself and others. This is extremely helpful in dealing with life situations. I believe in the premise that each of us have core individual needs that must be met. And, most importantly, that to be a 'whole' person one must be able to integrate the positive aspects of all the personality colors to live a happier life. It just makes sense to me.
Addicting 
by .. Emily J. Taylor (Utah)
This book helped me realize that I was a Core White with a secondary Blue. That's just exciting.
Now for the real review: I happen to find Hartman's system brilliant. He leaves plenty of room for individuality, but has still managed to find specific characteristics that dominate society and group them into four basic patterns. He also takes care to explain his theory and why it works in real life. With that are plenty of anctedotes of patients with whom he has worked, all that human intereraction to solidify these personalities.
The quiz is easy, but complex and varying, managing to cover many parts of a person. After that are the descriptions of each color, both positive and negative. After that he expands into relationships, work, personal improvement, you name it--the goal of making our individual personalities work. It's all very practical for understanding ourselves and how we work with others.
It's informative, insightful, and just plain fun. Most of all, it's very logical.
This book literally changed my life! by .. Debbie (Ogden, Utah USA)
I am a Registered Nurse and I was working at a hospital as a "quality assurance utilization manager" when a co-worker gave me this book. I was in the 13th year of my career and had always received great annual reviews from supervisors regarding the quality of my work. After working in this new administrative job for a year I got one of the lowest evaluations of my entire working life - after I had put more time, energy and passion into this new job than I had in any of my previous positions!
After I read this excellent book (back in 1991) I immediately understood the problem: My boss was a "Red" and "Yellow" personality, driven by power and craving focused attention. My personality is "White" and "Blue" so I seek peace and intimacy. Trust me - it was not a good fit! Thankfully I was able to quit my job and become a full-time parent to my two sweet children.
Fast forward seventeen years.....
My children are now 21 and 22 years old and attending college. They have been raised on the "Color Code" concepts and it has dramatically improved the quality of their interactions with family, friends, teachers and other acquaintances. My daughter has an intense "blue & yellow" personality (like my husband) and my son is "white and yellow" - which must be the most laid back personality on the planet! I am not exaggerating when I say that I use the concepts in this book every single day.
Thank you Taylor Hartman for your most excellent book!
Life changing book by .. Marla (CA USA)
I am amazed by this book. As I read the chapter on my personality color, I couldn't believe that the author had me figured out down to the very nuances of my behavior. This book has helped me view others with more understanding and forgiveness. You will never look at people the same way again. Every person I know who has read this book can't stop talking about it. It goes down as one of my favorite books ever. Your relationships will improve as a result. This book is a must read for all and a perfect wedding gift.
Related Search :
s innate ,
people code ,
motive  |
Author : Patrick Cauldwell
Number of Pages : 233
Publisher : Wrox
List Price : $39.99
Amazon Price : $14.50
Used Price : $14.25 |
Product Description
This book is for the career developer who wants to take his or her skill set and/or project to the next level. If you are a professional software developer with 3–4 years of experience looking to bring a higher level of discipline to your project, or to learn the skills that will help you transition from software engineer to technical lead, then this book is for you. The topics covered in this book will help you focus on delivering software at a higher quality and lower cost. The book is about practical techniques and practices that will help you and your team realize those goals.
This book is for the developer understands that the business of software is, first and foremost, business. Writing code is fun, but writing high-quality code on time and at the lowest possible cost is what makes a software project successful. A team lead or architect who wants to succeed must keep that in mind.
Given that target audience, this book assumes a certain level of skill at reading code in one or more languages, and basic familiarity with building and testing software projects. It also assumes that you have at least a basic understanding of the software development lifecycle, and how requirements from customers become testable software projects.
Who This Book Is Not For: This is not a book for the entry-level developer fresh out of college, or for those just getting started as professional coders. It isn’t a book about writing code; it’s a book about how we write code together while keeping quality up and costs down. It is not for those who want to learn to write more efficient or literate code. There are plenty of other books available on those subjects, as mentioned previously.
This is also not a book about project management or development methodology. All of the strategies and techniques presented here are just as applicable to waterfall projects as they are to those employing Agile methodologies. While certain strategies such as Test-Driven Development and Continuous Integration have risen to popularity hand in hand with Agile development methodologies, there is no coupling between them. There are plenty of projects run using SCRUM that do not use TDD, and there are just as many waterfall projects that do.
Philosophy versus Practicality: There are a lot of religious arguments in software development. Exceptions versus result codes, strongly typed versus dynamic languages, and where to put your curly braces are just a few examples. This book tried to steer clear of those arguments here. Most of the chapters in this book deal with practical steps that you as a developer can take to improve your skills and improve the state of your project. The author makes no claims that these practices represent the way to write software. They represent strategies that have worked well for the author and other developers that he have worked closely with.
Philosophy certainly has its place in software development. Much of the current thinking in project management has been influenced by the Agile philosophy, for example. The next wave may be influenced by the Lean methodologies developed by Toyota for building automobiles. Because it represents a philosophy, the Lean process model can be applied to building software just as easily as to building cars. On the other hand, because they exist at the philosophical level, such methodologies can be difficult to conceptualize. The book tries to favor the practical over the philosophical, the concrete over the theoretical. This should be the kind of book that you can pick up, read one chapter of, and go away with some practical changes you can make to your software project that will make it better.
That said, the first part of this book is entitled “Philosophy” because the strategies described in it represent ways of approaching a problem rather than a specific solution. There are just as many practical ways to do Test-Driven Development as there are ways to manage a software project. You will have to pick the way that fits your chosen programming language, environment, and team structure. The book has tried to describe some tangible ways of realizing TDD, but it remains an abstract ideal rather than a one-size-fits-all technical solution. The same applies to Continuous Integration. There are numerous ways of thinking about and achieving a Continuous Integration solution, and this book presents only a few. Continuous Integration represents a way of thinking about your development process rather than a concrete or specific technique.
The second and third parts represent more concrete process and construction techniques that can improve your code and your project. They focus on the pragmatic rather than the philosophical.
Every Little Bit Helps: You do not have to sit down and read this book from cover to cover. While there are interrelationships between the chapters, each chapter can also stand on its own. If you know that you have a particular problem such as error handling with your current project, read that chapter and try to implement some of the suggestions in it. Don’t feel that you have to overhaul your entire software project at once. The various techniques described in this book can all incrementally improve a project one at a time.
If you are starting a brand new project and have an opportunity to define its structure, then by all means read the whole book and see how it influences the way you design your project. If you have to work within an existing project structure, you might have more success applying a few improvements at a time.
In terms of personal career growth, the same applies. Every new technique you learn makes you a better developer, so take them one at a time as your schedule and projects allow.
Examples: Most of the examples in this book are written in C#. However, the techniques described in this book apply just as well to any other modern programming language with a little translation. Even if you are unfamiliar with the inner workings or details of C# as a language, the examples are very small and simple to understand. Again, this is not a book about how to write code, and the examples in it are all intended to illustrate a specific point, not to become a part of your software project in any literal sense.
This book is organized into three sections, Philosophy, Process and Code Construction. The following is a short summary of what you will find in each section and chapter.
Part I (Philosophy) contains chapters that focus on abstract ideas about how to approach a software project. Each chapter contains practical examples of how to realize those ideas.
Chapter 1 (Buy, not Build) describes how to go about deciding which parts of your software project you need to write yourself and which parts you may be able to purchase or otherwise leverage from someplace else. In order to keep costs down and focus on your real competitive advantage, it is necessary to write only those parts of your application that you really need to.
Chapter 2 (Test-Driven Development) examines the Test-Driven Development (or Test-Driven Design) philosophy and some practical ways of applying it to your development lifecycle to produce higher-quality code in less time.
Chapter 3 (Continuous Integration) explores the Continuous Integration philosophy and how you can apply it to your project. CI involves automating your build and unit testing processes to give developers a shorter feedback cycle about changes that they make to the project. A shorter feedback cycle makes it easier for developers to work together as a team and at a higher level of productivity.
The chapters in Part II (Process) explore processes and tools that you can use as a team to improve the quality of your source code and make it easier to understand and to maintain.
Chapter 4 (Done Is Done) contains suggestions for defining what it means for a developer to “finish” a development task. Creating a “done is done” policy for your team can make it easier for developers to work together, and easier for developers and testers to work together. If everyone on your team follows the same set of steps to complete each task, then development will be more predictable and of a higher quality.
Chapter 5 (Testing) presents some concrete suggestions for how to create tests, how to run them, and how to organize them to make them easier to run, easier to measure, and more useful to developers and to testers. Included are sections on what code coverage means and how to measure it effectively, how to organize your tests by type, and how to automate your testing processes to get the most benefit from them.
Chapter 6 (Source Control) explains techniques for using your source control system more effectively so that it is easier for developers to work together on the same project, and easier to correlate changes in source control with physical software binaries and with defect or issue reports in your tracking system.
Chapter 7 (Static Analysis) examines what static analysis is, what information it can provide, and how it can improve the quality and maintainability of your projects.
Part III (Code Construction) includes chapters on specific coding techniques that can improve the quality and maintainability of your software projects.
Chapter 8 (Contract, Contract, Contract!) tackles programming by contract and how that can make your code easier for developers to understand and to use. Programming by contract can also make your application easier (and therefore less expensive) to maintain and support.
Chapter 9 (Limiting Dependencies) focuses on techniques for limiting how dependent each part of your application is upon the others. Limiting dependencies can lead to software that is easier to make changes to and cheaper to maintain as well as easier to deploy and test.
Chapter 10 (The Model-View-Presenter Model) offers a brief descr...
Customer reviews
Good Book; Would Liked to Have Seen More 
by .. Brian Mains ()
This book tries to get any leader of a project in any type of role up to speed on the latest technologies, concepts, or decisions that a code leader has to go through, such as build vs. buy, whether TDD practices are practical, or the value of limiting dependencies.
This book does discuss code, but isn't full of code samples because it isn't meant to be a development book; rather, it looks at the practicalities at a higher level to discuss the rational for using or not using a technology or technique. Overall, the book is a quick read, covering several topics and delving into some specifics, but only discussing a few topics in different arenas. For instance, the MVP design pattern is discussed, but this design pattern is the only pattern discussed in detail in the book.
I did find the section on creating unit/integration tests especially useful because the boundaries in my unit tests were a little gray, some being complete unit tests, while some falling under the integration test scenario, and the detailed explanation about this approach. No good application goes without source control, analysis tools (on some occasions), and tracing capabilities, and Patrick discusses each of these with good details about how a project can make the most of these points. He gets pretty detailed about the options that an application can make use of with source control, and brings light to statistical analysis capabilities in the tools on the market.
I would have like to see this book go further with what the book covered. It's a quick read (232 pages) and is generally easy to read, but there are a lot of other important topics that come with software design I wish were included.
Develop better software now by .. Eric Kassan (Las Vegas, NV USA)
This book does a fantastic job of presenting auxiliary processes in the software development lifecycle (processes such as unit testing, source control, continuous integration, etc.). It clearly explains the value in each process it describes, as well as various tools and options to consider. It also suggests aspects of software development itself such as the MVP (Model View Presenter) pattern, contract usage, tracing, and error handling. As with the processes, these aspects are presented clearly, objectively, and with common options and variations spelled out.
Useful for self-taught programmers by .. Reinis (Los Angeles, CA)
I got this book because i'm completely self-taught in programming (including mostly Wrox books) and I thought it would be useful to get more background.
I was right. I've learnt a lot about how the programming, testing, versioning process works in general, as well as some specific issues that come up with the different methods. So for me it was useful.
If you have been working with programming in a business capacity already, or are certified/graduated in IT, this probably is below your level, although it's always nice to check if there are other ways of doing thing that you may want to think about.
Round Out Your Skills by .. Travis Illig (Portland, OR United States)
"Code Leader" is a book for developers who have been on a few projects and are ready to take that next step beyond just the "code" part of "coding." The book covers topics like when to build components vs. when to buy them, good testing practices, automating your build, and analyzing your code to learn where to improve it. Each topic is addressed at a reasonable pace, not miring you in super-low-level detail but providing enough information to get the point across.
As you read it, you'll find that much of it sounds like common sense, like some long-forgotten tidbit that you didn't realize you already knew. That's the strength of the book - bringing those things to light and showing you the benefits. The best example of this is the "Done is Done" chapter, bringing up the idea that sometimes when a developer says that a task is "done," there really are things left to do... and ideas on how to solve that so when someone says something is "done," all of the i's are dotted and t's are crossed.
At the end, the book brings all of the lessons together in a case study showing a developer performing a task from beginning to end and using the tenets described in the book. It's a good way to put everything into perspective and solidifies the concepts.
If you already practice things like test-driven devleopment and continuous integration; if you already know about the benefits of the MVP/MVC patterns (and use them); if you already know what dependency injection is and how it affects your testability; if you've got some nicely structured source control policies and do branch/merge per task (and know why that's good)... you may not get as much out of this book. You're probably already doing most of the stuff discussed and don't need to be sold a car you've already bought (so to speak).
Only two technical downsides to this book:
First, while the content could apply to any software development project in any technology, most of the tools mentioned and code samples are specifically .NET-oriented. That may be a little off-putting to non-.NET developers, but if you can get past that, you'll be rewarded.
Second, the text is abnormally small. I compared it to some of the other Wrox books I've got and there's got to be a two-or-three point size difference here, which makes the book lightweight but might give you a little eyestrain.
If you're looking for complementary books to this one, check out Coder to Developer: Tools and Strategies for Delivering Your Software by Mike Gunderloy. The two offer similar types of advice - ways to go beyond "just coding" and take your projects to the next level. While there are some overlapping topics, the two really are more complementary, each offering great guidance to help you sharpen your saw.
Related Search :
code leader ,
tools processes ,
programmer  |
Author : Lillian Glass
Number of Pages : 272
Publisher : Wiley
List Price : $14.95
Amazon Price : $4.98
Used Price : $4.93 |
Product Description
"A practical and savvy guide."
–– Gavin de Becker, #1 New York Times bestselling author of The Gift of Fear
"Understanding nonverbal language is the essential skill in any profession that involves communication. This book is the best primer on the topic of nonverbal communication I have ever read."
–– Geoffrey N. Fieger, noted trial attorney
"As a regular contributor to and commentator on Court TV, Dr. Lillian Glass has repeatedly demonstrated her exceptional professional skills of reading people in our on-air coverage of several trials. In this book, she shares with readers these skills, which could prove to be invaluable in every aspect of your life."
–– Nancy Grace, Court TV
"A must-read for everyone, whether they are in business or not. Applause to Dr. Glass for giving the public such an important work."
–– Arnold Kopelson, motion picture producer
Knowing how to read people–– picking up on and interpreting their hidden cues–– is a tremendous asset for virtually anything you do. In I Know What You’re Thinking, psychologist, bestselling author, and communications expert Dr. Lillian Glass helps you develop a tremendous new set of skills that will make you more perceptive, more powerful, and more successful. As she has done for her numerous clients, Dr. Glass shows you–– step by step–– how to gain the power to know the truth about people. Through simple quizzes and easy-to-follow exercises, you’ll learn to improve your judgment of others and make better decisions while projecting confidence, sincerity, and strength. With this fun, down-to-earth guide, you’ll be able to look anyone in the eye with a quiet self-assurance that says I Know What You’re Thinking.
Customer reviews
so interesting by .. loma ()
it is a very interesting book , full of knowledge and excitement... it worths every minute of reading .
Interesting reading by .. D. Jenkins (Clarksville, IN USA)
I paint and got this to understand people to make a point in my paintings. It is real entertaining. Enjoy!
The other reviewers are right on 
by .. Angela Siegel (Charlotte, NC)
Unfortunately, I bought the book while browsing, rather than doing my usual checkups on Amazon.
I like that the author approaches the four different aspects of reading people to give an overall sense of the person, rather than just focusing on body language or personality by itself. If I can find another book on the same subject but written better, then I'd love to read it. But I had to skim past the inane quizzes, the arrogant examples, and the oversimplified explanations. In doing so, I think I may have missed a few of the good points she probably makes. I know I'll try to re-read it, because there are some good things in the book, they're just more difficult to find.
Agree with others - fluff and arrogance 
by .. Nancy Beale (Kansas, USA)
I agree with the other reviewers in labeling this book as "fluff" and an opportunity for the author to talk about how great she is. She uses extreme categories liberally throughout this book - trying to pigeon-hole people into descriptive categories that are narrow and negative. For someone with a terminal degree, she provided not one reference or citation to studies that she referred to while attempting to validate her points. This book is not scientifically based and there is NO way that Oprah would have this woman or her book on her show!
reading this book by .. Charles F. Sinclair (Oklahoma)
Buying this book is a waste of money. Reading this book is a waste of time. The author is evidently narcissitic. The author is not shy about dropping names of the famous people she has treated. All the examples are of famous and affluent people she knows. The thoughts are only partially developed. She begins a subject and leaves you hanging. The chapters are very generic and things you already know. The book is an advertisement for herself and at the back she has a full page devoted to contacting her to do business with her. Your money and time would be well spent looking elsewhere for help on this subject.
Related Search :
reading people ,
thinking using ,
four codes 
