Chapter 1. Philosophies of data science

 

This chapter covers

  • The role of a data scientist and how it’s different from that of a software developer
  • The greatest asset of a data scientist, awareness, particularly in the presence of significant uncertainties
  • Prerequisites for reading this book: basic knowledge of software development and statistics
  • Setting priorities for a project while keeping the big picture in mind
  • Best practices: tips that can make life easier during a project

In the following pages, I introduce data science as a set of processes and concepts that act as a guide for making progress and decisions within a data-centric project. This contrasts with the view of data science as a set of statistical and software tools and the knowledge to use them, which in my experience is the far more popular perspective taken in conversations and texts on data science (see figure 1.1 for a humorous take on perspectives of data science). I don’t mean to say that these two perspectives contradict each other; they’re complementary. But to neglect one in favor of the other would be foolish, and so in this book I address the less-discussed side: process, both in practice and in thought.

Figure 1.1. Some stereotypical perspectives on data science

1.1. Data science and this book

 
 
 

1.2. Awareness is valuable

 
 
 

1.3. Developer vs. data scientist

 
 
 

1.4. Do I need to be a software developer?

 

1.5. Do I need to know statistics?

 
 

1.6. Priorities: knowledge first, technology second, opinions third

 
 
 

1.7. Best practices

 
 
 

1.8. Reading this book: how I discuss concepts

 
 

Summary

 
 
 
sitemap

Unable to load book!

The book could not be loaded.

(try again in a couple of minutes)

manning.com homepage
test yourself with a liveTest