![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 Science](https://towardsdatascience.com/category/data-science/) # Collaboration-Friendly SQL Queries A few tips to improve the quality of your SQL queries and collaborate better [Naser Tamimi](https://towardsdatascience.com/author/tamimi-naser/) November 8, 20218 min read ### DATA ENGINEERING AND DATA SCIENCES ![Photo by the author.](../images/000.png) Photo by the author. A data pipeline is stuck and needs someone's attention. Or a query needs to be refactored using a new table because one of the used tables is getting deprecated or unavailable. Or we need to add more to our SQL logic of a very old data pipeline. In all those situations, we have a feeling after a few minutes. We either appreciate the previous code authors, or we get stuck in hundreds of lines of SQL queries. I bet most people (if not all) would like to get appreciated for their work. However, many data engineers and data scientists don't know how to craft SQL queries in collaboration-friendly ways. This article will give you some of the essential tips that help you develop professional and collaboration-friendly SQL queries and data pipelines. Learn this step by step with the interactive [AI and Data Scientist](https://roadmap.sh/ai-data-scientist), [Computer Science](https://roadmap.sh/computer-science) and [SQL](https://roadmap.sh/sql) roadmaps. ## Avoid SELECT * Don't get me wrong, I use SELECT _often, but only in my temporary ad-hoc queries to investigate tables or to do quick data check. Rarely (there are a few exceptions that I explain later) use SELECT_ in your pipelines or queries that are non-temporary. The reason that it is important not to use SELECT * is when you want to update or refactor your pipeline or query later. The first thing to update a query (for example, to replace a table with another table) is to understand what columns are used in the query/pipeline. Let's consider an example. Suppose we are maintaining a table for recognizing our senior employees based on some metrics. For some reason, we cannot use the `performance_review` table anymore (for example, because of some privacy concerns). Our task is to replace the `performance_review` table with other accessible tables. text ``` WITH current_senior_employees AS ( SELECT * FROM employee WHERE age>=45 AND is_current = true AND years_in_company >= 6 ), performance_last_5years AS ( SELECT * FROM performance_review WHERE year BETWEEN 2016 AND 2020 ) SELECT ARBITRARY(a.first_name), ARBITRARY(a.last_name), ARBITRARY(a.email), SUM(b.num_of_managed_employees) AS total_num_managed_employees, SUM(b.num_of_managed_projects) AS total_num_of_managed_projects, SUM(b.revenue_generated_by_managed_projects) AS total_revenue FROM current_senior_employees AS a LEFT JOIN avg_performance_last_5years AS b ON a.id = b.employee_id GROUP BY b.employee_id ``` As you can see, due to misuse of SELECT _, we cannot easily recognize what columns from which tables are required to maintain this table. We need to go deeper into the code to find out that_` _num_of_managed_employees_`_,_`_num_of_managed_projects_`_,_`_revenue_generated_by_managed_projects_`_, and_` _employee_id_`_are the columns that we should find in other tables. Of course, my example is super small compared to regular queries in real jobs, and it is not hard to find out which columns are used. But a single query could be hundreds of lines and tens of joined tables in real-life projects. In those situations, it is super hard to go deep into the code to find out which columns are coming from which tables if the programmer uses SELECT_ to read everything first and then select the columns from a bunch of loaded columns. In my example, a better way to write this query is: text ``` WITH current_senior_employees AS ( SELECT id, first_name, last_name, email FROM employee WHERE age>=45 AND is_current = true AND years_in_company >= 6 ), performance_last_5years AS ( SELECT employee_id, num_of_managed_employees, num_of_managed_projects, revenue_generated_by_managed_projects FROM performance_review WHERE year BETWEEN 2016 AND 2020 ) SELECT ARBITRARY(a.first_name), ARBITRARY(a.last_name), ARBITRARY(a.email), SUM(b.num_of_managed_employees) AS total_num_managed_employees, SUM(b.num_of_managed_projects) AS total_num_of_managed_projects, SUM(b.revenue_generated_by_managed_projects) AS total_revenue FROM current_senior_employees AS a LEFT JOIN avg_performance_last_5years AS b ON a.id = b.employee_id GROUP BY b.employee_id ``` ## Use aliases One of the bad practices is to avoid using aliases when you join multiple tables. Look a the following example. text ``` WITH current_senior_employees AS ( ... ), performance_last_5years AS ( ... ) SELECT ARBITRARY(first_name), ARBITRARY(last_name), ARBITRARY(email), SUM(num_of_managed_employees) AS total_num_managed_employees, SUM(num_of_managed_projects) AS total_num_of_managed_projects, SUM(revenue_generated_by_managed_projects) AS total_revenue FROM current_senior_employees LEFT JOIN avg_performance_last_5years ON id = employee_id GROUP BY employee_id ``` It is the same example as the previous section. The only difference is that I did not use aliases (e.g., `a` and `b`) here. In this example, it is difficult to figure out the `email` column is coming from which table. Just because the column name is unique, you should not stop using aliases (especially when you join multiple tables). Now imagine if I used SELECT * in addition to not using aliases. text ``` WITH current_senior_employees AS ( SELECT * FROM employee WHERE age>=45 AND is_current = true AND years_in_company >= 6 ), performance_last_5years AS ( SELECT * FROM performance_review WHERE year BETWEEN 2016 AND 2020 ) SELECT ARBITRARY(first_name), ARBITRARY(last_name), ARBITRARY(email), SUM(num_of_managed_employees) AS total_num_managed_employees, SUM(num_of_managed_projects) AS total_num_of_managed_projects, SUM(revenue_generated_by_managed_projects) AS total_revenue FROM current_senior_employees LEFT JOIN avg_performance_last_5years ON id = employee_id GROUP BY employee_id ``` Using SELECT * and avoiding aliases even for a simple query can lead to big confusion. Remember, use aliases to make your query more readable and easier to understand. ## No meaningless aliases Stop using meaningless aliases like a, b, c, and so on. The next bad thing after not using aliases is to use meaningless aliases. It is very common among data engineers and scientists to use simple aliases like a and b when they join tables. I am not against using a and b for temporary ad-hoc queries, but I do not use them for long-term queries or pipelines. When you share a query with someone else or go back to your query after a long time, it is not easy to understand it with meaningless aliases. Again for super short queries like the previous example, it is not hard to find out what a and b refer to, but when the query becomes long, it takes too much of our short-term memory to understand the query and fix it when necessary. For example, in my query, I could use: text ``` WITH current_senior_employees AS ( SELECT id, first_name, last_name, email FROM employee WHERE age>=45 AND is_current = true AND years_in_company >= 6 ), performance_last_5years AS ( SELECT employee_id, num_of_managed_employees, num_of_managed_projects, revenue_generated_by_managed_projects FROM performance_review WHERE year BETWEEN 2016 AND 2020 ) SELECT ARBITRARY(employee.first_name), ARBITRARY(employee.last_name), ARBITRARY(employee.email), SUM(perform.num_of_managed_employees) AS total_num_managed_employees, SUM(perform.num_of_managed_projects) AS total_num_of_managed_projects, SUM(perform.revenue_generated_by_managed_projects) AS total_revenue FROM current_senior_employees AS employee LEFT JOIN avg_performance_last_5years AS perform ON employee.id = perform.employee_id GROUP BY perform.employee_id ``` ## CTEs are friendly Don't be afraid to use CTEs. I have seen Data Engineers and Scientists who use complex nested subqueries to avoid using CTEs (for no obvious reason!). Let me show you how my example query becomes complex if I use subqueries instead of CTEs. text ``` SELECT ARBITRARY(employee.first_name), ARBITRARY(employee.last_name), ARBITRARY(employee.email), SUM(perform.num_of_managed_employees) AS total_num_managed_employees, SUM(perform.num_of_managed_projects) AS total_num_of_managed_projects, SUM(perform.revenue_generated_by_managed_projects) AS total_revenue FROM ( SELECT id, first_name, last_name, email FROM employee WHERE age>=45 AND is_current = true AND years_in_company >= 6 ) AS employee LEFT JOIN( SELECT employee_id, num_of_managed_employees, num_of_managed_projects, revenue_generated_by_managed_projects FROM performance_review WHERE year BETWEEN 2016 AND 2020 ) AS perform ON employee.id = perform.employee_id GROUP BY perform.employee_id ``` Imagine how complex this could be if we have tens of joined tables (sometimes nested). Remember, there are multiple benefits of using CTEs: 1. CTEs are friendly to human short memory (more organized). 2. You can use a CTE multiple times in a query and make your query more organized (opposed to subqueries). ## Base query using JINJA2 Jinja2 is very popular among data engineers and scientists to develop data pipelines. It enables them to make dynamic queries and compact large ETL queries via `Template()` function. Here I only focus on one of the hundreds of Jinja2 Template applications. My focus is to show you how Jinja2 Template can help you to write more clear SQL queries. If you have multiple queries in your pipeline that use the same CTE or subquery, consider using defining a base query and replacing it in your queries via Jinja2. Here is an example of a pseudo query. text ``` WITH cte1 AS ( SELECT ... FROM table3 JOIN ( SELECT ... FROM table1 JOIN table2 ON table1.col1 = table2.col2 WHERE ... AND ... ) AS table_x ON ... WHERE ...), cte2 AS ( SELECT ... FROM table4 JOIN ( SELECT ... FROM table1 JOIN table2 ON table1.col1 = table2.col2 WHERE ... AND ... ) AS table_x ON ... WHERE ...), ) SELECT ... FROM cte1 JOIN cte2 ON ... WHERE ... ``` If you look closely, you notice that the bolded subquery is repeated in both `cte1` and `cte2`. Using Jinja2 Template (for example, in Python), you can define a base query for the repeated query and replace it within the main query. You might argue that we can define a CTE instead of using the Jinja2 Template in this example. You are absolutely right! If there is only one query in your pipeline with such a subquery, using a CTE is a much better solution. Still, if you have multiple individual queries in your pipeline (for example, for different tasks) that use the same subquery, then you can use Jinja2 Template to share the same query between them. If you don't know how to use Jinja2 Template, here is an example in Python. text ``` from jinja2 import Template ``` text ``` base_query = """ SELECT ... FROM table1 JOIN table2 ON table1.col1 = table2.col2 WHERE ... AND ... """ ``` text ``` main_query = Template(""" WITH cte1 AS ( SELECT ... FROM table3 JOIN ({{subquery}}) AS table_x ON ... WHERE ...), cte2 AS ( SELECT ... FROM table4 JOIN ({{subquery}}) AS table_x ON ... WHERE ...), ) SELECT ... FROM cte1 JOIN cte2 ON ... WHERE ... """).render(subquery=base_query) ``` ## Some final (but important!!!) tips In the end, I would like to have some crucial general advice for you on how to craft your queries or pipeline for better collaboration. Thanks to the query optimization feature of most relational database systems, the query you write get optimized before it gets executed. Therefore, in many cases, you may write an inefficient query (for example, loading all columns in a CTE and then selecting columns). However, the optimizer finds an optimum query plan for execution, and the machine performance is still good. However, always remember, just because the optimizer is helping you to have a better performance, it does not mean that you can write queries any way you like. We must be considerate of people who collaborate with us now and in the future to maintain the code. Finally, if you think something might take your time at the query development stage, but it will save time later for those who read it, you must do it. For example, it might take you a little bit of time to find and use a proper alias name instead of random "a" or "b," but it will save much time later for those who read it later (even yourself). * * * Follow me on [Medium](https://tamimi-naser.medium.com/) and [Twitter](https://twitter.com/TamimiNas) for the latest stories. ## 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-909ce5c2500185af5a85.jpeg) Written By ## [Naser Tamimi](https://towardsdatascience.com/author/tamimi-naser/) [See all from Naser Tamimi](https://towardsdatascience.com/author/tamimi-naser/) [Data Science](https://towardsdatascience.com/tag/data-science/)[Programming](https://towardsdatascience.com/tag/programming/)[Software Development](https://towardsdatascience.com/tag/software-development/)[Sql](https://towardsdatascience.com/tag/sql/)[Technology](https://towardsdatascience.com/tag/technology/) Share This Article * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fcollaboration-friendly-sql-queries-ee7e14547a61%2F&title=Collaboration-Friendly%20SQL%20Queries) * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fcollaboration-friendly-sql-queries-ee7e14547a61%2F&title=Collaboration-Friendly%20SQL%20Queries) * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fcollaboration-friendly-sql-queries-ee7e14547a61%2F&text=Collaboration-Friendly%20SQL%20Queries) 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.png)](https://towardsdatascience.com/field-boundary-detection-in-satellite-imagery-using-the-sam2-model-b556aa97bf7a/) ## [Field Boundary Detection in Satellite Imagery Using the SAM2 Model](https://towardsdatascience.com/field-boundary-detection-in-satellite-imagery-using-the-sam2-model-b556aa97bf7a/) [Data Science](https://towardsdatascience.com/category/data-science/) Step-by-Step Tutorial on Applying Segment Anything Model Version 2 to Satellite Imagery for Detecting and Exporting Field Boundaries in... [Mahyar Aboutalebi](https://towardsdatascience.com/author/mahyar.aboutalebi/) November 15, 202413 min read * [![](../images/002.jpg)](https://towardsdatascience.com/heres-how-openai-codex-will-revolutionize-programming-and-the-world-e8432aafc5f7/) ## [Here's How OpenAI Codex Will Revolutionize Programming (and the World)](https://towardsdatascience.com/heres-how-openai-codex-will-revolutionize-programming-and-the-world-e8432aafc5f7/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) "Codex gets close to what most of us really want from computers - we say what we want, and they do it." - Sam Altman [Alberto Romero](https://towardsdatascience.com/author/albertoromgar/) August 11, 202112 min read * [![](../images/003.png)](https://towardsdatascience.com/python-list-comprehension-is-not-just-syntactic-sugar-346463b4853d/) ## [Python List Comprehension Is Not Just Syntactic Sugar](https://towardsdatascience.com/python-list-comprehension-is-not-just-syntactic-sugar-346463b4853d/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) "Pythonic" is not a good reason. Why is the performance better? When not to use it? [Christopher Tao](https://towardsdatascience.com/author/christophertao/) April 8, 20248 min read * [![](../images/004.jpg)](https://towardsdatascience.com/automatically-detecting-label-errors-in-datasets-with-cleanlab-e0a3ea5fb345/) ## [Automatically Detecting Label Errors in Datasets with CleanLab](https://towardsdatascience.com/automatically-detecting-label-errors-in-datasets-with-cleanlab-e0a3ea5fb345/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) A Tale of AI and wrongly-classified Brazilian Federal Laws [João Pedro](https://towardsdatascience.com/author/joaopedro214/) July 22, 202310 min read * [![](../images/005.jpg)](https://towardsdatascience.com/train-your-mind-to-think-recursively-in-5-steps-8f85c0e0eb81/) ## [Train Your Mind to Think Recursively in 5 Steps](https://towardsdatascience.com/train-your-mind-to-think-recursively-in-5-steps-8f85c0e0eb81/) [Programming](https://towardsdatascience.com/category/programming/) How to solve recursive problems easily? [Sara A. Metwalli](https://towardsdatascience.com/author/saraametwalli/) October 31, 20207 min read * [![](../images/006.png)](https://towardsdatascience.com/find-the-best-matching-distribution-for-your-data-effortlessly-bcc091aa08ab/) ## [Find the Best-matching Distribution for Your Data Effortlessly](https://towardsdatascience.com/find-the-best-matching-distribution-for-your-data-effortlessly-bcc091aa08ab/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) How to find the best-matching statistical distributions for your data points - in an automated and easy way. [Tirthajyoti Sarkar](https://towardsdatascience.com/author/tirthajyoti/) August 17, 20215 min read * [![](../images/007.jpeg)](https://towardsdatascience.com/3-beginner-mistakes-ive-made-in-my-data-science-career-a177f1cf751b/) ## [3 Beginner Mistakes I've Made in My Data Science Career](https://towardsdatascience.com/3-beginner-mistakes-ive-made-in-my-data-science-career-a177f1cf751b/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) Writing this feels like career suicide [Arunn Thevapalan](https://towardsdatascience.com/author/arunnthevapalan/) April 29, 20218 min read * [![](../images/008.jpg)](https://towardsdatascience.com/breaking-down-state-of-the-art-ppo-implementations-in-jax-6f102c06c149/) ## [A Practical Guide to Proximal Policy Optimization in JAX](https://towardsdatascience.com/breaking-down-state-of-the-art-ppo-implementations-in-jax-6f102c06c149/) [Programming](https://towardsdatascience.com/category/programming/) All the tricks and details you wish you knew about PPO [Ryan Pégoud](https://towardsdatascience.com/author/ryanpegoud/) May 1, 20248 min read * [![](../images/009.jpeg)](https://towardsdatascience.com/shannon-information-theory-discovering-particles-of-information-ab2c136c6a25/) ## [Shannon Information: Discovering Atoms of Communication](https://towardsdatascience.com/shannon-information-theory-discovering-particles-of-information-ab2c136c6a25/) [Data Science](https://towardsdatascience.com/category/data-science/) Physical objects have atoms, information has bits. Claude Shannon believes that information, although intangible, can be quantified... [Casey Cheng](https://towardsdatascience.com/author/casey-cheng/) March 21, 202214 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/607686/image?etag=1782161464448&width=500&height=500) How Relevance Models Foreshadowed Transformers for NLP ](https://towardsdatascience.com/how-relevance-models-foreshadowed-transformers-for-nlp/ "How Relevance Models Foreshadowed Transformers for NLP") * [ ![](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?")