![Revisit consent button](../images/body-df29beacd7496220cc94.svg) We value your privacy We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies. Customise Reject All Accept All Customise Consent Preferences ![](../images/body-2159bb67f3de8ad870eb.svg) We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below. The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... Show more NecessaryAlways Active Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data. * Cookie BCTempID * Duration 10 minutes * Description No description available. * Cookie __cf_bm * Duration 1 hour * Description This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. * Cookie AWSALBCORS * Duration 7 days * Description Amazon Web Services set this cookie for load balancing. * Cookie _cfuvid * Duration session * Description Cloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services * Cookie li_gc * Duration 6 months * Description Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. * Cookie __hssrc * Duration session * Description This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. * Cookie __hssc * Duration 1 hour * Description HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. * Cookie wpEmojiSettingsSupports * Duration session * Description WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. * Cookie BCSessionID * Duration 1 year 1 month 4 days * Description Blueconic sets this cookie as a unique identifier for the BlueConic profile. * Cookie _octo * Duration 1 year * Description No description available. * Cookie logged_in * Duration 1 year * Description No description available. * Cookie __Secure-YEC * Duration past * Description YouTube sets this cookie to stores the user's video player preferences using embedded YouTube video * Cookie __eoi * Duration 6 months * Description Description is currently not available. * Cookie AWSALBTGCORS * Duration 7 days * Description No description available. * Cookie login-status-p * Duration past * Description Description is currently not available. * Cookie AWSALBTG * Duration 7 days * Description No description available. * Cookie csrf_token * Duration session * Description No description available. * Cookie token_v2 * Duration 1 day * Description Description is currently not available. * Cookie D * Duration 1 year * Description Description is currently not available. * Cookie PHPSESSID * Duration session * Description This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed. * Cookie VISITOR_PRIVACY_METADATA * Duration 6 months * Description YouTube sets this cookie to store the user's cookie consent state for the current domain. * Cookie cookietest * Duration session * Description The cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience. * Cookie __Host-airtable-session * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie __Host-airtable-session.sig * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie m * Duration 1 year 1 month 4 days * Description Stripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly. * Cookie BIGipServer* * Duration session * Description Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user. * Cookie __cfruid * Duration session * Description Cloudflare sets this cookie to identify trusted web traffic. * Cookie _GRECAPTCHA * Duration 6 months * Description Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks. * Cookie __Secure-YNID * Duration 6 months * Description Google cookie used to protect user security and prevent fraud, especially during the login process. * Cookie cookieyes-consent * Duration 1 year * Description CookieYes sets this cookie to remember users' consent preferences so that their preferences are respected on subsequent visits to this site. It does not collect or store any personal information about the site visitors. Functional Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features. * Cookie lidc * Duration 1 day * Description LinkedIn sets the lidc cookie to facilitate data center selection. * Cookie brw * Duration 1 year * Description No description available. * Cookie brwConsent * Duration 5 minutes * Description Description is currently not available. * Cookie WMF-Uniq * Duration 1 year * Description Description is currently not available. * Cookie loom_anon_comment * Duration 1 year * Description No description available. * Cookie loom_referral_video * Duration session * Description Description is currently not available. * Cookie VISITOR_INFO1_LIVE * Duration 6 months * Description A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. * Cookie yt-remote-connected-devices * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie ytidb::LAST_RESULT_ENTRY_KEY * Duration Never Expires * Description The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future. * Cookie yt-remote-device-id * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie yt-remote-session-name * Duration session * Description The yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video. * Cookie yt-remote-fast-check-period * Duration session * Description The yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos. * Cookie yt-remote-session-app * Duration session * Description The yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player. * Cookie yt-remote-cast-available * Duration session * Description The yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player. * Cookie yt-remote-cast-installed * Duration session * Description The yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video. * Cookie cp_session * Duration 3 months * Description Codepen sets this cookie for Help systems found in the website. * Cookie loid * Duration 1 year 1 month 4 days * Description This cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform. Analytics Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc. * Cookie __hstc * Duration 6 months * Description Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). * Cookie hubspotutk * Duration 6 months * Description HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. * Cookie _ga * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. * Cookie _ga_* * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to store and count page views. * Cookie __Host-psifi.analyticsTrace * Duration 6 hours * Description Description is currently not available. * Cookie __Host-psifi.analyticsTraceV2 * Duration 6 hours * Description Description is currently not available. * Cookie _gh_sess * Duration session * Description GitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form. * Cookie YSC * Duration session * Description YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. * Cookie ajs_anonymous_id * Duration 1 year * Description This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. * Cookie vuid * Duration 1 year 1 month 4 days * Description Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. Performance Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors. * Cookie AWSALB * Duration 7 days * Description AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target. * Cookie acq * Duration past * Description Description is currently not available. * Cookie acq.sig * Duration past * Description Description is currently not available. * Cookie ptc * Duration 2 years * Description No description available. Advertisement Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns. * Cookie muc_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to collect user behaviour and interaction data to optimize the website. * Cookie guest_id_marketing * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie guest_id_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie personalization_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting. * Cookie guest_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. It registers if a user is signed in to the Twitter platform and collects information about ad preferences. * Cookie bcookie * Duration 1 year * Description LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. * Cookie __Secure-ROLLOUT_TOKEN * Duration 6 months * Description YouTube sets this cookie to manage feature rollout and experimentation. It helps Google control which new features or interface changes are shown to users as part of testing and staged rollouts, ensuring consistent experience for a given user during an experiment. * Cookie yt.innertube::nextId * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie yt.innertube::requests * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie session_tracker * Duration session * Description This cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website. * Cookie edgebucket * Duration session * Description Reddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content. * Cookie did * Duration 1 year * Description Arbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year. Uncategorised Other uncategorised cookies are those that are being analysed and have not been classified into a category as yet. No cookies to display. Reject All Save My Preferences Accept All Toggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation [](https://towardsdatascience.com/) Publish AI, ML & data-science insights to a global community of data professionals. Sign in[Submit an Article](https://write.insightmediagroup.io) [Latest](https://towardsdatascience.com/latest/)[Editor's Picks](https://towardsdatascience.com/tag/editors-pick/)[Newsletter](https://towardsdatascience.com/tag/the-variable/)[ShipAI](https://towardsdatascience.com/shipai/) * * * [Write For TDS](https://towardsdatascience.com/submissions/) [LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search [Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/) # From Data Analyst to Data Engineer: My 12-Month Self-Study Roadmap The exact tools I'm learning, the projects I'm building, and the mistakes I'm already expecting to make [Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/) May 16, 20269 min read ![](../images/000.jpg) Generated with Gemini AI To be honest. A part of me started this journey because data engineering is one of the hottest and highest-paying careers right now. I'm not going to pretend that wasn't a factor. But there's more to it than that. I've been learning data analytics for a while now. SQL, Power BI, Python (Pandas, NumPy, a little Polars), data cleaning, EDA. You name it, I've been in the weeds with it. And I genuinely enjoy it. But somewhere along the way, I started getting curious about what happens before the data lands on my desk. How does it move? Who builds those pipelines? What does the infrastructure behind all of this actually look like? That curiosity planted a seed. Then AI started making a lot of what I do faster and easier. Which is great. But it also made me think: if AI can handle the analysis, what's my edge? What can I build and understand that goes deeper? I work as an IT System Analyst at a startup, and while I enjoy the work, I realized I wasn't challenging myself the way I wanted to. I was ready for more. The final push came from a video by Data With Baraa, where he laid out a complete [data engineering roadmap](https://www.youtube.com/watch?v=odZHmYgebbw). Something about seeing it structured and broken down made it feel real and doable. So here I am. I'm learning data engineering in public. And this article is the beginning of that journey. _Also, just leaving a disclaimer that I'm not affiliated with Data with Baraa. I'm just sharing my personal journey. Hope it helps._ Learn this step by step with the interactive [Data Engineer](https://roadmap.sh/data-engineer) roadmap. ## Why Data Engineering Specifically I want to spend a moment here because I think this question deserves a real answer. Data analytics taught me how to work with data after it arrives. Clean it, explore it, visualize it, draw insights from it. That skillset is genuinely valuable. But the more I learned, the more I kept bumping into the same wall. The data I was working with had already been shaped and moved by someone else. Someone had built the pipeline that brought it to me. Someone had decided how it was stored, how it was structured, how often it refreshed. I wanted to be that person. Data engineering sits upstream from analytics. It's about building the systems that make analysis possible in the first place. Data pipelines, storage architecture, workflow orchestration, large-scale data processing. These are the foundations everything else is built on. And honestly, that kind of infrastructure work appeals to me in a way that pure analysis no longer does. There's also a practical argument. Data engineering roles consistently rank among the highest paying in the data industry. As AI tools get better at automating the analytical layer, the demand for people who can build and maintain reliable data infrastructure is only going to grow. I'd rather be building the pipes than just using them. And one more thing. The startup I work at doesn't use any of the tools I'm about to learn. Which means every hour I put into this is entirely self-directed. No team to learn from, no work projects to apply it on. Just me, the internet, and whatever I can build on my own. That's a challenge I'm choosing on purpose. ## Why I'm Doing This in Public Writing about what I learn is something I already believe in deeply. It forces you to actually understand something before you explain it. It keeps you accountable. And over time, it builds something that a resume alone never could. But I'll be honest about my fears too, because I think that's the point of doing this publicly. I have shiny object syndrome. There, I said it. I've explored graphic design, animation, writing, marketing, and IT before landing in data. There's always something new and exciting pulling my attention. Data engineering could easily get replaced by the next flashy thing in my feed if I'm not intentional about it. Consistency is another one. I work a 9-5 where I barely touch the tools I'll be learning. There's no natural reinforcement at work, no colleague I can bounce Airflow questions off of. I'm building this entirely on my own time, outside of my job responsibilities. And balance. Three to four hours a day is the goal. Some days that will feel easy. Other days it will feel impossible. Publishing this journey is my accountability system. If I go quiet, you'll know I slipped. And I'd rather not slip. ## What I'm Starting With I'm not starting from zero, which helps. I already have beginner to intermediate SQL knowledge from my data analytics work, basic Python fundamentals, and some hands-on experience with Pandas. That gives me a foundation to build on rather than rebuild from scratch. Here's the full learning stack, roughly in the order I'll be tackling it. ### 1. SQL: Going Deeper Than Analytics I know SQL. But analytics SQL and engineering SQL are different animals. I'll be going deeper into query optimization, indexing, working with very large datasets, and writing SQL that's built for performance rather than just exploration. If you've only ever used SQL to pull and filter data, there's a whole other layer underneath worth understanding. > **Why it's first:** Everything in data engineering eventually touches SQL. Getting sharp here before layering in more complex tools makes the rest of the journey easier. ### 2. Python: From Exploratory to Production-Ready I have the basics. Pandas, NumPy, some Polars. But the Python I've been writing lives mostly in notebooks. Exploratory, messy, not built to last. The goal now is to write cleaner, more structured, reusable code. Functions, modules, error handling, scripting. The kind of Python you'd actually put in a pipeline. > **Why it matters:** Python is the glue that holds most modern data engineering stacks together. Airflow uses it. PySpark is built on it. Getting comfortable here is non-negotiable. ### 3. Git and GitHub: Version Control Done Properly I'll be honest. My Git knowledge is currently "copy the command, hope it works." That has to change. Version control is fundamental to working like an engineer rather than just an analyst. I'll be learning branching, pull requests, and how to manage code properly across projects. > **Why it matters:** Every project I build from here on goes on GitHub. It's portfolio, it's discipline, and it's how real teams work. ### 4. Apache Spark and PySpark: Big Data Processing This is where things get genuinely exciting. Apache Spark is one of the most widely used engines for processing large-scale data. PySpark is the Python API for it, which means I can use a language I'm already somewhat familiar with to work with distributed data at scale. The jump from Pandas to Spark is a mindset shift. Pandas works on a single machine. Spark is built to run across clusters. Learning to think in that distributed way is one of the skills that separates data engineers from analysts. > **Why it matters:** If you want to work with big data in a production environment, Spark is almost unavoidable. It shows up in job descriptions constantly and is core to the Databricks ecosystem I'll be building toward. ### 5. Apache Airflow: Orchestrating Data Pipelines Data pipelines don't run themselves. You need something to schedule them, monitor them, and handle failures gracefully. That's where workflow orchestration tools come in, and Airflow is my pick. I considered a few options here. Databricks Workflows is great if you're already deep in the Databricks ecosystem. Azure Data Factory makes sense for Azure-heavy environments. But Airflow is free, open-source, cloud-agnostic, and widely used across the industry. It also teaches you the core concepts of orchestration in a way that transfers to other tools. Starting with Airflow felt like the right call, especially since I'm trying to keep costs low. > **Why it matters:** Orchestration is what turns a collection of scripts into an actual pipeline. Understanding Airflow is understanding how production data workflows are managed. ### 6. Databricks: The Data Platform At some point you need to pick a data platform and go deep on it. I'm going with Databricks. It's built on top of Spark, it's in high demand, and it has a free Community Edition that lets you practice without paying for cloud credits. The alternatives are solid too. Snowflake is a clean, fast SQL warehouse that a lot of companies love. BigQuery is Google's fully managed, serverless option and genuinely excellent if you're leaning toward Google Cloud. But Databricks sits at the intersection of big data, machine learning, and data engineering in a way that matches where I want to go. It made the most sense for my goals. > **Why it matters:** Employers want you to have platform experience. Going deep on one is more valuable than knowing a little about all of them. ## How I'm Structuring the 12 Months The honest answer is that this might take longer than 12 months. And I'm okay with that. I'd rather take 15 months and actually understand what I'm doing than rush through in 12 and come out shaky on the fundamentals. The general approach is to move through each skill in order and not advance until I've built something with what I just learned. Tutorials are fine for orientation but projects are where real learning happens. My plan is to document each phase here on Towards Data Science: the concepts, the projects, the frustrations, and the wins. For tracking progress, I'm using the Notion roadmap from Data With Baraa as my backbone. It breaks down each skill into core topics and lets me track where I am without getting overwhelmed by the full picture all at once. As for time commitment, three to four hours a day is the target. Some of that will be structured learning. Some will be building. Some will be writing about what I just learned, which is its own form of studying. ## What Success Looks Like Landing a high-paying data engineering role is the goal. That's real and I'm not going to dress it up. But alongside that, I want to become a credible voice in this space. Someone who builds things worth talking about, documents the journey without filtering out the hard parts, and maybe makes the path a little clearer for someone coming up behind me. The writing and the learning feed each other. The portfolio becomes the proof. The proof builds the brand. That's the vision. ## Starting Today This article is my official start date. I'm not waiting until I feel ready or until everything is perfectly planned. I'm starting now, writing as I go, and letting the process be public and a little messy. If you're somewhere on a similar path. Whether you're in analytics thinking about engineering, in IT wondering what's next, or just someone trying to build skills that hold their value in an AI-accelerated world. Follow along. I think we'll have a lot to talk about. I'll also be sharing my learnings on my YouTube channel. So feel free to subscribe below and follow along. ··· _This is the first article in an ongoing series documenting my data engineering journey. I'll be publishing regularly on my progress, the projects I'm building, and everything I learn along the way._ _And if you want to get access to the Notion template, in case you're on the same journey as I am, you can access it_[ _here_](https://www.notion.so/Data-Engineering-Roadmap-By-Data-With-Baraa-262e8e8e112280808c57e8a01990ce93?source=copy_link). _Follow along on my journey below_. [YouTube](https://www.youtube.com/@ibbysalam) [Medium](https://medium.com/@ibbysalam) [LinkedIn](https://www.linkedin.com/in/ibrahim-salami-059863228/) [Twitter](https://x.com/IbbySalam) ## Register Now to Continue Reading ### Unlock Towards Data Science with a Free Account All articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more. Register for freeSign in to your account * * * ![](../images/body-542334df68a32cd56c4a.jpeg) Written By ## [Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/) [See all from Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/) [Career Advice](https://towardsdatascience.com/tag/career-advice/)[Career Change](https://towardsdatascience.com/tag/career-change/)[Data Engineer](https://towardsdatascience.com/tag/data-engineer/)[Data Science](https://towardsdatascience.com/tag/data-science/)[Programming](https://towardsdatascience.com/tag/programming/) Share This Article * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Ffrom-data-analyst-to-data-engineer-my-12-month-self-study-roadmap%2F&title=From%20Data%20Analyst%20to%20Data%20Engineer%3A%20My%2012-Month%20Self-Study%20Roadmap) * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Ffrom-data-analyst-to-data-engineer-my-12-month-self-study-roadmap%2F&title=From%20Data%20Analyst%20to%20Data%20Engineer%3A%20My%2012-Month%20Self-Study%20Roadmap) * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Ffrom-data-analyst-to-data-engineer-my-12-month-self-study-roadmap%2F&text=From%20Data%20Analyst%20to%20Data%20Engineer%3A%20My%2012-Month%20Self-Study%20Roadmap) Towards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program. [Write for TDS](https://towardsdatascience.com/submissions/) ## Related Articles * [![](../images/001.jpeg)](https://towardsdatascience.com/deployment-models-cloud-computing-b17fe1e58d44/) ## [Deployment Models in Cloud Computing](https://towardsdatascience.com/deployment-models-cloud-computing-b17fe1e58d44/) [Programming](https://towardsdatascience.com/category/programming/) Understanding the difference between private, public and hybrid cloud [Giorgos Myrianthous](https://towardsdatascience.com/author/gmyrianthous/) November 4, 20213 min read * [![](../images/002.jpg)](https://towardsdatascience.com/why-load-testing-is-essential-to-take-your-ml-app-to-production-faab0df1c4e1/) ## [Why Load Testing is Essential to Take Your ML App to Production](https://towardsdatascience.com/why-load-testing-is-essential-to-take-your-ml-app-to-production-faab0df1c4e1/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) Load Testing a Flask ML Application using Locust [Ram Vegiraju](https://towardsdatascience.com/author/ram-vegiraju/) July 9, 20215 min read * [![](../images/003.png)](https://towardsdatascience.com/interactive-geographical-maps-with-geopandas-4586a9d7cc10/) ## [Interactive Geographical maps with GeoPandas](https://towardsdatascience.com/interactive-geographical-maps-with-geopandas-4586a9d7cc10/) [Data Science](https://towardsdatascience.com/category/data-science/) Explore the geospatial data with interactive visualizations [Parul Pandey](https://towardsdatascience.com/author/pandeyparul/) November 10, 20217 min read * [![](../images/004.jpg)](https://towardsdatascience.com/apache-spark-for-data-science-how-to-install-and-get-started-with-pyspark-6367a1ea3de8/) ## [Apache Spark for Data Science - How to Install and Get Started with PySpark](https://towardsdatascience.com/apache-spark-for-data-science-how-to-install-and-get-started-with-pyspark-6367a1ea3de8/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) Install PySpark locally and load your first dataset - Only 5 minutes required. [Dario Radečić](https://towardsdatascience.com/author/radecicdario/) April 7, 20226 min read * [![](../images/005.jpeg)](https://towardsdatascience.com/radical-simplicity-in-data-engineering-86ec3d2bd71c/) ## [Radical Simplicity in Data Engineering](https://towardsdatascience.com/radical-simplicity-in-data-engineering-86ec3d2bd71c/) [Programming](https://towardsdatascience.com/category/programming/) Learn from Software Engineers and Discover the Joy of 'Worse is Better' Thinking [Cai Parry-Jones](https://towardsdatascience.com/author/caiparryjones96/) July 26, 20246 min read * [![](../images/006.jpg)](https://towardsdatascience.com/from-cartography-to-digital-mapping-do-you-know-the-truth-c1440bb193dc/) ## [From Cartography to Digital Mapping: Do you know the truth?](https://towardsdatascience.com/from-cartography-to-digital-mapping-do-you-know-the-truth-c1440bb193dc/) [Data Science](https://towardsdatascience.com/category/data-science/) An online exhibition reflects on how the history of persuasive cartography can teach us to spot biases in visual data [Nahal Sheikh](https://towardsdatascience.com/author/nahalsheikh/) September 27, 20207 min read * [![](../images/body-63beb50f664a055ed739.jpg)](https://towardsdatascience.com/latest-picks-how-to-measure-interpretability-5a146814b53e/) ## [Latest picks: How to measure interpretability?](https://towardsdatascience.com/latest-picks-how-to-measure-interpretability-5a146814b53e/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) Your daily dose of data science [TDS Editors](https://towardsdatascience.com/author/towardsdatascience/) November 23, 20201 min read * [![](../images/008.jpeg)](https://towardsdatascience.com/working-with-python-and-json-1ca0a7446744/) ## [Working with Python and JSON](https://towardsdatascience.com/working-with-python-and-json-1ca0a7446744/) [Data Science](https://towardsdatascience.com/category/data-science/) The Basics every Data Enthusiast have to know about As a data analyst, data engineer... [Christianlauer](https://towardsdatascience.com/author/christianlauer90/) May 25, 20214 min read * [![](../images/009.jpg)](https://towardsdatascience.com/building-a-user-event-data-pipeline-f57ca088e766/) ## [Building a User Event Data Pipeline](https://towardsdatascience.com/building-a-user-event-data-pipeline-f57ca088e766/) [Data Science](https://towardsdatascience.com/category/data-science/) It's never been easier to take control of your data with a custom data pipeline [Jeremy Dorn](https://towardsdatascience.com/author/jeremydorn/) July 14, 20215 min read * [YouTube](https://www.youtube.com/c/TowardsDataScience) * [X](https://x.com/TDataScience) * [LinkedIn](https://www.linkedin.com/company/towards-data-science/) * [Threads](https://www.threads.net/@towardsdatascience) * [Bluesky](https://bsky.app/profile/towardsdatascience.com) [](https://towardsdatascience.com/) Your home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals. Subscribe to Our Newsletter[Write For TDS](https://towardsdatascience.com/submissions/)•[About](https://towardsdatascience.com/about-towards-data-science-d691af11cc2f/)•[Advertise](https://contact.towardsdatascience.com/advertise-with-towards-data-science)•[Privacy Policy](https://towardsdatascience.com/privacy-policy/)•[Terms of Use](https://towardsdatascience.com/website-terms-of-use/) © Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network) #### Recommended Articles Close * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500) Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1 ](https://towardsdatascience.com/javascript-fatigue-you-dont-need-js-to-build-chatgpt/ "Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500) The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs ](https://towardsdatascience.com/subset-sum-problem-solved-in-linear-time-for-dense-enough-inputs/ "The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500) Does Your Company Have a Data Strategy? ](https://towardsdatascience.com/does-your-company-have-a-data-strategy-e8944dbec4ae/ "Does Your Company Have a Data Strategy?") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/4970/image?etag=1780565225463&width=500&height=500) Productivity Tips, Data Career Insights, and Other Recent Must-Reads ](https://towardsdatascience.com/productivity-tips-data-career-insights-and-other-recent-must-reads-5c47eb7a2fe0/ "Productivity Tips, Data Career Insights, and Other Recent Must-Reads")