What Modern Data Science Really Means - Python and R Book Preface

The preface of “Python and R for the Modern Data Scientist” sets up the whole book in a few pages. And it does something rare for a tech book. It actually defines what it means by its own title.

So here’s what happened. Rick Scavetta and Boyan Angelov got tired of the Python vs R debate. Not because they didn’t care, but because they thought it was the wrong conversation. Their argument is simple: a good craftsperson picks the right tool for the job. If all you have is a hammer, everything looks like a nail. They call it Maslow’s hammer, and it describes a lot of the data science community.

Why They Wrote This Book

The authors didn’t set out to write a bilingual dictionary for Python and R. Well, not only that. There is a translation appendix in the back, but the real goal was changing how data scientists think about their tools.

Here’s the thing. Being deliberate about your tool choices makes you more productive. Not picking one tool and sticking with it forever. Not jumping on whatever is trendy. Understanding your options and making informed decisions based on the actual problem you’re solving.

The “language wars” between Python and R have been going on for years, and the authors think those wars stopped being useful a long time ago. Real work happens in real contexts, and contexts change. What works for a statistics-heavy research project might not work for deploying a model in production.

What “Modern” Actually Means

The word “modern” in the title is doing a lot of heavy lifting. Scavetta and Angelov don’t just mean “new” or “current.” They lay out six principles that define modern data science:

Collective. Data science doesn’t happen in a vacuum. It’s integrated into teams and organizations. Jargon should build bridges, not walls.

Simple. Reduce unnecessary complexity in your methods, your code, and your communication. If something can be simpler, make it simpler.

Accessible. Your process should be open enough that others can evaluate, understand, and improve it. No black boxes.

Generalizable. The fundamental tools and concepts should apply across many domains. If your approach only works in one narrow context, it’s too brittle.

Outward looking. Good data science pulls ideas from other fields. It doesn’t stay locked inside its own bubble.

Ethical and honest. This is people-oriented work. It considers consequences for communities and society. It avoids hype and fads that only serve short-term gains.

That last point hit me. In a field obsessed with the next big thing, calling out hype and fads as something to actively avoid is a strong stance. And an honest one.

Technical Interactions

One concept from the preface stuck with me: technical interactions. When you accept that no single tool can handle everything, you create complexity. You have to think about programming languages, packages, naming conventions, project structures, IDEs, text editors. The list goes on.

But here’s the problem. Every one of those choices can either build a bridge or build a barrier. Picking an obscure tool because you personally like it might cut you off from your team. Using a common framework might mean trade-offs, but it lets everyone collaborate.

The authors say the challenge is balancing personal preference with communal accessibility. Your tool choices aren’t just about you. They affect everyone who works with your code, your data, and your outputs.

And this isn’t just about “hard” skills like picking Python or R. Communication matters too. How you write docs, present results, explain your methods. All of these are technical interactions that either bring people closer or push them away.

Who Is This Book For

The book targets intermediate data scientists who already know at least one of the two languages and want to learn the other. It’s not trying to teach data science from scratch.

But early-career data scientists can benefit too. Seeing what’s possible in a bilingual context before you commit to one tool gives you a broader perspective from the start.

How the Book Is Organized

Here’s a neat detail. The authors structured the book like learning a second spoken language as an adult.

Part I covers the origins of Python and R, like studying the etymology of a language. Part II is where you start learning: R for Python users, then Python for R users. The authors warn against two temptations: constantly saying “well, in MY language this is easier” and translating everything word for word. Some things don’t map 1:1 between languages, and that’s a feature, not a bug.

Part III covers when to use which language. Part IV is where the two languages work together in a single workflow. Not side by side. Together. The authors compare it to code-switching in bilingual communities, where you mix languages because one word sometimes captures meaning better than the other language can.

My Take

Most book prefaces are skippable. This one is not. It establishes a philosophy. The six principles of modern data science feel timeless even though the specific tools will change. And the framing of tool choices as bridges or barriers is something every data professional should think about.

The preface sets expectations clearly: this is not a book about Python vs R. It’s a book about Python and R.

Previous: Book Retelling Introduction | Next: Chapter 1 - Origins of Python and R