Getting in Front on Data: Who Does What

Technics Publications
Free sample

 This is the single best book ever written on data quality.  Clear, concise, and actionable.  We all want to leverage our data resources to drive growth, but we too often ignore the fundamentals of data quality, which almost always inhibits our success.  Tom lays out a clear path for each organization to holistically improve not only its data quality, but more importantly the performance of its business as a whole.

 —Jeffrey G. McMillan, Chief Analytics and Data Officer, Morgan Stanley

 

This book lays out the roles everyone, up and down the organization chart, can and must play to ensure that data is up to the demands of its use, in day-in, day-out work, decision-making, planning, and analytics.

 

By now, everyone knows that bad data extorts an enormous toll, adding huge (though often hidden) costs, and making it more difficult to make good decisions and leverage advanced analyses.  While the problems are pervasive and insidious, they are also solvable!  As Tom Redman, “the Data Doc,” explains in Getting in Front on Data, the secret lies in getting the right people in the right roles to “get in front” of the management and social issues that lead to bad data in the first place.

 

Everyone should see himself or herself in this book.  We are all both data customers and data creators—after all, we use data created by others and create data used by others.   And all of us must step up to these roles.   As data customers, we must clarify our most important needs and communicate them to data creators.  As data creators, we must strive to meet those needs by finding and eliminating the root causes of error. 

 

Getting in Front on Data proposes new roles for data professionals as:

embedded data managers, in helping data customers and creators complete their work, DQ team leads, in connecting customers and creators, pulling the entire program together, and training people on their new roles, data maestros, in providing deep expertise on the really tough problems, chief data architects, in establishing common data definitions, and technologists, in increasing scale and decreasing unit cost. 

 

Getting in Front on Data introduces a new role, the data provocateur, the motive force in attacking data quality properly!  This book urges everyone to unleash their inner provocateur. 

 

Finally, it crystallizes what senior leaders must do if their entire organizations are to enjoy the benefits of high-quality data!

 

Data quality has always been important. But now, in the growing digital economy where business transactions and customer experiences are automated and tailored, data quality is critical. This book comes just in time.

—Maria C. Villar, Global Vice President, SAP America, Inc.

 

Winning, and more importantly thriving, in the digital age requires more than stating “Data is a strategic corporate asset.” Leaders and organizations need a plan of action to make the new vision a reality.  Tom's latest book is a how-to for those seeking that reality.

—Bob Palermo, Vice President, Performance Excellence, Shell Unconventionals

 

Many, if not most, companies still struggle with their data. With his latest offering, Tom Redman sets out a path they can follow to Get in Front on Data. Based on his decades of experience working with many companies and individuals, this is the most practical guide around. A must read for data professionals, and especially data “provocateurs”.

—Ken Self, President IAIDQ

 

This book offers a unique perspective on how to think about data and address Data Quality – offering practical guidance and useful instruction from the perspective of each stakeholder. The process – and processes – to go from business need to having the right quality data to address that need is no small task.

—John Nicodemo, Global Leader, Data Quality, Dun & Bradstreet

 

Getting in Front on Data is a clearly written survival handbook for the new data-driven economy. It is a “must read” for the employees of any organization expecting to remain relevant and competitive. The “Data Doc” has an extraordinary talent for explaining key concepts with simple examples and understandable analogies making it accessible to everyone in their organization regardless of their role.

—John R. Talburt, Director of the Information Quality Graduate Program University of Arkansas at Little Rock

Read more

About the author

 Tom Redman, the Data Doc, and his company, Data Quality Solutions, help leaders world-wide attack data quality head-on.  Thousands benefit from his approaches and methods, which focus on getting the right people in the right roles, creating data correctly the first time, and addressing the issues that lead to bad data.   Tom started his career at Bell Labs, where he conceived and led the Data Quality Lab. He was first to understand the fundamental importance of data and data quality, understand the nature of data in organizations, and give meaning to the phrase "manage data assets." He has a Ph.D.  in Statistics and two patents.  Tom and his wife Nancy live in Rumson, New Jersey, USA.

Read more
Loading...

Additional Information

