![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
[Business](https://towardsdatascience.com/category/business/)
# Missing features in the data product movement
[Chad Isenberg](https://towardsdatascience.com/author/cisenbe/)
February 15, 20238 min read
# The Missing Features in Your Data Product
Engagement, delight, and trust as deliverables
I lead a monthly data discussion group at Zendesk, where I'm fortunate to get to hear a variety of thoughts and perspectives from smart, diverse, and talented people. We cover topics ranging from the [technical ](https://medium.com/airbnb-engineering/how-airbnb-achieved-metric-consistency-at-scale-f23cc53dea70)to the [procedural](https://benn.substack.com/p/how-dbt-fails), and we regularly tie these back to our work streams. Online discussion groups, local meetups, and conferences are terrific, but I feel there's even more value in getting the people in your organization together to discuss industry trends, as it can provide direction for your teams and their projects.
One of the themes we've been returning to is the idea of our team's value and how we can measure it. In an [earlier article](https://medium.com/towards-data-science/data-teams-as-support-teams-2bb1f1ed31b), I talked about how data teams generate value, but this isn't the only way. Regardless of whether you're providing business support, enabling automation through reverse ETL, or feeding data to advanced analytical and machine learning use-cases, there's always a lingering question: did we save or generate more than we spent?
As one of our attendees said, our customers frequently measure our impact "based on vibes." This shouldn't be taken as a slight, but rather a concession to the difficulty in creating firm metrics around impact and value. Additionally, embedded in this idea is that there is subjective and perhaps non-quantifiable value in analytical outputs, which we'll discuss in a moment.
Building an attribution model for data products is a notoriously tough nut to crack, and I won't try to tackle all of the elements here. While I believe we could benefit from a broad attribution framework, I don't know if that's even possible, given the number of ways data can reduce costs and increase revenue. Instead, I want to focus on a few specific components that I feel are neglected, in particular:
  1. The psychosocial value of data
  2. Customer delight and satisfaction
  3. Data quality as a core deliverable


Learn this step by step with the interactive [AI and Data Scientist](https://roadmap.sh/ai-data-scientist) and [Data Analyst](https://roadmap.sh/data-analyst) roadmaps.
## Are we cheerleaders?
This first observation is less about how we should be "doing data products" and more about what the table stakes are. During our discussion, I brought up the idea that we don't necessarily know why data-driven companies succeed, but [research indicates that they do](https://cisr.mit.edu/publication/2022_0101_Dashboarding_WeillWoerner). One person responded with this insight: maybe the dashboards aren't "doing anything," at least not in the sense of driving a specific, deliberate action. What if instead of (or in addition to) actionable insights, their value is in motivating and aligning our customers?
![Photo by Rojan Maharjan on Unsplash](../images/000.jpg)
Photo by [Rojan Maharjan](https://unsplash.com/@kathmandude_?utm_source=medium&utm_medium=referral) on [Unsplash](https://unsplash.com?utm_source=medium&utm_medium=referral)
At one point in my career, I was working as a BI developer for a wholesale company, and we had reporting that provided our sales team with summaries of their sales metrics. This report saw reasonable usage throughout the month, but it sky-rocketed at month-end, with some users refreshing several times an hour. I remember being completely bewildered by this trend.
I'm sure there were several operational use cases behind this behavior, but in hindsight, I believe one of the most valuable outputs of the report was motivation. Seeing their shipments go out in near real-time made our salespeople excited; it gave them the extra "oomph" to make calls and close deals as they rushed to meet or exceed quota. This reporting was doing very real work and driving a business process, even if it wasn't in the way that we would typically expect.
It's also worth noting that there's something inherently social about many of these data artifacts. A dashboard is a shared object and can serve as a common thread of conversation between colleagues. Even if the underlying data isn't remarkable or particularly insightful, the dialogues and shared narratives sparked by them can be valuable. Alignment is a powerful tool for an organization, and data can drive alignment.
As "objective" people, many data professionals may be reluctant to accept that "inspiration" is a valid or valuable output; however, we're missing something if we don't use data to motivate us. I resisted this idea initially, but reflecting on my career, I have many stories and anecdotes like the above, and I can't help but feel that this qualitative impact is significant. Perhaps the most important lesson I took away from this experience is that just because I couldn't perceive a mechanism for generating value doesn't mean that it didn't exist.
Finally, the narrative of the data showing us some hidden insight or a contrarian opinion is a trope at this point, but there's something powerful that happens when data affirms our beliefs and reassures us that we're on the right track. That data often supports the status quo rather than upends it should be celebrated, not feared.
## Bread and circuses
![Photo by Mathew Schwartz on Unsplash](../images/001.jpg)
Photo by [Mathew Schwartz](https://unsplash.com/@cadop?utm_source=medium&utm_medium=referral) on [Unsplash](https://unsplash.com?utm_source=medium&utm_medium=referral)
In the same vein, I believe it's important to consider whether or not our customers like our data products. This could range from providing ergonomic naming conventions and easily-consumable tables for analysts and data scientists to delivering aesthetically-pleasing dashboards for business users.
What does this look like? Should we be building in feedback mechanisms to our data products? Should we have surveys? I would caution that we don't want to be too heavy-handed; as with all internal products, we're at risk of having a tenuous relationship with the actual value chain (i. e., how we get paid).
Still, I think there's room for providing lightweight systems to drive feedback in the data product lifecycle. Which features are loved? Which are hated? When is it safe for a data product to go into "maintenance mode," and when do we sunset? In my experience, these questions are almost always raised in an ad-hoc fashion, and by that point in the product's lifecycle, even identifying active users can be complicated by process automation that has been long since forgotten.
## Quality as a deliverable
As we were closing our monthly meeting, [Niral Patel](https://www.linkedin.com/in/niralpatel/), one of the data engineering managers on my team, brought up this cogent point: why is quality an afterthought when it's a critical component to satisfy our customers' demands?
To some extent, this is a matter of resources. Data teams are frequently scrappy and asked to take on far more work than they're capable of delivering. They're mired in operational woes and unclear requirements. When pressed for time, delivering an incomplete thing is better than delivering nothing.
But like standardized tests where you're penalized for wrong answers, poor data quality damages trust. If your team consistently cranks out dashboards that are inaccurate, stale, and inconsistent, your customers will lose trust in you. And the damage isn't limited to you and your team; you're contributing to a culture of mistrust that can require years of work and huge turnover to repair.
We have a responsibility to our stakeholders to promote data quality as a key feature of our products, and we need to involve them in the tradeoffs. Since data quality has many [dimensions](https://towardsdatascience.com/the-six-dimensions-of-data-quality-and-how-to-deal-with-them-bdcf9a3dba71), our customers have to be involved in prioritizing: how should we handle unusual data volumes? What should we do when we encounter a schema change? Is it more important to deliver incomplete data on time or complete data late? While there's a sense of what "poor" data quality is, managing the tradeoffs in delivering "good" data is much more complicated and context-sensitive.
Important work is being done in the data governance space, and it's time to bring that to bear in our data products, from the start and every time. Quality is an essential feature, every bit as important as the design, interfaces, and use-cases enabled by our products.
## The metrics we need
While there are products and services that can provide us with usage data, the data in itself isn't enough; we need metrics and associated outcomes. I believe the following metrics (and related monitoring / observability) are critical components of a successful data product:
  1. A way of measuring usage, ideally differentiating automation from ad-hoc
  2. A way of measuring satisfaction, ideally at the feature level
  3. A way of measuring data quality, all key aspects


These components are far from sufficient, but I believe they are necessary for data teams to adequately judge whether or not their work is having an impact. Yes, dollar or FTE-equivalent attribution is the gold standard, but in cases where that's not available, knowing that we're delivering high-quality data to engaged, satisfied users is a good proxy. These metrics also allow us to capture those unintended benefits of a data product; perhaps our users are applying the outputs to different processes altogether.
One salient point that Niral raised in a follow-up conversation is that data products should be actionable; an automation or dashboard should drive some action that generates value. It's critical to make the distinction between creating data products with the primary goal of psychosocial impact and considering psychosocial impact as a dimension of value. I wouldn't suggest that, in the planning phase, we make a product with the sole goal of improving morale or team cohesion, as that value proposition is tenuous at best. Rather, if our product fails to drive its intended action but is still wildly popular, we should have the framework in place to investigate why. Essentially, we don't want to throw away something valuable just because it's not "working as intended."
* * *
To wrap up with a brilliant insight from one attendee: data teams contribute to the workplace well-being of our stakeholders; if providing a data pull or a dashboard makes users happy, there's utility in that. It certainly can't be the data team's only value proposition, but it's also not something we should discount. While it may be tempting to lean into objectivity and dismiss the human elements of our work ("weaknesses" that data can "overcome"), the reality is that we're social creatures working in complex organizations. We have tools for cutting through subjectivity, but most of our work will pass through another person's hands; there's more value in acknowledging and recognizing that human element than there is in turning away from it.
* * *
Literally minutes after I finished my first draft of this article, [Benn Stancil](https://towardsdatascience.com/missing-features-in-the-data-product-movement-613f4b5718b7/None) released a smart piece on [his discomfort with giving up on the objectivity of data](https://benn.substack.com/p/the-case-for-being-biased). I would be remiss if I didn't send you in his direction.
## 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-9e4c3e3de7a22688d8ce.jpeg)
Written By
## [Chad Isenberg](https://towardsdatascience.com/author/cisenbe/)
[See all from Chad Isenberg](https://towardsdatascience.com/author/cisenbe/)
[Analytics](https://towardsdatascience.com/tag/analytics/)[Business](https://towardsdatascience.com/tag/business/)[Data Product Creation](https://towardsdatascience.com/tag/data-product-creation/)[Data Science](https://towardsdatascience.com/tag/data-science/)[Notes From Industry](https://towardsdatascience.com/tag/notes-from-industry/)
Share This Article
  * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fmissing-features-in-the-data-product-movement-613f4b5718b7%2F&title=Missing%20features%20in%20the%20data%20product%20movement)
  * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fmissing-features-in-the-data-product-movement-613f4b5718b7%2F&title=Missing%20features%20in%20the%20data%20product%20movement)
  * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fmissing-features-in-the-data-product-movement-613f4b5718b7%2F&text=Missing%20features%20in%20the%20data%20product%20movement)


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/002.jpg)](https://towardsdatascience.com/how-to-successfully-run-a-b-tests-f3ca363dec98/)
## [How to Successfully Run A/B Tests](https://towardsdatascience.com/how-to-successfully-run-a-b-tests-f3ca363dec98/)
[Data Science](https://towardsdatascience.com/category/data-science/)
Best practices from large tech companies that are aggressively experimenting with everything
[Kevin Babitz](https://towardsdatascience.com/author/kevindbabitz/)
February 25, 202110 min read
  * [![](../images/003.jpg)](https://towardsdatascience.com/getting-ai-ready-preparing-for-a-world-of-agentic-ai-as-tech-professionals/)
## [Get AI-Ready: How to Prepare for a World of Agentic AI as Tech Professionals](https://towardsdatascience.com/getting-ai-ready-preparing-for-a-world-of-agentic-ai-as-tech-professionals/)
[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)
Explore how Agentic AI is reshaping the tech careers, from data to decision-making, and how professionals can prepare for the future of work
[Rashi Desai](https://towardsdatascience.com/author/rashidesai/)
August 27, 20256 min read
  * [![](../images/004.jpeg)](https://towardsdatascience.com/under-the-hood-of-gradient-boosting-and-its-python-implementation-99cc63efd24d/)
## [Under the Hood of Gradient Boosting and Its Python Implementation](https://towardsdatascience.com/under-the-hood-of-gradient-boosting-and-its-python-implementation-99cc63efd24d/)
[Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/)
Boosting algorithms in machine learning - Part 3
[Rukshan Pramoditha](https://towardsdatascience.com/author/rukshanpramoditha/)
October 24, 20215 min read
  * [![](../images/005.jpg)](https://towardsdatascience.com/python-logging-saving-logs-to-a-file-sending-logs-to-an-api-75ec5964943f/)
## [Python logging - saving logs to a file & sending logs to an API](https://towardsdatascience.com/python-logging-saving-logs-to-a-file-sending-logs-to-an-api-75ec5964943f/)
[Programming](https://towardsdatascience.com/category/programming/)
Get your logs to where they are needed to debug your code
[Mike Huls](https://towardsdatascience.com/author/mikehuls/)
June 9, 20225 min read
  * [![](../images/006.jpeg)](https://towardsdatascience.com/math-vs-coding-data-science-43e216b4f671/)
## [How to Get into Data Science - Math Or Coding](https://towardsdatascience.com/math-vs-coding-data-science-43e216b4f671/)
[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)
For people who are still deciding whether Math or Coding is more important
[Low Wei Hong](https://towardsdatascience.com/author/lowweihong/)
October 20, 20195 min read
  * [![](../images/007.jpg)](https://towardsdatascience.com/create-a-sms-spam-classifier-in-python-b4b015f7404b/)
## [Create a SMS spam classifier in python](https://towardsdatascience.com/create-a-sms-spam-classifier-in-python-b4b015f7404b/)
[NLP](https://towardsdatascience.com/category/artificial-intelligence/nlp/)
Natural Language Processing basics using scikit-learn
[Chia Dehan](https://towardsdatascience.com/author/thedehan/)
August 16, 20206 min read
  * [![](../images/008.png)](https://towardsdatascience.com/batch-norm-explained-visually-why-does-it-work-90b98bcc58a0/)
## [Batch Norm Explained Visually - Why does it work](https://towardsdatascience.com/batch-norm-explained-visually-why-does-it-work-90b98bcc58a0/)
[Deep Learning](https://towardsdatascience.com/category/artificial-intelligence/deep-learning/)
A Gentle Guide to the reasons for the Batch Norm layer's success in making training converge faster, in Plain English
[Ketan Doshi](https://towardsdatascience.com/author/ketanhdoshi/)
May 26, 20218 min read
  * [![](../images/009.jpeg)](https://towardsdatascience.com/10-must-know-topics-of-python-for-data-science-9ce36a5b9681/)
## [10 Must-Know Python Topics for Data Science](https://towardsdatascience.com/10-must-know-topics-of-python-for-data-science-9ce36a5b9681/)
[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)
What Pandas or Matplotlib does not teach you
[Soner Yıldırım](https://towardsdatascience.com/author/sonery/)
February 13, 20217 min read
  * [![](../images/010.jpg)](https://towardsdatascience.com/how-to-write-code-effectively-in-python-105dc5f2d293/)
## [How To Write Code Effectively In Python](https://towardsdatascience.com/how-to-write-code-effectively-in-python-105dc5f2d293/)
[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)
Analyzing the best practices that you should follow while writing code in Python
[Bharath K](https://towardsdatascience.com/author/bharath-k1297/)
September 7, 202110 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?")


