{
  "source_file": "0930",
  "source_platform": "Medium",
  "author": "Ibrahim Salami",
  "title_listed": "I Thought Data Engineering Was Just Writing Scripts. I Was Wrong.",
  "keywords": "",
  "domain": "数据处理",
  "content_type": "深度技术解析",
  "is_paid_flag": "否",
  "url": "https://towardsdatascience.com/i-thought-data-engineering-was-just-writing-scripts-i-was-wrong/",
  "publish_date": "2026-06-12",
  "corpus_stage": "",
  "notes": "",
  "id": "142ec8d51cc4",
  "collected_at": "2026-10-02T11:33:52",
  "title": "I Thought Data Engineering Was Just Writing Scripts. I Was Wrong. | Towards Data Science",
  "body_markdown": "![Revisit consent button](../images/body-df29beacd7496220cc94.svg)\nWe value your privacy\nWe 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.\nCustomise Reject All Accept All\nCustomise Consent Preferences ![](../images/body-2159bb67f3de8ad870eb.svg)\nWe use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.\nThe 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\nNecessaryAlways Active\nNecessary 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.\n  * Cookie\nBCTempID\n  * Duration\n10 minutes\n  * Description\nNo description available.\n\n\n  * Cookie\n__cf_bm\n  * Duration\n1 hour\n  * Description\nThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management. \n\n\n  * Cookie\nAWSALBCORS\n  * Duration\n7 days\n  * Description\nAmazon Web Services set this cookie for load balancing.\n\n\n  * Cookie\n_cfuvid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services\n\n\n  * Cookie\nli_gc\n  * Duration\n6 months\n  * Description\nLinkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.\n\n\n  * Cookie\n__hssrc\n  * Duration\nsession\n  * Description\nThis 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.\n\n\n  * Cookie\n__hssc\n  * Duration\n1 hour\n  * Description\nHubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.\n\n\n  * Cookie\nwpEmojiSettingsSupports\n  * Duration\nsession\n  * Description\nWordPress 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.\n\n\n  * Cookie\nBCSessionID\n  * Duration\n1 year 1 month 4 days\n  * Description\nBlueconic sets this cookie as a unique identifier for the BlueConic profile.\n\n\n  * Cookie\n_octo\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nlogged_in\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\n__Secure-YEC\n  * Duration\npast\n  * Description\nYouTube sets this cookie to stores the user's video player preferences using embedded YouTube video\n\n\n  * Cookie\n__eoi\n  * Duration\n6 months\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTGCORS\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\nlogin-status-p\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTG\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\ncsrf_token\n  * Duration\nsession\n  * Description\nNo description available.\n\n\n  * Cookie\ntoken_v2\n  * Duration\n1 day\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nD\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nPHPSESSID\n  * Duration\nsession\n  * Description\nThis 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.\n\n\n  * Cookie\nVISITOR_PRIVACY_METADATA\n  * Duration\n6 months\n  * Description\nYouTube sets this cookie to store the user's cookie consent state for the current domain. \n\n\n  * Cookie\ncookietest\n  * Duration\nsession\n  * Description\nThe cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience.\n\n\n  * Cookie\n__Host-airtable-session\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\n__Host-airtable-session.sig\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\nm\n  * Duration\n1 year 1 month 4 days\n  * Description\nStripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly.\n\n\n  * Cookie\nBIGipServer*\n  * Duration\nsession\n  * Description\nMarketo 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. \n\n\n  * Cookie\n__cfruid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to identify trusted web traffic.\n\n\n  * Cookie\n_GRECAPTCHA\n  * Duration\n6 months\n  * Description\nGoogle Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks.\n\n\n  * Cookie\n__Secure-YNID\n  * Duration\n6 months\n  * Description\nGoogle cookie used to protect user security and prevent fraud, especially during the login process.\n\n\n  * Cookie\ncookieyes-consent\n  * Duration\n1 year\n  * Description\nCookieYes 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.\n\n\nFunctional\nFunctional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.\n  * Cookie\nlidc\n  * Duration\n1 day\n  * Description\nLinkedIn sets the lidc cookie to facilitate data center selection.\n\n\n  * Cookie\nbrw\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nbrwConsent\n  * Duration\n5 minutes\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nWMF-Uniq\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nloom_anon_comment\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nloom_referral_video\n  * Duration\nsession\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nVISITOR_INFO1_LIVE\n  * Duration\n6 months\n  * Description\nA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.\n\n\n  * Cookie\nyt-remote-connected-devices\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nytidb::LAST_RESULT_ENTRY_KEY\n  * Duration\nNever Expires\n  * Description\nThe 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.\n\n\n  * Cookie\nyt-remote-device-id\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-name\n  * Duration\nsession\n  * Description\nThe yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\nyt-remote-fast-check-period\n  * Duration\nsession\n  * Description\nThe yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-app\n  * Duration\nsession\n  * Description\nThe yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-available\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-installed\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\ncp_session\n  * Duration\n3 months\n  * Description\nCodepen sets this cookie for Help systems found in the website.\n\n\n  * Cookie\nloid\n  * Duration\n1 year 1 month 4 days\n  * Description\nThis cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform.\n\n\nAnalytics\nAnalytical 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.\n  * Cookie\n__hstc\n  * Duration\n6 months\n  * Description\nHubspot 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).\n\n\n  * Cookie\nhubspotutk\n  * Duration\n6 months\n  * Description\nHubSpot 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.\n\n\n  * Cookie\n_ga\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle 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.\n\n\n  * Cookie\n_ga_*\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle Analytics sets this cookie to store and count page views.\n\n\n  * Cookie\n__Host-psifi.analyticsTrace\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n__Host-psifi.analyticsTraceV2\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n_gh_sess\n  * Duration\nsession\n  * Description\nGitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form.\n\n\n  * Cookie\nYSC\n  * Duration\nsession\n  * Description\nYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.\n\n\n  * Cookie\najs_anonymous_id\n  * Duration\n1 year\n  * Description\nThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.\n\n\n  * Cookie\nvuid\n  * Duration\n1 year 1 month 4 days\n  * Description\nVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. \n\n\nPerformance\nPerformance 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.\n  * Cookie\nAWSALB\n  * Duration\n7 days\n  * Description\nAWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target.\n\n\n  * Cookie\nacq\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nacq.sig\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nptc\n  * Duration\n2 years\n  * Description\nNo description available.\n\n\nAdvertisement\nAdvertisement 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.\n  * Cookie\nmuc_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to collect user behaviour and interaction data to optimize the website.\n\n\n  * Cookie\nguest_id_marketing\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\nguest_id_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\npersonalization_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter 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.\n\n\n  * Cookie\nguest_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter 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.\n\n\n  * Cookie\nbcookie\n  * Duration\n1 year\n  * Description\nLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.\n\n\n  * Cookie\n__Secure-ROLLOUT_TOKEN\n  * Duration\n6 months\n  * Description\nYouTube 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.\n\n\n  * Cookie\nyt.innertube::nextId\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nyt.innertube::requests\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nsession_tracker\n  * Duration\nsession\n  * Description\nThis cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website.\n\n\n  * Cookie\nedgebucket\n  * Duration\nsession\n  * Description\nReddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content.\n\n\n  * Cookie\ndid\n  * Duration\n1 year\n  * Description\nArbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year.\n\n\nUncategorised\nOther uncategorised cookies are those that are being analysed and have not been classified into a category as yet.\nNo cookies to display.\nReject All Save My Preferences Accept All\nToggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation\n[](https://towardsdatascience.com/)\nPublish AI, ML & data-science insights to a global community of data professionals.\nSign in[Submit an Article](https://write.insightmediagroup.io)\n[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/)\n* * *\n[Write For TDS](https://towardsdatascience.com/submissions/)\n[LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search\n[Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/)\n# I Thought Data Engineering Was Just Writing Scripts. I Was Wrong.\nI tried to make my ETL pipeline production-ready. Three things broke. Each one taught me something scripting alone never could.\n[Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/)\nJune 12, 20268 min read\n![](../images/000.jpg)\nCreated with Gemini AI\nAfter I built my first ETL pipeline, I thought I had a pretty good grip on what data engineering actually was. You extract data from somewhere, you clean it up, you load it somewhere useful. ETL. Simple enough.\nFor context, I am a data analyst trying to transition into data engineering. I have been documenting that journey publicly, starting with a [12-month self-study roadmap](https://towardsdatascience.com/from-data-analyst-to-data-engineer-my-12-month-self-study-roadmap/) I put together earlier this year. The most recent step in that journey was [building my first ETL pipeline from scratch](https://towardsdatascience.com/i-built-my-first-etl-pipeline-as-a-complete-beginner-heres-exactly-how/) using the GitHub API, which I wrote about here on TDS. That pipeline worked. It pulled data, cleaned it, saved it to a CSV. I was happy with it.\nSo I decided to push it further, make it more \"production-ready\" as the internet likes to say. What happened next genuinely surprised me. Not because things broke, but because of what the breaking revealed.\n## The Original Pipeline\nThe original pipeline was basic, which was fine because that was the point. Extract data from the GitHub API, do a bit of cleaning, save everything to a CSV file. It worked perfectly for what it was: a learning exercise. But a CSV file and a one-time script is not how data engineering works in the real world. I wanted to find out what \"real world\" actually meant in practice, so I decided to push the pipeline further and see what happened.\nLearn this step by step with the interactive [Data Engineer](https://roadmap.sh/data-engineer) roadmap.\nHere is the full original pipeline for anyone who hasn't read the previous article:\npython\n\n```\nimport requests\nfrom datetime import datetime, timedelta\n\nurl = \"https://api.github.com/search/repositories\"\nparams = {\n    \"q\": \"language:python created:>2025-04-22\",\n    \"sort\": \"stars\",\n    \"order\": \"desc\",\n    \"per_page\": 30\n}\n\nresponse = requests.get(url, params=params)\ndata = response.json()\n\nimport pandas as pd\nrepos = []\nfor repo in data['items']:\n    repos.append({\n        \"name\": repo['name'],\n        \"owner\": repo['owner']['login'],\n        \"stars\": repo['stargazers_count'],\n        \"forks\": repo['forks_count'],\n        \"language\": repo['language'],\n        \"description\": repo['description'],\n        \"url\": repo['html_url'],\n        \"created_at\": repo['created_at']\n    })\n\ndf = pd.DataFrame(repos)\ndf_clean = df.dropna(subset=['description'])\ndf_clean = df_clean.copy()\ndf_clean['viral'] = df_clean['stars'].apply(lambda x: 'Yes' if x > 50000 else 'No')\ndf_clean = df_clean.sort_values('stars', ascending=False).reset_index(drop=True)\n\ndf_clean.to_csv('github_trending_repos.csv', index=False)\nprint(\"Pipeline complete. File saved.\")\n```\n\nSimple, readable, and it works. But the moment you try to run it more than once, or come back to it the next day, the cracks start to show.\n## Wall One: The Pipeline Had No Memory\nThe first upgrade was straightforward. Instead of saving to a CSV file, I loaded the data into a SQLite database. SQLite is still just a single file, but it behaves like a real database. You can query it, check what's already in it, and build on top of it properly. It felt like a small change. It wasn't.\nI ran the pipeline once and got 22 repos. Then I ran it a second time without changing anything and checked the database.\nmarkup\n\n```\nTotal rows: 44 Unique repos: 22 Duplicates: 22\n```\n\nHonestly, I didn't expect it. I guessed it could happen but I never really thought it would. But I'm glad it did, because it was the first time I actually watched my pipeline break. And what it revealed was simple but important: the script had no memory. Every time it ran, it started completely fresh and blindly appended whatever it found. No warning, no error. Just \"Pipeline complete\" like everything was fine.\nThis is where I came across a concept called idempotency.  \nIdempotency is a fancy word for a simple idea. If something has already happened, it shouldn't happen again. In the context of a data pipeline, it means that running your pipeline once or running it ten times should always produce the same result. No extra rows, no duplicates, no silent corruption of your data.\nThe fix was straightforward in principle. Before inserting anything into the database, the pipeline now checks if that record already exists. If it does, it removes it first, then inserts the fresh version. One small change in thinking, but it completely changes how reliable your pipeline is.\nAnd here's the part that stuck with me: a basic script will never think about this on its own. You have to build it in deliberately. That's not scripting anymore. That's engineering.\n## Wall Two: The Data Disappeared Overnight\nThe second wall was less technical and more unsettling.\nWhen I closed Colab for the night and came back the next day, there was this uneasy feeling. I had to run everything again from scratch and hope nothing broke, even though everything had worked perfectly the night before. The database I had carefully built was just gone. And I remembered that before this project, I had actually struggled to find my original ETL pipeline file. I spent time looking for it before I finally did. That feeling of almost losing your work stays with you.\nI knew there had to be a better way. A real pipeline cannot depend on someone being there to rerun it every morning. The data has to live somewhere that survives beyond the session.\nThe fix here was mounting Google Drive directly inside Colab and pointing the database connection there instead of to the temporary Colab environment. One line change:\npython\n\n```\nconn = sqlite3.connect('/content/drive/MyDrive/github_repos.db')\n```\n\nNow the database lives in Google Drive. Close the session, restart the runtime, open a new notebook entirely. The data is still there waiting.\nBut this fix revealed something bigger. If persisting data already requires thinking about where things live and how they survive, what happens when you need the pipeline to run automatically every day without you touching it at all?\n## Wall Three: Nobody Can Press Run Forever\nThe third wall was the one that excited me the most, which surprised me.\nEven with the duplicate problem solved and the database living safely in Google Drive, someone still has to open the notebook and press run. Colab is not a server. It is an interactive environment. It does not wake up at 3am, pull fresh data from the GitHub API, and go back to sleep. That is not what it was built for.\nAnd when I thought about it from a real world perspective, that clicked immediately. In an actual company, nobody is sitting there on alert at midnight waiting to run a script. The pipeline has to run itself. On a schedule. Reliably. Whether or not anyone is watching.\nThis is where tools like Apache Airflow, Prefect, and cloud-based cron jobs come in. These are not Python scripts. They are systems that live on servers, manage schedules, handle failures, send alerts when something goes wrong, and keep a history of every run.\nScheduling is honestly the concept I am most excited to dig into next, because it is where data engineering starts to feel like real infrastructure work.\n## Walking Through the Key Changes\nLet me walk through the three actual changes I made to the pipeline and what each one does.\n### 1. Swapping CSV for SQLite\npython\n\n```\n# Before\ndf_clean.to_csv('github_trending_repos.csv', index=False)\n\n# After\nconn = sqlite3.connect('github_repos.db')\ndf_clean.to_sql('repos', conn, if_exists='append', index=False)\nconn.close()\n```\n\nSaving to a CSV is fine for a one-time analysis. But a CSV is just a text file. You cannot easily query it, and it does not scale well as your data grows. SQLite is an actual database, which means you can run SQL queries on it, check what is already inside it, and build on top of it properly. Same simplicity, much more capability.\n### 2. Fixing the duplicate problem\npython\n\n```\ncursor.execute('''\n    DELETE FROM repos WHERE url IN (SELECT url FROM repos_temp)\n''')\ncursor.execute('''\n    INSERT INTO repos SELECT * FROM repos_temp\n''')\n```\n\nThis is the idempotency fix. Before inserting anything, the pipeline checks if that repo already exists in the database using its URL as a unique identifier. If it does, it deletes it first, then inserts the fresh version. So no matter how many times the pipeline runs, you always end up with clean, non-duplicated data.\n### 3. Persisting data to Google Drive\npython\n\n```\n# Before\nconn = sqlite3.connect('github_repos.db')\n\n# After\nconn = sqlite3.connect('/content/drive/MyDrive/github_repos.db')\n```\n\nThis is one line but it changes everything. Instead of saving the database to the temporary Colab environment where it disappears when the session closes, it saves directly to Google Drive. Close the notebook, restart the runtime, come back tomorrow. Your data is still there waiting for you.\nHere is the full upgraded pipeline putting all three changes together:\npython\n\n```\nimport requests\nimport pandas as pd\nimport sqlite3\nfrom datetime import datetime, timedelta\n\n# Extract\nyesterday = (datetime.now() - timedelta(days=1)).strftime('%Y-%m-%d')\n\nurl = \"https://api.github.com/search/repositories\"\nparams = {\n    \"q\": f\"language:python created:>{yesterday}\",\n    \"sort\": \"stars\",\n    \"order\": \"desc\",\n    \"per_page\": 30\n}\n\nresponse = requests.get(url, params=params)\ndata = response.json()\n\n# Transform\nrepos = []\nfor repo in data['items']:\n    repos.append({\n        \"name\": repo['name'],\n        \"owner\": repo['owner']['login'],\n        \"stars\": repo['stargazers_count'],\n        \"forks\": repo['forks_count'],\n        \"language\": repo['language'],\n        \"description\": repo['description'],\n        \"url\": repo['html_url'],\n        \"created_at\": repo['created_at']\n    })\n\ndf = pd.DataFrame(repos)\ndf_clean = df.dropna(subset=['description'])\ndf_clean = df_clean.copy()\ndf_clean['viral'] = df_clean['stars'].apply(lambda x: 'Yes' if x > 50000 else 'No')\ndf_clean = df_clean.sort_values('stars', ascending=False).reset_index(drop=True)\n\n# Load\nconn = sqlite3.connect('/content/drive/MyDrive/github_repos.db')\ncursor = conn.cursor()\n\ncursor.execute('''\n    CREATE TABLE IF NOT EXISTS repos (\n        name TEXT, owner TEXT, stars INTEGER, forks INTEGER,\n        language TEXT, description TEXT, url TEXT,\n        created_at TEXT, viral TEXT, loaded_at TEXT\n    )\n''')\n\ndf_clean['loaded_at'] = datetime.now().strftime('%Y-%m-%d')\ndf_clean.to_sql('repos_temp', conn, if_exists='replace', index=False)\n\ncursor.execute('''\n    DELETE FROM repos WHERE url IN (SELECT url FROM repos_temp)\n''')\ncursor.execute('''\n    INSERT INTO repos SELECT * FROM repos_temp\n''')\n\nconn.commit()\nconn.close()\nprint(\"Pipeline complete. Duplicates handled.\")\n```\n\n## So What Is Data Engineering, Really?\nIf you had asked me what data engineering was after I built my first ETL pipeline, I would have said it was mostly about writing scripts. Extract, transform, load. Repeat. That is what it looked like from the outside.\nBut after pushing that pipeline further and watching it break in three different ways, I think about it differently now. Data engineering is about building systems that are reliable, not just scripts that run. There is a difference. A script does what you tell it, once, when you tell it. A system handles failure, remembers what it has already done, persists data beyond a single session, and runs itself on a schedule without anyone watching.\nIdempotency, persistence, scheduling. None of these concepts showed up when I was running my pipeline once in a notebook. They only revealed themselves when I tried to make it work like something real.\nAnd in a real company, you cannot afford to get this wrong. The data your pipeline produces is being used to make decisions. If it is full of duplicates, or disappears overnight, or only runs when someone remembers to press a button, that is not a data pipeline. That is a liability.\nI still have a lot to learn. Scheduling is the next wall I am walking toward. But I am walking toward it now knowing that data engineering was never just about writing scripts. I just had to break a few things to see that.\n_This is an ongoing data engineering series. Follow along as I document every step of the journey, including the parts that don’t go smoothly._\n_Connect with me on_[ _LinkedIn_](https://www.linkedin.com/in/ibrahim-salami-059863228/) _,_[_YouTube_](https://www.youtube.com/@ibbysalam) _, and_[ _Twitter_](https://x.com/IbbySalam) _._\n## Register Now to Continue Reading\n### Unlock Towards Data Science with a Free Account\nAll articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more.\nRegister for freeSign in to your account\n* * *\n![](../images/body-542334df68a32cd56c4a.jpeg)\nWritten By\n## [Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/)\n[See all from Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/)\n[Data Engineering](https://towardsdatascience.com/tag/data-engineering/)[Data Pipeline](https://towardsdatascience.com/tag/data-pipeline/)[Data Science](https://towardsdatascience.com/tag/data-science/)[Etl](https://towardsdatascience.com/tag/etl/)[Python](https://towardsdatascience.com/tag/python/)\nShare This Article\n  * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fi-thought-data-engineering-was-just-writing-scripts-i-was-wrong%2F&title=I%20Thought%20Data%20Engineering%20Was%20Just%20Writing%20Scripts.%20I%20Was%20Wrong.)\n  * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fi-thought-data-engineering-was-just-writing-scripts-i-was-wrong%2F&title=I%20Thought%20Data%20Engineering%20Was%20Just%20Writing%20Scripts.%20I%20Was%20Wrong.)\n  * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fi-thought-data-engineering-was-just-writing-scripts-i-was-wrong%2F&text=I%20Thought%20Data%20Engineering%20Was%20Just%20Writing%20Scripts.%20I%20Was%20Wrong.)\n\n\nTowards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program.\n[Write for TDS](https://towardsdatascience.com/submissions/)\n## Related Articles\n  * [![](../images/001.jpeg)](https://towardsdatascience.com/parallel-computing-92c4f818c/)\n## [What is Parallel Computing?](https://towardsdatascience.com/parallel-computing-92c4f818c/)\n[Programming](https://towardsdatascience.com/category/programming/)\nUnderstanding the importance of parallel computing in the context of Data Engineering\n[Giorgos Myrianthous](https://towardsdatascience.com/author/gmyrianthous/)\nApril 20, 20226 min read\n  * [![](../images/002.jpeg)](https://towardsdatascience.com/my-experience-changing-careers-to-become-a-data-analyst-7d45d1f0f162/)\n## [My Experience Changing Careers to Become a Data Analyst](https://towardsdatascience.com/my-experience-changing-careers-to-become-a-data-analyst-7d45d1f0f162/)\n[Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/)\nHow to decide if data analytics is the right career for you\n[Vicky Yu](https://towardsdatascience.com/author/madfordata/)\nDecember 4, 20203 min read\n  * [![](../images/003.jpeg)](https://towardsdatascience.com/the-most-for-your-money-from-amazon-s3-6536c78189da/)\n## [The Most for Your Money from Amazon S3](https://towardsdatascience.com/the-most-for-your-money-from-amazon-s3-6536c78189da/)\n[Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/)\nLeverage the power of cloud storage with frugality in mind.\n[Vel Lesikov](https://towardsdatascience.com/author/vel-lesikov/)\nOctober 12, 20216 min read\n  * [![](../images/004.jpg)](https://towardsdatascience.com/tensorflow-transform-ensuring-seamless-data-preparation-in-production-99ffcf49f535/)\n## [TensorFlow Transform: Ensuring Seamless Data Preparation in Production](https://towardsdatascience.com/tensorflow-transform-ensuring-seamless-data-preparation-in-production-99ffcf49f535/)\n[Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/)\nLeveraging TensorFlow Transform for scaling data pipelines for production environments\n[Akila Somasundaram](https://towardsdatascience.com/author/akila29/)\nJuly 8, 20249 min read\n  * [![](../images/005.jpg)](https://towardsdatascience.com/i-replaced-vector-dbs-with-googles-memory-agent-pattern-for-my-notes-in-obsidian/)\n## [I Replaced Vector DBs with Google’s Memory Agent Pattern for my notes in Obsidian](https://towardsdatascience.com/i-replaced-vector-dbs-with-googles-memory-agent-pattern-for-my-notes-in-obsidian/)\n[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)\nPersistent AI memory without embeddings, Pinecone, or a PhD in similarity search.\n[Nick Lawson](https://towardsdatascience.com/author/ccrngd1/)\nApril 3, 202611 min read\n  * [![](../images/006.jpg)](https://towardsdatascience.com/automate-sap-report-extraction-with-pyautogui-f115ae19b653/)\n## [Automate SAP Report Extraction with Pyautogui](https://towardsdatascience.com/automate-sap-report-extraction-with-pyautogui-f115ae19b653/)\n[Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/)\nA guide to saving your time from the most tedious task in the world.\n[Pathairush Seeda](https://towardsdatascience.com/author/padpathairush/)\nApril 17, 20218 min read\n  * [![](../images/007.png)](https://towardsdatascience.com/should-an-engineer-learn-r-or-python-c91b36215a91/)\n## [Should An Engineer Learn R or Python?](https://towardsdatascience.com/should-an-engineer-learn-r-or-python-c91b36215a91/)\n[Data Science](https://towardsdatascience.com/category/data-science/)\nAn Honest And Actionable Review\n[Brock Taute](https://towardsdatascience.com/author/tautebro12/)\nFebruary 18, 20217 min read\n  * [![](../images/008.jpg)](https://towardsdatascience.com/a-common-mistake-to-avoid-when-working-with-time-series-data-eedf60a8b4c1/)\n## [How NOT to Analyze Time Series](https://towardsdatascience.com/a-common-mistake-to-avoid-when-working-with-time-series-data-eedf60a8b4c1/)\n[Data Science](https://towardsdatascience.com/category/data-science/)\nOne of the most common time series data mistakes I see junior data scientists and interview candidates make is to assume that the data has...\n[Yifei Huang](https://towardsdatascience.com/author/yifei-huang/)\nSeptember 29, 20213 min read\n  * [![](../images/009.png)](https://towardsdatascience.com/setting-a-dockerized-python-environment-the-elegant-way-f716ef85571d/)\n## [Setting A Dockerized Python Environment - The Elegant Way](https://towardsdatascience.com/setting-a-dockerized-python-environment-the-elegant-way-f716ef85571d/)\n[Data Science](https://towardsdatascience.com/category/data-science/)\nThis post provides a step-by-step guide for setting up a Python dockerized development environment with VScode and the Dev Containers...\n[Rami Krispin](https://towardsdatascience.com/author/rami.krispin/)\nApril 2, 20249 min read\n\n\n  * [YouTube](https://www.youtube.com/c/TowardsDataScience)\n  * [X](https://x.com/TDataScience)\n  * [LinkedIn](https://www.linkedin.com/company/towards-data-science/)\n  * [Threads](https://www.threads.net/@towardsdatascience)\n  * [Bluesky](https://bsky.app/profile/towardsdatascience.com)\n\n\n[](https://towardsdatascience.com/)\nYour home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals.\nSubscribe 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/)\n© Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network)\n####  Recommended Articles \nClose\n  * [ ![](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\")\n  * [ ![](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\")\n  * [ ![](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?\")\n  * [ ![](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\")\n\n\n",
  "metadata": {
    "title": "I Thought Data Engineering Was Just Writing Scripts. I Was Wrong. | Towards Data Science",
    "description": "I tried to make my ETL pipeline production-ready. Three things broke. Each one taught me something scripting alone never could.",
    "keywords": null,
    "author": "Ibrahim Salami",
    "og:locale": "en_US",
    "og:type": "article",
    "og:title": "I Thought Data Engineering Was Just Writing Scripts. I Was Wrong.",
    "og:description": "I tried to make my ETL pipeline production-ready. Three things broke. Each one taught me something scripting alone never could.",
    "og:url": "https://towardsdatascience.com/i-thought-data-engineering-was-just-writing-scripts-i-was-wrong/",
    "og:site_name": "Towards Data Science",
    "og:image": "https://assets.insightmediagroup.io/media/wp-content/uploads/2026/06/data-engineering-scripts.jpg",
    "og:image:width": "756",
    "og:image:height": "412",
    "og:image:type": "image/jpeg",
    "twitter:card": "summary_large_image",
    "twitter:site": "@TDataScience",
    "twitter:creator": "@TDataScience",
    "twitter:label1": "Written by",
    "twitter:data1": "Ibrahim Salami",
    "twitter:label2": "Est. reading time",
    "twitter:data2": "8 min read",
    "article:published_time": "2026-06-12T07:30:07.000Z",
    "article:modified_time": "2026-06-12T07:30:07.000Z",
    "article:author": "https://towardsdatascience.com/author/ibrahim.salami/"
  },
  "paywall": {
    "listed_paid": false,
    "detected": false,
    "marker": "",
    "public_only": false,
    "policy": "付费/会员内容只保留页面公开可见部分，不绕过付费墙"
  },
  "crawl": {
    "success": true,
    "status_code": 202,
    "error": ""
  },
  "code_blocks": [
    {
      "language": "txt",
      "file": "attachments/142ec8d51cc4/code/block_000.txt",
      "chars": 1054
    },
    {
      "language": "txt",
      "file": "attachments/142ec8d51cc4/code/block_001.txt",
      "chars": 47
    },
    {
      "language": "txt",
      "file": "attachments/142ec8d51cc4/code/block_002.txt",
      "chars": 65
    },
    {
      "language": "txt",
      "file": "attachments/142ec8d51cc4/code/block_003.txt",
      "chars": 195
    },
    {
      "language": "txt",
      "file": "attachments/142ec8d51cc4/code/block_004.txt",
      "chars": 159
    },
    {
      "language": "txt",
      "file": "attachments/142ec8d51cc4/code/block_005.txt",
      "chars": 125
    },
    {
      "language": "txt",
      "file": "attachments/142ec8d51cc4/code/block_006.txt",
      "chars": 1762
    }
  ],
  "images": [
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T18:07:57Z"
    },
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T18:07:57Z"
    },
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T18:07:57Z"
    },
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/4970/image?etag=1780565225463&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/4970/image?etag=1780565225463&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T18:07:57Z"
    }
  ],
  "audio": [],
  "videos": [
    {
      "url": "https://www.youtube.com/@ibbysalam",
      "kind": "channel_reference",
      "status": "reference_only"
    },
    {
      "url": "https://www.youtube.com/c/TowardsDataScience",
      "kind": "channel_reference",
      "status": "reference_only"
    }
  ],
  "links": [
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/latest/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/editors-pick/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/the-variable/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/shipai/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/submissions/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/category/data-science/data-engineering/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/author/ibrahim.salami/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/from-data-analyst-to-data-engineer-my-12-month-self-study-roadmap/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/i-built-my-first-etl-pipeline-as-a-complete-beginner-heres-exactly-how/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/data-engineering/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/data-pipeline/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/data-science/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/etl/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/python/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/parallel-computing-92c4f818c/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/category/programming/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/author/gmyrianthous/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/my-experience-changing-careers-to-become-a-data-analyst-7d45d1f0f162/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/category/artificial-intelligence/machine-learning/"
    },
    {
      "type": "external",
      "href": "https://write.insightmediagroup.io"
    },
    {
      "type": "external",
      "href": "https://www.linkedin.com/company/towards-data-science/"
    },
    {
      "type": "external",
      "href": "https://x.com/TDataScience"
    },
    {
      "type": "external",
      "href": "https://roadmap.sh/data-engineer"
    },
    {
      "type": "external",
      "href": "https://www.linkedin.com/in/ibrahim-salami-059863228/"
    },
    {
      "type": "external",
      "href": "https://www.youtube.com/@ibbysalam"
    },
    {
      "type": "external",
      "href": "https://x.com/IbbySalam"
    },
    {
      "type": "external",
      "href": "https://www.facebook.com/sharer/sharer.php?title=I+Thought+Data+Engineering+Was+Just+Writing+Scripts.+I+Was+Wrong.&u=https%3A%2F%2Ftowardsdatascience.com%2Fi-thought-data-engineering-was-just-writing-scripts-i-was-wrong%2F"
    },
    {
      "type": "external",
      "href": "https://www.linkedin.com/shareArticle?mini=true&title=I+Thought+Data+Engineering+Was+Just+Writing+Scripts.+I+Was+Wrong.&url=https%3A%2F%2Ftowardsdatascience.com%2Fi-thought-data-engineering-was-just-writing-scripts-i-was-wrong%2F"
    },
    {
      "type": "external",
      "href": "https://x.com/share?text=I+Thought+Data+Engineering+Was+Just+Writing+Scripts.+I+Was+Wrong.&url=https%3A%2F%2Ftowardsdatascience.com%2Fi-thought-data-engineering-was-just-writing-scripts-i-was-wrong%2F"
    },
    {
      "type": "external",
      "href": "https://www.youtube.com/c/TowardsDataScience"
    },
    {
      "type": "external",
      "href": "https://www.threads.net/@towardsdatascience"
    },
    {
      "type": "external",
      "href": "https://bsky.app/profile/towardsdatascience.com"
    },
    {
      "type": "external",
      "href": "https://thenewstack.io"
    },
    {
      "type": "external",
      "href": "https://roadmap.sh"
    },
    {
      "type": "external",
      "href": "https://insightmediagroup.io/creator-network"
    }
  ],
  "repair_version": 2,
  "repaired_at": "2026-10-20T17:33:17Z",
  "source_url": "https://towardsdatascience.com/i-thought-data-engineering-was-just-writing-scripts-i-was-wrong/",
  "delivery_status": "unverified",
  "discovery_status": "http_403",
  "missing_reason": "源页面未重新核验:http_403；已按保留正文补采图片",
  "repair_error": "",
  "actual_video_files": [],
  "expected_saved_body_images": 4,
  "image_discovery": "saved_markdown",
  "source_body_markdown": "![Revisit consent button](https://cdn-cookieyes.com/assets/images/revisit.svg)\nWe value your privacy\nWe 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.\nCustomise Reject All Accept All\nCustomise Consent Preferences ![](https://cdn-cookieyes.com/assets/images/close.svg)\nWe use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.\nThe 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\nNecessaryAlways Active\nNecessary 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.\n  * Cookie\nBCTempID\n  * Duration\n10 minutes\n  * Description\nNo description available.\n\n\n  * Cookie\n__cf_bm\n  * Duration\n1 hour\n  * Description\nThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management. \n\n\n  * Cookie\nAWSALBCORS\n  * Duration\n7 days\n  * Description\nAmazon Web Services set this cookie for load balancing.\n\n\n  * Cookie\n_cfuvid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services\n\n\n  * Cookie\nli_gc\n  * Duration\n6 months\n  * Description\nLinkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.\n\n\n  * Cookie\n__hssrc\n  * Duration\nsession\n  * Description\nThis 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.\n\n\n  * Cookie\n__hssc\n  * Duration\n1 hour\n  * Description\nHubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.\n\n\n  * Cookie\nwpEmojiSettingsSupports\n  * Duration\nsession\n  * Description\nWordPress 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.\n\n\n  * Cookie\nBCSessionID\n  * Duration\n1 year 1 month 4 days\n  * Description\nBlueconic sets this cookie as a unique identifier for the BlueConic profile.\n\n\n  * Cookie\n_octo\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nlogged_in\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\n__Secure-YEC\n  * Duration\npast\n  * Description\nYouTube sets this cookie to stores the user's video player preferences using embedded YouTube video\n\n\n  * Cookie\n__eoi\n  * Duration\n6 months\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTGCORS\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\nlogin-status-p\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTG\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\ncsrf_token\n  * Duration\nsession\n  * Description\nNo description available.\n\n\n  * Cookie\ntoken_v2\n  * Duration\n1 day\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nD\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nPHPSESSID\n  * Duration\nsession\n  * Description\nThis 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.\n\n\n  * Cookie\nVISITOR_PRIVACY_METADATA\n  * Duration\n6 months\n  * Description\nYouTube sets this cookie to store the user's cookie consent state for the current domain. \n\n\n  * Cookie\ncookietest\n  * Duration\nsession\n  * Description\nThe cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience.\n\n\n  * Cookie\n__Host-airtable-session\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\n__Host-airtable-session.sig\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\nm\n  * Duration\n1 year 1 month 4 days\n  * Description\nStripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly.\n\n\n  * Cookie\nBIGipServer*\n  * Duration\nsession\n  * Description\nMarketo 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. \n\n\n  * Cookie\n__cfruid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to identify trusted web traffic.\n\n\n  * Cookie\n_GRECAPTCHA\n  * Duration\n6 months\n  * Description\nGoogle Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks.\n\n\n  * Cookie\n__Secure-YNID\n  * Duration\n6 months\n  * Description\nGoogle cookie used to protect user security and prevent fraud, especially during the login process.\n\n\n  * Cookie\ncookieyes-consent\n  * Duration\n1 year\n  * Description\nCookieYes 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.\n\n\nFunctional\nFunctional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.\n  * Cookie\nlidc\n  * Duration\n1 day\n  * Description\nLinkedIn sets the lidc cookie to facilitate data center selection.\n\n\n  * Cookie\nbrw\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nbrwConsent\n  * Duration\n5 minutes\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nWMF-Uniq\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nloom_anon_comment\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nloom_referral_video\n  * Duration\nsession\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nVISITOR_INFO1_LIVE\n  * Duration\n6 months\n  * Description\nA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.\n\n\n  * Cookie\nyt-remote-connected-devices\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nytidb::LAST_RESULT_ENTRY_KEY\n  * Duration\nNever Expires\n  * Description\nThe 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.\n\n\n  * Cookie\nyt-remote-device-id\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-name\n  * Duration\nsession\n  * Description\nThe yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\nyt-remote-fast-check-period\n  * Duration\nsession\n  * Description\nThe yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-app\n  * Duration\nsession\n  * Description\nThe yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-available\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-installed\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\ncp_session\n  * Duration\n3 months\n  * Description\nCodepen sets this cookie for Help systems found in the website.\n\n\n  * Cookie\nloid\n  * Duration\n1 year 1 month 4 days\n  * Description\nThis cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform.\n\n\nAnalytics\nAnalytical 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.\n  * Cookie\n__hstc\n  * Duration\n6 months\n  * Description\nHubspot 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).\n\n\n  * Cookie\nhubspotutk\n  * Duration\n6 months\n  * Description\nHubSpot 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.\n\n\n  * Cookie\n_ga\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle 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.\n\n\n  * Cookie\n_ga_*\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle Analytics sets this cookie to store and count page views.\n\n\n  * Cookie\n__Host-psifi.analyticsTrace\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n__Host-psifi.analyticsTraceV2\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n_gh_sess\n  * Duration\nsession\n  * Description\nGitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form.\n\n\n  * Cookie\nYSC\n  * Duration\nsession\n  * Description\nYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.\n\n\n  * Cookie\najs_anonymous_id\n  * Duration\n1 year\n  * Description\nThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.\n\n\n  * Cookie\nvuid\n  * Duration\n1 year 1 month 4 days\n  * Description\nVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. \n\n\nPerformance\nPerformance 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.\n  * Cookie\nAWSALB\n  * Duration\n7 days\n  * Description\nAWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target.\n\n\n  * Cookie\nacq\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nacq.sig\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nptc\n  * Duration\n2 years\n  * Description\nNo description available.\n\n\nAdvertisement\nAdvertisement 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.\n  * Cookie\nmuc_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to collect user behaviour and interaction data to optimize the website.\n\n\n  * Cookie\nguest_id_marketing\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\nguest_id_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\npersonalization_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter 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.\n\n\n  * Cookie\nguest_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter 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.\n\n\n  * Cookie\nbcookie\n  * Duration\n1 year\n  * Description\nLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.\n\n\n  * Cookie\n__Secure-ROLLOUT_TOKEN\n  * Duration\n6 months\n  * Description\nYouTube 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.\n\n\n  * Cookie\nyt.innertube::nextId\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nyt.innertube::requests\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nsession_tracker\n  * Duration\nsession\n  * Description\nThis cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website.\n\n\n  * Cookie\nedgebucket\n  * Duration\nsession\n  * Description\nReddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content.\n\n\n  * Cookie\ndid\n  * Duration\n1 year\n  * Description\nArbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year.\n\n\nUncategorised\nOther uncategorised cookies are those that are being analysed and have not been classified into a category as yet.\nNo cookies to display.\nReject All Save My Preferences Accept All\nToggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation\n[](https://towardsdatascience.com/)\nPublish AI, ML & data-science insights to a global community of data professionals.\nSign in[Submit an Article](https://write.insightmediagroup.io)\n[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/)\n* * *\n[Write For TDS](https://towardsdatascience.com/submissions/)\n[LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search\n[Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/)\n# I Thought Data Engineering Was Just Writing Scripts. I Was Wrong.\nI tried to make my ETL pipeline production-ready. Three things broke. Each one taught me something scripting alone never could.\n[Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/)\nJune 12, 20268 min read\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/06/data-engineering-scripts.jpg)\nCreated with Gemini AI\nAfter I built my first ETL pipeline, I thought I had a pretty good grip on what data engineering actually was. You extract data from somewhere, you clean it up, you load it somewhere useful. ETL. Simple enough.\nFor context, I am a data analyst trying to transition into data engineering. I have been documenting that journey publicly, starting with a [12-month self-study roadmap](https://towardsdatascience.com/from-data-analyst-to-data-engineer-my-12-month-self-study-roadmap/) I put together earlier this year. The most recent step in that journey was [building my first ETL pipeline from scratch](https://towardsdatascience.com/i-built-my-first-etl-pipeline-as-a-complete-beginner-heres-exactly-how/) using the GitHub API, which I wrote about here on TDS. That pipeline worked. It pulled data, cleaned it, saved it to a CSV. I was happy with it.\nSo I decided to push it further, make it more \"production-ready\" as the internet likes to say. What happened next genuinely surprised me. Not because things broke, but because of what the breaking revealed.\n## The Original Pipeline\nThe original pipeline was basic, which was fine because that was the point. Extract data from the GitHub API, do a bit of cleaning, save everything to a CSV file. It worked perfectly for what it was: a learning exercise. But a CSV file and a one-time script is not how data engineering works in the real world. I wanted to find out what \"real world\" actually meant in practice, so I decided to push the pipeline further and see what happened.\nLearn this step by step with the interactive [Data Engineer](https://roadmap.sh/data-engineer) roadmap.\nHere is the full original pipeline for anyone who hasn't read the previous article:\npython\n\n```\nimport requests\nfrom datetime import datetime, timedelta\n\nurl = \"https://api.github.com/search/repositories\"\nparams = {\n    \"q\": \"language:python created:>2025-04-22\",\n    \"sort\": \"stars\",\n    \"order\": \"desc\",\n    \"per_page\": 30\n}\n\nresponse = requests.get(url, params=params)\ndata = response.json()\n\nimport pandas as pd\nrepos = []\nfor repo in data['items']:\n    repos.append({\n        \"name\": repo['name'],\n        \"owner\": repo['owner']['login'],\n        \"stars\": repo['stargazers_count'],\n        \"forks\": repo['forks_count'],\n        \"language\": repo['language'],\n        \"description\": repo['description'],\n        \"url\": repo['html_url'],\n        \"created_at\": repo['created_at']\n    })\n\ndf = pd.DataFrame(repos)\ndf_clean = df.dropna(subset=['description'])\ndf_clean = df_clean.copy()\ndf_clean['viral'] = df_clean['stars'].apply(lambda x: 'Yes' if x > 50000 else 'No')\ndf_clean = df_clean.sort_values('stars', ascending=False).reset_index(drop=True)\n\ndf_clean.to_csv('github_trending_repos.csv', index=False)\nprint(\"Pipeline complete. File saved.\")\n```\n\nSimple, readable, and it works. But the moment you try to run it more than once, or come back to it the next day, the cracks start to show.\n## Wall One: The Pipeline Had No Memory\nThe first upgrade was straightforward. Instead of saving to a CSV file, I loaded the data into a SQLite database. SQLite is still just a single file, but it behaves like a real database. You can query it, check what's already in it, and build on top of it properly. It felt like a small change. It wasn't.\nI ran the pipeline once and got 22 repos. Then I ran it a second time without changing anything and checked the database.\nmarkup\n\n```\nTotal rows: 44 Unique repos: 22 Duplicates: 22\n```\n\nHonestly, I didn't expect it. I guessed it could happen but I never really thought it would. But I'm glad it did, because it was the first time I actually watched my pipeline break. And what it revealed was simple but important: the script had no memory. Every time it ran, it started completely fresh and blindly appended whatever it found. No warning, no error. Just \"Pipeline complete\" like everything was fine.\nThis is where I came across a concept called idempotency.  \nIdempotency is a fancy word for a simple idea. If something has already happened, it shouldn't happen again. In the context of a data pipeline, it means that running your pipeline once or running it ten times should always produce the same result. No extra rows, no duplicates, no silent corruption of your data.\nThe fix was straightforward in principle. Before inserting anything into the database, the pipeline now checks if that record already exists. If it does, it removes it first, then inserts the fresh version. One small change in thinking, but it completely changes how reliable your pipeline is.\nAnd here's the part that stuck with me: a basic script will never think about this on its own. You have to build it in deliberately. That's not scripting anymore. That's engineering.\n## Wall Two: The Data Disappeared Overnight\nThe second wall was less technical and more unsettling.\nWhen I closed Colab for the night and came back the next day, there was this uneasy feeling. I had to run everything again from scratch and hope nothing broke, even though everything had worked perfectly the night before. The database I had carefully built was just gone. And I remembered that before this project, I had actually struggled to find my original ETL pipeline file. I spent time looking for it before I finally did. That feeling of almost losing your work stays with you.\nI knew there had to be a better way. A real pipeline cannot depend on someone being there to rerun it every morning. The data has to live somewhere that survives beyond the session.\nThe fix here was mounting Google Drive directly inside Colab and pointing the database connection there instead of to the temporary Colab environment. One line change:\npython\n\n```\nconn = sqlite3.connect('/content/drive/MyDrive/github_repos.db')\n```\n\nNow the database lives in Google Drive. Close the session, restart the runtime, open a new notebook entirely. The data is still there waiting.\nBut this fix revealed something bigger. If persisting data already requires thinking about where things live and how they survive, what happens when you need the pipeline to run automatically every day without you touching it at all?\n## Wall Three: Nobody Can Press Run Forever\nThe third wall was the one that excited me the most, which surprised me.\nEven with the duplicate problem solved and the database living safely in Google Drive, someone still has to open the notebook and press run. Colab is not a server. It is an interactive environment. It does not wake up at 3am, pull fresh data from the GitHub API, and go back to sleep. That is not what it was built for.\nAnd when I thought about it from a real world perspective, that clicked immediately. In an actual company, nobody is sitting there on alert at midnight waiting to run a script. The pipeline has to run itself. On a schedule. Reliably. Whether or not anyone is watching.\nThis is where tools like Apache Airflow, Prefect, and cloud-based cron jobs come in. These are not Python scripts. They are systems that live on servers, manage schedules, handle failures, send alerts when something goes wrong, and keep a history of every run.\nScheduling is honestly the concept I am most excited to dig into next, because it is where data engineering starts to feel like real infrastructure work.\n## Walking Through the Key Changes\nLet me walk through the three actual changes I made to the pipeline and what each one does.\n### 1. Swapping CSV for SQLite\npython\n\n```\n# Before\ndf_clean.to_csv('github_trending_repos.csv', index=False)\n\n# After\nconn = sqlite3.connect('github_repos.db')\ndf_clean.to_sql('repos', conn, if_exists='append', index=False)\nconn.close()\n```\n\nSaving to a CSV is fine for a one-time analysis. But a CSV is just a text file. You cannot easily query it, and it does not scale well as your data grows. SQLite is an actual database, which means you can run SQL queries on it, check what is already inside it, and build on top of it properly. Same simplicity, much more capability.\n### 2. Fixing the duplicate problem\npython\n\n```\ncursor.execute('''\n    DELETE FROM repos WHERE url IN (SELECT url FROM repos_temp)\n''')\ncursor.execute('''\n    INSERT INTO repos SELECT * FROM repos_temp\n''')\n```\n\nThis is the idempotency fix. Before inserting anything, the pipeline checks if that repo already exists in the database using its URL as a unique identifier. If it does, it deletes it first, then inserts the fresh version. So no matter how many times the pipeline runs, you always end up with clean, non-duplicated data.\n### 3. Persisting data to Google Drive\npython\n\n```\n# Before\nconn = sqlite3.connect('github_repos.db')\n\n# After\nconn = sqlite3.connect('/content/drive/MyDrive/github_repos.db')\n```\n\nThis is one line but it changes everything. Instead of saving the database to the temporary Colab environment where it disappears when the session closes, it saves directly to Google Drive. Close the notebook, restart the runtime, come back tomorrow. Your data is still there waiting for you.\nHere is the full upgraded pipeline putting all three changes together:\npython\n\n```\nimport requests\nimport pandas as pd\nimport sqlite3\nfrom datetime import datetime, timedelta\n\n# Extract\nyesterday = (datetime.now() - timedelta(days=1)).strftime('%Y-%m-%d')\n\nurl = \"https://api.github.com/search/repositories\"\nparams = {\n    \"q\": f\"language:python created:>{yesterday}\",\n    \"sort\": \"stars\",\n    \"order\": \"desc\",\n    \"per_page\": 30\n}\n\nresponse = requests.get(url, params=params)\ndata = response.json()\n\n# Transform\nrepos = []\nfor repo in data['items']:\n    repos.append({\n        \"name\": repo['name'],\n        \"owner\": repo['owner']['login'],\n        \"stars\": repo['stargazers_count'],\n        \"forks\": repo['forks_count'],\n        \"language\": repo['language'],\n        \"description\": repo['description'],\n        \"url\": repo['html_url'],\n        \"created_at\": repo['created_at']\n    })\n\ndf = pd.DataFrame(repos)\ndf_clean = df.dropna(subset=['description'])\ndf_clean = df_clean.copy()\ndf_clean['viral'] = df_clean['stars'].apply(lambda x: 'Yes' if x > 50000 else 'No')\ndf_clean = df_clean.sort_values('stars', ascending=False).reset_index(drop=True)\n\n# Load\nconn = sqlite3.connect('/content/drive/MyDrive/github_repos.db')\ncursor = conn.cursor()\n\ncursor.execute('''\n    CREATE TABLE IF NOT EXISTS repos (\n        name TEXT, owner TEXT, stars INTEGER, forks INTEGER,\n        language TEXT, description TEXT, url TEXT,\n        created_at TEXT, viral TEXT, loaded_at TEXT\n    )\n''')\n\ndf_clean['loaded_at'] = datetime.now().strftime('%Y-%m-%d')\ndf_clean.to_sql('repos_temp', conn, if_exists='replace', index=False)\n\ncursor.execute('''\n    DELETE FROM repos WHERE url IN (SELECT url FROM repos_temp)\n''')\ncursor.execute('''\n    INSERT INTO repos SELECT * FROM repos_temp\n''')\n\nconn.commit()\nconn.close()\nprint(\"Pipeline complete. Duplicates handled.\")\n```\n\n## So What Is Data Engineering, Really?\nIf you had asked me what data engineering was after I built my first ETL pipeline, I would have said it was mostly about writing scripts. Extract, transform, load. Repeat. That is what it looked like from the outside.\nBut after pushing that pipeline further and watching it break in three different ways, I think about it differently now. Data engineering is about building systems that are reliable, not just scripts that run. There is a difference. A script does what you tell it, once, when you tell it. A system handles failure, remembers what it has already done, persists data beyond a single session, and runs itself on a schedule without anyone watching.\nIdempotency, persistence, scheduling. None of these concepts showed up when I was running my pipeline once in a notebook. They only revealed themselves when I tried to make it work like something real.\nAnd in a real company, you cannot afford to get this wrong. The data your pipeline produces is being used to make decisions. If it is full of duplicates, or disappears overnight, or only runs when someone remembers to press a button, that is not a data pipeline. That is a liability.\nI still have a lot to learn. Scheduling is the next wall I am walking toward. But I am walking toward it now knowing that data engineering was never just about writing scripts. I just had to break a few things to see that.\n_This is an ongoing data engineering series. Follow along as I document every step of the journey, including the parts that don’t go smoothly._\n_Connect with me on_[ _LinkedIn_](https://www.linkedin.com/in/ibrahim-salami-059863228/) _,_[_YouTube_](https://www.youtube.com/@ibbysalam) _, and_[ _Twitter_](https://x.com/IbbySalam) _._\n## Register Now to Continue Reading\n### Unlock Towards Data Science with a Free Account\nAll articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more.\nRegister for freeSign in to your account\n* * *\n![](https://assets.insightmediagroup.io/media/1787657709013_9ddcph.jpeg)\nWritten By\n## [Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/)\n[See all from Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/)\n[Data Engineering](https://towardsdatascience.com/tag/data-engineering/)[Data Pipeline](https://towardsdatascience.com/tag/data-pipeline/)[Data Science](https://towardsdatascience.com/tag/data-science/)[Etl](https://towardsdatascience.com/tag/etl/)[Python](https://towardsdatascience.com/tag/python/)\nShare This Article\n  * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fi-thought-data-engineering-was-just-writing-scripts-i-was-wrong%2F&title=I%20Thought%20Data%20Engineering%20Was%20Just%20Writing%20Scripts.%20I%20Was%20Wrong.)\n  * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fi-thought-data-engineering-was-just-writing-scripts-i-was-wrong%2F&title=I%20Thought%20Data%20Engineering%20Was%20Just%20Writing%20Scripts.%20I%20Was%20Wrong.)\n  * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fi-thought-data-engineering-was-just-writing-scripts-i-was-wrong%2F&text=I%20Thought%20Data%20Engineering%20Was%20Just%20Writing%20Scripts.%20I%20Was%20Wrong.)\n\n\nTowards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program.\n[Write for TDS](https://towardsdatascience.com/submissions/)\n## Related Articles\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2022/06/1NVCf6SSB4U3JsOvOewdPHQ-scaled.jpeg)](https://towardsdatascience.com/parallel-computing-92c4f818c/)\n## [What is Parallel Computing?](https://towardsdatascience.com/parallel-computing-92c4f818c/)\n[Programming](https://towardsdatascience.com/category/programming/)\nUnderstanding the importance of parallel computing in the context of Data Engineering\n[Giorgos Myrianthous](https://towardsdatascience.com/author/gmyrianthous/)\nApril 20, 20226 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2020/12/16-eE-qCqDKCMIWVYqkjb2g.jpeg)](https://towardsdatascience.com/my-experience-changing-careers-to-become-a-data-analyst-7d45d1f0f162/)\n## [My Experience Changing Careers to Become a Data Analyst](https://towardsdatascience.com/my-experience-changing-careers-to-become-a-data-analyst-7d45d1f0f162/)\n[Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/)\nHow to decide if data analytics is the right career for you\n[Vicky Yu](https://towardsdatascience.com/author/madfordata/)\nDecember 4, 20203 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2021/10/15Um71EDFL4CstytERv1HwA-scaled.jpeg)](https://towardsdatascience.com/the-most-for-your-money-from-amazon-s3-6536c78189da/)\n## [The Most for Your Money from Amazon S3](https://towardsdatascience.com/the-most-for-your-money-from-amazon-s3-6536c78189da/)\n[Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/)\nLeverage the power of cloud storage with frugality in mind.\n[Vel Lesikov](https://towardsdatascience.com/author/vel-lesikov/)\nOctober 12, 20216 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2024/07/0rLFQK7315X-cZpFx-scaled.jpg)](https://towardsdatascience.com/tensorflow-transform-ensuring-seamless-data-preparation-in-production-99ffcf49f535/)\n## [TensorFlow Transform: Ensuring Seamless Data Preparation in Production](https://towardsdatascience.com/tensorflow-transform-ensuring-seamless-data-preparation-in-production-99ffcf49f535/)\n[Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/)\nLeveraging TensorFlow Transform for scaling data pipelines for production environments\n[Akila Somasundaram](https://towardsdatascience.com/author/akila29/)\nJuly 8, 20249 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/Gemini_Generated_Image_y59dgdy59dgdy59d-scaled-1.jpg)](https://towardsdatascience.com/i-replaced-vector-dbs-with-googles-memory-agent-pattern-for-my-notes-in-obsidian/)\n## [I Replaced Vector DBs with Google’s Memory Agent Pattern for my notes in Obsidian](https://towardsdatascience.com/i-replaced-vector-dbs-with-googles-memory-agent-pattern-for-my-notes-in-obsidian/)\n[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)\nPersistent AI memory without embeddings, Pinecone, or a PhD in similarity search.\n[Nick Lawson](https://towardsdatascience.com/author/ccrngd1/)\nApril 3, 202611 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2021/04/05JUvLuKA5wO9VY4O-scaled.jpg)](https://towardsdatascience.com/automate-sap-report-extraction-with-pyautogui-f115ae19b653/)\n## [Automate SAP Report Extraction with Pyautogui](https://towardsdatascience.com/automate-sap-report-extraction-with-pyautogui-f115ae19b653/)\n[Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/)\nA guide to saving your time from the most tedious task in the world.\n[Pathairush Seeda](https://towardsdatascience.com/author/padpathairush/)\nApril 17, 20218 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2021/02/1VpGpRVHB9QxP29R-F-BOWA.png)](https://towardsdatascience.com/should-an-engineer-learn-r-or-python-c91b36215a91/)\n## [Should An Engineer Learn R or Python?](https://towardsdatascience.com/should-an-engineer-learn-r-or-python-c91b36215a91/)\n[Data Science](https://towardsdatascience.com/category/data-science/)\nAn Honest And Actionable Review\n[Brock Taute](https://towardsdatascience.com/author/tautebro12/)\nFebruary 18, 20217 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2021/09/0BCNlSmMEA4OKy2bj-scaled.jpg)](https://towardsdatascience.com/a-common-mistake-to-avoid-when-working-with-time-series-data-eedf60a8b4c1/)\n## [How NOT to Analyze Time Series](https://towardsdatascience.com/a-common-mistake-to-avoid-when-working-with-time-series-data-eedf60a8b4c1/)\n[Data Science](https://towardsdatascience.com/category/data-science/)\nOne of the most common time series data mistakes I see junior data scientists and interview candidates make is to assume that the data has...\n[Yifei Huang](https://towardsdatascience.com/author/yifei-huang/)\nSeptember 29, 20213 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2024/04/1oibKw8sjdG54bYtey9lmqg.png)](https://towardsdatascience.com/setting-a-dockerized-python-environment-the-elegant-way-f716ef85571d/)\n## [Setting A Dockerized Python Environment - The Elegant Way](https://towardsdatascience.com/setting-a-dockerized-python-environment-the-elegant-way-f716ef85571d/)\n[Data Science](https://towardsdatascience.com/category/data-science/)\nThis post provides a step-by-step guide for setting up a Python dockerized development environment with VScode and the Dev Containers...\n[Rami Krispin](https://towardsdatascience.com/author/rami.krispin/)\nApril 2, 20249 min read\n\n\n  * [YouTube](https://www.youtube.com/c/TowardsDataScience)\n  * [X](https://x.com/TDataScience)\n  * [LinkedIn](https://www.linkedin.com/company/towards-data-science/)\n  * [Threads](https://www.threads.net/@towardsdatascience)\n  * [Bluesky](https://bsky.app/profile/towardsdatascience.com)\n\n\n[](https://towardsdatascience.com/)\nYour home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals.\nSubscribe 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/)\n© Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network)\n####  Recommended Articles \nClose\n  * [ ![](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\")\n  * [ ![](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\")\n  * [ ![](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?\")\n  * [ ![](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\")\n\n\n",
  "body_base_path": "attachments/142ec8d51cc4/pages/",
  "body_markdown_path": "attachments/142ec8d51cc4/pages/archived-body.md",
  "local_html": "attachments/142ec8d51cc4/pages/archived-body.html",
  "body_source": "prior_capture"
}