I've been there—sitting on the sidelines watching others get really good with Python. Feeling stuck with just Excel and SQL. Not really knowing how to branch out. Meanwhile, everyone else moves forward. And you're left behind:
It’s exhausting. It was for me a few years into my business analytics career anyway. I had a co-worker, Scott, who was AWESOME at Python and could do seemingly anything. He ended up getting promoted and I ended up taking over his boring, pre-canned Excel reports for our boss. But then, I asked myself: what if it were EASY to learn Python? I mean, what would that look like?
Well, here's how to get there: 1. Start with the BasicsBegin by learning the essential elements of Python, like variables, data types, and simple operations. Don’t worry about complex algorithms. Familiarize yourself with the simpler, foundational concepts. It’s like learning to walk before you run. Here are some quick start steps if you aren't sure where to start:
Interested in a deep dive tutorial walkthrough of these steps? Let me know! 2. Practice RegularlyDon’t just read—implement. Apply what you learn through small projects or tasks. Consistency is key. It's about practicing daily, even if it's just for a short amount of time. The more you practice, the more the concepts will sink in, making it easier over time. Examples of Python projects for data analysts:
Each of these projects is valuable on its own. Especially when you practice regularly. You'll work with different libraries. And work through different problems and use cases. 3. Seek HelpConnect with Python communities online, join forums, and don’t hesitate to ask questions, no matter how basic they seem. Here are my go-to Python communities when I'm stuck:
Python is a handy tool for people who work with data and want to increase their earning potential. This guide is here to show you simple ways to start using Python, even if you’re really busy. Here’s a quick look back at what you’ve learned:
Now, you know the basics and can start using Python to make smarter business choices. Keep trying more with Python; each new thing you try helps you learn more. So, what are you going to try next with Python? Take 3 minutes to let me know what you want help with next. Until next time, Brian PS: You may have noticed that Starting with Data hasn't been published in a few weeks. Sorry about that! I had some family matters come up – thanks to everyone who has had me in their thoughts and prayers. I really appreciate it! 🙏 Whenever you're ready, there are three ways I can help
|
You are receiving this because you signed up for Starting with Data, purchased one of my data analytics products, or enrolled in one of my data analytics courses. Unsubscribe at any time using the link below. 600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246 |
Learn to build analytics projects with SQL, Tableau, Excel, and Python. For data analysts looking to level up their career and complete beginners looking to get started. No fluff. No theory. Just step-by-step tutorials anyone can follow.
Hey Reader, Most analysts can't answer something like this: "Which of our guides are generating the most revenue, and are we assigning them to the right expeditions?" This isn't a one-step question. You need to: Calculate revenue per guide Look at which expedition types they're assigned to Compare guide revenue to expedition category performance Identify mismatches (top guides on underperforming products, or vice versa) That's four analytical steps. Trying to write this as a single SQL query...
Hey Reader, Quick question: Could a colleague open your most recent SQL query and understand what it does without asking you a single question? If the answer is "probably not," this newsletter is for you. Writing SQL that works is step one. Writing SQL that someone else can read, trust, and maintain — that's the skill that changes how people see your work. Why This Matters More Than You Think Here's what I've noticed over 15+ years in analytics: the analysts who get promoted aren't always the...
Hey Reader, Imagine you're presenting a finding to your team: "Customer A spent $4,200 with us." The first question from the room: "Is that a lot?" Most analysts learning SQL don't realize that, without context, the number means nothing. You need comparison. Is the average customer spend $500 or $5,000? Is $4,200 in the top 10% or the middle of the pack? This is the "compared to what?" problem, and subqueries solve it elegantly. Numbers without context don't drive decisions. Executives don't...