—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
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.
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 understandingHow 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
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.
Is your code easy to change? Can you get nearly instantaneous feedback when you do change it? Do you understand it? If the answer to any of these questions is no, you have legacy code, and it is draining time and money away from your development efforts.
In this book, Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. This book draws on material Michael created for his renowned Object Mentor seminars: techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control.
The topics covered includeUnderstanding the mechanics of software change: adding features, fixing bugs, improving design, optimizing performance Getting legacy code into a test harness Writing tests that protect you against introducing new problems Techniques that can be used with any language or platform—with examples in Java, C++, C, and C# Accurately identifying where code changes need to be made Coping with legacy systems that aren't object-oriented Handling applications that don't seem to have any structure
This book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.
Pioneering the Future of Software Test
Do you need to get it right, too? Then, learn from Google. Legendary testing expert James Whittaker, until recently a Google testing leader, and two top Google experts reveal exactly how Google tests software, offering brand-new best practices you can use even if you’re not quite Google’s size…yet!
Breakthrough Techniques You Can Actually Use
Discover 100% practical, amazingly scalable techniques for analyzing risk and planning tests…thinking like real users…implementing exploratory, black box, white box, and acceptance testing…getting usable feedback…tracking issues…choosing and creating tools…testing “Docs & Mocks,” interfaces, classes, modules, libraries, binaries, services, and infrastructure…reviewing code and refactoring…using test hooks, presubmit scripts, queues, continuous builds, and more. With these techniques, you can transform testing from a bottleneck into an accelerator–and make your whole organization more productive!