从数据科学家到AI架构师

Towards Data Science

Towards Data Science2026年5月8日

从数据科学家到AI架构师

3.5Score

TL;DR · AI 摘要

文章介绍网站使用的各种Cookie，但缺乏技术深度和实用价值。

核心要点

文章列出多个Cookie名称及用途，但描述不完整
部分Cookie用于广告追踪和用户行为分析
未提供技术架构或工程实践建议

结构提纲

按章节快速跳转。

§引言
文章介绍网站使用Cookie来优化用户体验和广告投放。
·Cookie分类
文章将Cookie分为必要性和非必要性两类。
›必要性Cookie
必要性Cookie用于基本功能如登录和会话管理。
›非必要性Cookie
非必要性Cookie用于个性化广告和内容推荐。

思维导图

用一张图看清主题之间的关系。

查看大纲文本（无障碍 / 无 JS 友好）

网站Cookie使用
- Cookie分类
  - 必要性Cookie
  - 非必要性Cookie
- Cookie用途
  - 基本功能
  - 广告追踪
  - 用户行为分析
- Cookie示例
  - BCTempID
  - li_gc
  - PHPSESSID

金句 / Highlights

值得收藏与分享的关键句。

必要性Cookie用于基本功能如登录和会话管理，不存储个人数据。
— 第 2 段
⬇︎ 下载 PNG 𝕏 分享到 X
部分Cookie用于广告追踪和用户行为分析，如LinkedIn的li_gc Cookie。
— 第 3 段
⬇︎ 下载 PNG 𝕏 分享到 X
文章未提供技术架构或工程实践建议，实用性较低。
— 结论
⬇︎ 下载 PNG 𝕏 分享到 X

#Web Development#Privacy

打开原文

From Data Scientist to AI Architect | Towards Data Science

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

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

Necessary Always 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

[x]

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

[x]

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

[x]

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.

[x]

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

Skip to content

Publish AI, ML & data-science insights to a global community of data professionals.

Sign in

Submit an Article

* *

Write For TDS

Toggle Mobile Navigation

Toggle Search

Search

Career Advice

From Data Scientist to AI Architect

The end of model-centric thinking in data science

Sara A. Metwalli

May 8, 2026

6 min read

Share

Image by Google DeepMind from Pexels

There was a time _(not that long ago)_ when being a data scientist meant living in a notebook, tweaking hyperparameters as if your life depended on it, and in a lot of cases, the whole project did, indeed, depend on it.

Do you remember those overnight grid searches? Or building feature engineering pipelines that felt more like art than science? And the satisfaction of squeezing out an extra 0.7% accuracy from an XGBoost model?

Back in 2019, that was the job of a data scientist! Which made sense. If you wanted a strong model, you had to build it yourself or work hard to get it right. The real value came from how well you could tune, optimize, and understand the data.

Now, ‘state-of-the-art’ is just an API call away. Need a top language model? Done. Need embeddings or multimodal reasoning? Also done. The hardest parts of modeling are now handled by scalable endpoints, far beyond what most teams could build themselves.

The question now is, if the model is already there, _where did the work go?_

The value isn’t just in the model anymore. It’s in how all the parts connect, communicate, and adapt. That change is reshaping the role of a data scientist entirely.

_How_, you ask? This is what this article is all about.

What changed?

Image by the author

1. Bypassing the .fit() Method

If you look at the code in a modern AI project, you’ll quickly notice there isn’t much actual modeling going on.

You might see a call to an LLM or an embedding model, but that’s rarely the main challenge. The real work is in data ingestion, routing, assembling context, caching, monitoring, and handling retries.

In other words, using .fit() is now one of the least interesting parts of the code.

2. Adapting to the New Components

Today, instead of focusing on model internals, we assemble systems from ready-made components. A typical modeling stack now includes:

Vector databases (e.g., Pinecone, Milvus)
Prompt engineering.
Memory layers.

In addition to functions/ agent calls. When we look at the big picture, we see that this isn’t traditional modeling. It’s system design. An important thing to point out here is that none of these components is particularly useful on its own. Their power comes from how they’re orchestrated together.

3. Putting everything together

