Sber and Yandex Practicum expert explains where AI helps data science
A Sber and Yandex Practicum expert has described how AI is actually used in a data scientist's work: it speeds up routine tasks and helps with code, hypotheses and presenting results. But the model cannot be fully trusted. It can misread data, invent facts and has no feel for business context. The takeaway is simple: AI is useful as an assistant, not as a replacement for a specialist.
AI-processed from Habr AI; edited by Hamidun News
Vyacheslav Demin, an expert at Sber and Yandex Practicum, has published a piece on how artificial intelligence has already become part of a data scientist's daily work. His main point is simple: AI is good at speeding up routine and draft work, but it cannot yet replace a specialist where the cost of an error is high.
Where AI helps
The author's background matters in itself: he entered the profession through training at Yandex Practicum, then worked in insurance and petrochemicals, and now heads data analytics at Sber. That background keeps his conclusions grounded. This is not about polished demos, but about how models behave on real tasks, with deadlines, business constraints, heterogeneous data and the need to answer for results to the team.
In this context, AI is useful first of all as a way to get started faster. It helps build the skeleton of a solution more quickly, sketch the structure of a notebook, check syntax, work through documentation, prepare a draft text for a report or compare several approaches. If a specialist already understands the task and can verify the answer, the time savings are noticeable. But the value comes not from any magic in the model; it comes from the model taking over the mechanical part of the work.
Which tasks get faster
The piece stresses that AI is particularly strong at routine and supporting actions around analytics and machine learning that do not form the core of a solution. This is an important boundary: a model can do a decent job around data science, but it cannot take responsibility for the final conclusion. That is why the gain is most often visible in preparation speed, not in removing the human from the process entirely.
- Draft Python and SQL code for standard operations
- Quick explanations of errors, stack traces and documentation
- A first version of EDA, hypotheses and features
- Descriptions of experiments, reports and presentation takeaways
- Less time spent searching for wording and on boilerplate actions
This scenario fits well with real team processes. A specialist spends less time on repetitive operations and more on what really affects the quality of the result: framing the task, choosing metrics, testing hypotheses and discussing the effect on the product or business. Here AI acts as a working add-on that removes friction from daily routine, but it does not replace engineering thinking, statistical rigor or understanding of the subject area.
Where the limits begin
The main limitation the author insists on is that artificial intelligence still cannot be left unsupervised. A model can generate a plausible, neatly formatted answer and still get the logic wrong, mix up assumptions, explain a metric incorrectly or suggest code that looks reasonable but breaks on real data. In data science this is especially dangerous: an error often shows up not immediately, but after an experiment, a release or a management decision.
"You still should not rely on it 100%."
The limits are most visible where domain expertise and accountability for the conclusion are required. AI does not know a company's context the way a person does: it does not understand hidden constraints in the data, does not see the cost of false positive and false negative decisions in a specific product, and is not answerable to the business for the outcome. So it can be trusted with a draft, but not, without checking, with the choice of target variable, the interpretation of correlations, the assessment of model quality or the final recommendations.
Another trap is confusing speed of response with quality of analysis. If a model produced code, a table or a chart interpretation in a minute, that does not remove the need to manually check samples, features, data leakage and the meaning of the dependencies found. In applied analytics an error is rarely abstract: it can lead to a wrong product priority, a bad credit scoring decision, a demand forecast that does not work, or a false sense that the model is ready for deployment.
What this means
Vyacheslav Demin's piece captures a mature view of AI's role in data science. It is no longer an experimental toy or a universal autopilot, but a useful layer on top of a specialist's everyday work. The teams that gain most will be those that build AI into the process as a controlled tool: they will use it to speed up routine, but keep problem framing, validation of results and responsibility for final conclusions in production with a human.
- Oct 28, 2026Anthropic reveals how it builds Claude with Claude: the brain separate from the hands
- Oct 28, 2026Bayer Launches Multi-Agent Engine on AgentCore: 80% of Questions Handled Without Engineers
- Oct 28, 2026Liquid AI releases LFM2.5-24B-A2B: an agent model with 2B active parameters
- Oct 28, 2026AgentOrch: Pre-Planned AI Agents Now Trail Step-by-Step Execution by Just 8.5 Points
Key Questions Answered
Where AI helps?
The author's background matters in itself: he entered the profession through training at Yandex Practicum, then worked in insurance and petrochemicals, and now heads data analytics at Sber. That background keeps his conclusions grounded. This is not about polished demos, but about how models behave on real tasks, with deadlines, business constraints, heterogeneous data and the need to answer for results to the team. In this context, AI is useful first of all as a way to get started faster. It helps build the skeleton of a solution more quickly, sketch the structure of a not
Which tasks get faster?
The piece stresses that AI is particularly strong at routine and supporting actions around analytics and machine learning that do not form the core of a solution. This is an important boundary: a model can do a decent job around data science, but it cannot take responsibility for the final conclusion. That is why the gain is most often visible in preparation speed, not in removing the human from the process entirely. Draft Python and SQL code for standard operations Quick explanations of errors, stack traces and documentation A first version of EDA, hypotheses and features
Where the limits begin?
The main limitation the author insists on is that artificial intelligence still cannot be left unsupervised. A model can generate a plausible, neatly formatted answer and still get the logic wrong, mix up assumptions, explain a metric incorrectly or suggest code that looks reasonable but breaks on real data. In data science this is especially dangerous: an error often shows up not immediately, but after an experiment, a release or a management decision. "You still should not rely on it 100%." The limits are most visible where domain expertise and accountability for the conc
Test Frontier LLMs & Autonomous Agents in One Workspace
Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.