Publisher
Technics Publications
Read more
Published on
Sep 12, 2016
Read more
Pages
190
Read more
ISBN
9781634621281
Read more
Language
English
Read more
Genres
Business & Economics / Human Resources & Personnel Management
Business & Economics / Information Management
Computers / Software Development & Engineering / Quality Assurance & Testing
Read more
Content Protection
This content is DRM protected.
Read more
Read Aloud
Available on Android devices
Read more

Reading information

Smartphones and Tablets

Install the Google Play Books app for Android and iPad/iPhone. It syncs automatically with your account and allows you to read online or offline wherever you are.

Laptops and Computers

You can read books purchased on Google Play using your computer's web browser.

eReaders and other devices

To read on e-ink devices like the Sony eReader or Barnes & Noble Nook, you'll need to download a file and transfer it to your device. Please follow the detailed Help center instructions to transfer the files to supported eReaders.
Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way.

Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code “on the fly” into a book that will instill within you the values of a software craftsman and make you a better programmer–but only if you work at it.

What kind of work will you be doing? You’ll be reading code–lots of code. And you will be challenged to think about what’s right about that code, and what’s wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.

Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code–of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and “smells” gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code.

Readers will come away from this book understanding
How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
The Robert C. Martin Clean Code Collection consists of two bestselling eBooks: Clean Code: A Handbook of Agile Software Craftmanship The Clean Coder: A Code of Conduct for Professional Programmers

In Clean Code, legendary software expert Robert C. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code “on the fly” into a book that will instill within you the values of a software craftsman and make you a better programmer--but only if you work at it. You will be challenged to think about what’s right about that code and what’s wrong with it. More important, you will be challenged to reassess your professional values and your commitment to your craft.

In The Clean Coder, Martin introduces the disciplines, techniques, tools, and practices of true software craftsmanship. This book is packed with practical advice--about everything from estimating and coding to refactoring and testing. It covers much more than technique: It is about attitude. Martin shows how to approach software development with honor, self-respect, and pride; work well and work clean; communicate and estimate faithfully; face difficult decisions with clarity and honesty; and understand that deep knowledge comes with a responsibility to act.

Readers of this collection will come away understanding

How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development What it means to behave as a true software craftsman How to deal with conflict, tight schedules, and unreasonable managers How to get into the flow of coding and get past writer’s block How to handle unrelenting pressure and avoid burnout How to combine enduring attitudes with new development paradigms How to manage your time and avoid blind alleys, marshes, bogs, and swamps How to foster environments where programmers and teams can thrive When to say “No”--and how to say it When to say “Yes”--and what yes really means
Practical Software Architecture Solutions from the Legendary Robert C. Martin (“Uncle Bob”)

By applying universal rules of software architecture, you can dramatically improve developer productivity throughout the life of any software system. Now, building upon the success of his best-selling books Clean Code and The Clean Coder, legendary software craftsman Robert C. Martin (“Uncle Bob”) reveals those rules and helps you apply them.

Martin’s Clean Architecture doesn’t merely present options. Drawing on over a half-century of experience in software environments of every imaginable type, Martin tells you what choices to make and why they are critical to your success. As you’ve come to expect from Uncle Bob, this book is packed with direct, no-nonsense solutions for the real challenges you’ll face–the ones that will make or break your projects.

Learn what software architects need to achieve–and core disciplines and practices for achieving it Master essential software design principles for addressing function, component separation, and data management See how programming paradigms impose discipline by restricting what developers can do Understand what’s critically important and what’s merely a “detail” Implement optimal, high-level structures for web, database, thick-client, console, and embedded applications Define appropriate boundaries and layers, and organize components and services See why designs and architectures go wrong, and how to prevent (or fix) these failures

Clean Architecture is essential reading for every current or aspiring software architect, systems analyst, system designer, and software manager–and for every programmer who must execute someone else’s designs.


Register your product for convenient access to downloads, updates, and/or corrections as they become available.

This is a practical guide for software developers, and different than other software architecture books. Here's why:

It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face.

It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties.

It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts.

It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail.

It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.
©2018 GoogleSite Terms of ServicePrivacyDevelopersArtistsAbout Google|Location: United StatesLanguage: English (United States)
By purchasing this item, you are transacting with Google Payments and agreeing to the Google Payments Terms of Service and Privacy Notice.