Right now, most data science code is about connecting the pieces. It’s not about linear algebra, optimization, or even statistics.

It’s about writing code that moves data between components, formats inputs, parses outputs, logs interactions, and manages state across distributed systems.

If you measure your code, you’ll see that only 10 to 20 percent is spent using a model (API calls, inference), while 80 to 90 percent is spent on orchestration—handling data flow, integration, and infrastructure.

The shift from Data Scientist to AI Architect

The biggest change in mindset today is that you’re no longer just optimizing a function. Now, you’re designing a whole system, thinking about latency, cost, reliability, and how people interact with it.

Instead of asking, “_How do I improve model performance?_” we now ask, _“How does this whole system work in real-world situations?_”

I know what you’re thinking—this is a completely different challenge! It was uncomfortable for many people, including me, when this shift first happened.

To keep up with today’s stack, we need more than just statistics and machine learning. We have to be comfortable with APIs (such as FastAPI or Flask) for serving and routing, containerization (such as Docker) for deployment, async programming (using Asyncio) for handling multiple requests, cloud infrastructure for scaling and monitoring, and data engineering basics for pipelines and storage.

If you’re thinking this sounds a lot like _backend engineering_, you’re right.

This shift has blurred the line between data scientist and engineer. The people who do well are those who can work comfortably in both areas.

The old vs. The new

The key question now is: what does this shift look like in code?

Legacy Project (2019): Sentiment Analysis

Many of us have worked on projects like this. The process is simple:

Collect a labeled dataset.
Perform feature engineering (TF-IDF, n-grams).
Train classifier (logistic regression, XGBoost).
Tune hyperparameters.
Deploy model.

Success here depends on the quality of your dataset and your model.

Modern Project (2026): Autonomous Customer Feedback Agent

The process is different now. To build a system today, you need to:

Ingest customer messages in real time.
Store embeddings in a vector database.
Retrieve relevant historical context.
Dynamically construct prompts.
Route to LLM with tool access (e.g., CRM updates, ticketing systems)
Maintain conversational memory.
Monitor outputs for quality and safety.

Can you spot what’s missing? _Here’s a hint:_ there’s no training loop.

This example is simple on purpose, but notice what we focus on now. Retrieval is part of the system; the model is just one piece, and the value comes from how everything connects and works together.

How to Start Thinking Like an AI Architect

Now that we know what’s changed, let’s talk about what you should actually do differently. How can you move forward with this shift instead of falling behind?

_The short answer:_ start building systems, not just models.

_The longer answer:_ focus on building these skills:

1. Build End-to-End, Not Just Components

Instead of thinking, “_I trained a model_,” aim for, “_I built a system that takes input, processes it, and returns a value._” It is now about the big picture, not just one task.

2. Learn Just Enough Backend to Be Dangerous

You don’t need to become a full-time backend engineer, but you should know enough to build your system. Focus on:

Spinning up a simple API (FastAPI is enough)
Handling requests asynchronously
Logging and error handling
Basic deployment (Docker + one cloud platform)

3. Get Comfortable With Ambiguity

Modern AI systems aren’t deterministic like traditional models. This makes them harder to work with, because now you’re not just debugging code; rather, you’re debugging behavior.

That means, iterating on prompts, designing fallback mechanisms, and evaluating outputs qualitatively, not just quantitatively.

4. Measure What Actually Matters

Accuracy isn’t always the main metric anymore. Now, latency, cost per request, user satisfaction, and task completion rate matter more.

A system that’s 95% accurate but unusable in production is worse than one that’s 85% accurate and reliable.

Image by the author

The Final Thought

In our field, there’s always a temptation to chase whatever feels most “technical”, the newest model, the biggest benchmark, the flashiest architecture.

But the most valuable part of this job has always been, and will always be, the human side! Which is understanding the problem. Knowing what we’re trying to solve matters more than the data or the model we use.

Asking questions like, “_What is the need here? What does the user care about? What does ‘good’ actually mean in context?_” makes a huge difference in what you build.

You can’t outsource or hide that part behind an API. And you definitely can’t automate it away.

So don’t just aim to build a car’s engine. Aim to be the person who understands where the car should go, and then builds the system to get it there.