Part 1: Getting Started with Python

Chapters 1–8

You already know how to work. You know how to open a spreadsheet, build a pivot table, filter a dataset, and wrangle columns into something presentable. You have been doing this for years, possibly decades, and you are good at it. That competence is real, and this book will not ask you to abandon any of it.

What it will ask you to do is add one more skill — a skill that will feel genuinely strange for the first few weeks, and then, almost without you noticing, will start to feel like something you have always had.

Where You Are Right Now

Before you write a single line of code, it is worth being honest about the starting point.

You are a business professional who works with data. Maybe you are an analyst who spends Monday mornings consolidating reports. Maybe you are a consultant who tracks client work across three separate spreadsheets that were never really designed to talk to each other. Maybe you are a manager who needs numbers faster than your team can produce them. Whatever your specific situation, you have probably bumped against the ceiling of what your current tools can do. A file that is too big. A task that takes too long. A process that could not possibly be more manual and yet somehow still is.

You have heard that Python can help with this. You are not entirely sure what Python is or whether it is really for someone like you. You may have tried to learn it once before, gotten through the Hello World example, and then found yourself looking at a tutorial that wanted you to sort a list of integers and wondered what any of it had to do with your actual work.

This book was written for exactly that experience. The frustration is valid. The solution is here.

What Part 1 Actually Is

Part 1 is eight chapters. It covers the foundations: not just the syntax of Python, but the reasoning behind it. Why Python is worth your time. How to set up an environment that does not fight you. What variables, data types, and operators mean in business terms. How to encode decision logic into code. How to automate repetition. How to build reusable tools. How to store and work with collections of business data. And — critically — how to write code that does not catastrophically fail the moment real-world data misbehaves.

None of these chapters assume any prior programming experience. They do assume that you are a capable adult who can follow a logical argument and is willing to type things and see what happens.

The order matters. Each chapter builds on what came before. Chapter 3 on basics sets up Chapter 4 on control flow, which sets up Chapter 5 on loops, which sets up Chapter 6 on functions, and so on. This is not a collection of standalone topics you can read in any order — it is a designed progression. Following it is one of the higher-leverage things you can do.

The Learning Curve Ahead: An Honest Assessment

There is a particular experience that almost everyone goes through in the first few weeks of learning Python, and it is useful to name it in advance so that when you encounter it, you recognize it for what it is rather than interpreting it as evidence that you cannot do this.

The experience is: the first week or two are disorienting. The syntax is unfamiliar. The error messages are cryptic. The concepts do not quite connect to anything you already know. You will type something that looks correct and it will fail. You will fix one error and produce another. You will spend twenty minutes on something that, in hindsight, required changing one character.

This is normal. This is not a sign of inadequacy. This is what learning a new skill feels like before the neural pathways exist.

The experience changes around week three or four. The connections start forming. You begin to recognize patterns. You stop having to look up every piece of syntax. More importantly, you begin to write code that does something real — something that saves you time, or produces an output that would have taken an hour in Excel, or automates a step that you used to do by hand. When that happens for the first time, the disorientation transforms into something else entirely.

Push through weeks one and two. The return starts in week three.

Meet Priya and Maya

Two characters will accompany you through all forty chapters of this book. They are worth introducing here, because you will be seeing a great deal of them.

Priya Okonkwo is a junior analyst at Acme Corp, a mid-sized regional distributor of office supplies with four regional offices and a legacy IT infrastructure stitched together with Excel files and good intentions. Priya is 18 months into her first job out of college. She is smart, competent, and spending an embarrassing fraction of her Monday mornings manually consolidating the same four CSV files into the same weekly report that Sandra Chen, the VP of Sales, needs by nine o'clock. Priya's boss Marcus, the IT manager, has been skeptical of "another thing to maintain," but he is watching with interest.

At the start of Part 1, Priya has no Python experience. She has Excel skills, a sharp analytical instinct, and a weekly report that is eating her mornings.

Maya Reyes is a freelance business consultant three years into her own practice. She manages twelve active client relationships and tracks everything — projects, hours, invoices, pipeline — across three separate spreadsheets that do not communicate with each other. She has been meaning to "get more organized" for two years. She bills at a solid rate and is leaving money on the table not because of the quality of her work but because her business infrastructure is a collection of workarounds.

At the start of Part 1, Maya is exactly where many solo professionals are: the data exists, the need is clear, and the missing piece is Python.

Both of their stories develop in real time alongside yours. By the end of Part 1, they will have taken the same steps you have. By the end of the book, both of them will have transformed how they work.

What You Will Be Able to Do After Part 1

After eight chapters, you will be able to:

• Install Python and set up a development environment that works reliably
• Write Python programs that store and manipulate business data
• Build decision logic that mirrors the rules your organization already follows
• Automate repetitive calculations and transformations using loops
• Package your business logic into reusable functions with clear inputs and outputs
• Store and query collections of data — product lists, customer records, sales results
• Write code that handles real-world messiness without crashing

These are not toy capabilities. They are the foundation on which everything else in this book is built. More importantly, they are genuinely useful on their own. By the time you finish Chapter 8, you will be able to write small programs that solve real business problems.

Part 2 is where the data work begins in earnest. But first: foundations.

Let's go.

Chapter 1: Why Python? The Business Case for Coding →