#061 ML Александр Алерон Миленькин. Надо ли строить бизнес вокруг ML

#061 ML Александр Алерон Миленькин. Надо ли строить бизнес вокруг ML

#061 ML Александр Алерон Миленькин. Is it necessary to build a business around ML?

🎙 Mikhail Kryzhanovskiy (Machine Learning Podcast) 👥 5K 📅 January 25, 2025 ⏱ 55 min 👁 444 📄 expert opinion 🧭 2026-10-09
Available in: English (current) Français

Keywords

RAGLLMagentsrecommender systemsML strategy

Summary

This episode of the Machine Learning Podcast features Alexander ‘Aleron’ Milenkin, ML lead at Dodo Brands, IT entrepreneur, Kaggle expert and instructor. He explains his path from wet-lab biology to bioinformatics and then to data science, and describes how his team covers most ML needs at Dodo Brands, with recommender systems generating the largest business value, followed by NLP and computer vision. The central thesis is that ML is a tool to boost an existing business, not a business in itself: startups that build a company around an ML solution rarely succeed, whereas established businesses with data can extract additional value. The conversation then turns to the economics of large models: not every company needs to train its own LLM, and external APIs can be cheap and effective if the use case converts into revenue with good margin. The guest outlines three growth paths for LLM-based products: building a RAG system over interchangeable models, fine-tuning with LoRA-style methods on proprietary data, or full continued pre-training. A detailed walkthrough of a RAG pipeline follows, including document loaders, chunking, embeddings, vector stores, retrievers and prompt construction, illustrated by Dodo’s voice-ordering use case combining speech-to-text, semantic search and few-shot prompting. The discussion then moves to agents that can browse the web or documentation, and to the risks of giving them write access. The episode closes with a reflection on why stuffing an entire knowledge base into a prompt is not a substitute for RAG.

241 words

Critical Evaluation

Value of the Information & Strength of the Argument

The informational value is high for practitioners and decision-makers: the guest provides a coherent mental model of where ML creates value in a company, ranked by business impact (recommenders first, NLP second, computer vision third), and explains why this ranking follows from the share of orders placed through the app. The argument that ML should be built around an existing business rather than the reverse is well supported by the observation that small companies often lack the data volume to justify bespoke models and should instead rely on analytics or ready-made services. The three-path framework for LLM products (RAG, LoRA fine-tuning, full pre-training) is a useful decision aid, and the preference for RAG is justified by the speed at which knowledge changes versus the cost of retraining. The voice-ordering case study is particularly valuable because it shows a complete pipeline from speech-to-text through semantic search and few-shot prompting to a final API response, including the practical trick of letting the model output Python dicts for downstream parsing. The argumentation is mostly experiential rather than evidence-based: claims such as ‘almost no hallucinations in this simple domain’ or ‘computer vision is not rocket science for production’ are asserted rather than demonstrated with metrics. The agent discussion is vivid and grounded in a concrete MongoDB agent example, but the leap to ‘Terminator’ scenarios is rhetorical rather than analytical. Overall, the reasoning is clear, structured and practically useful, but it relies on the guest’s authority and experience rather than on comparative data or published benchmarks.

Scientific Rigor, Source Quality, Title Accuracy

Scientific rigor is moderate. The episode is a practitioner conversation, not a research presentation: no papers, benchmarks or datasets are cited, and quantitative claims (e.g. 90% of orders via the app, API cost-effectiveness) are given without supporting figures. The technical descriptions of RAG components (loaders, embeddings, vector stores, retrievers, cosine similarity) are accurate and consistent with standard industry practice, and the mention of LoRA-family methods for parameter-efficient fine-tuning is correct. The distinction between RAG, fine-tuning and continued pre-training is presented clearly and without overstatement. Source quality is limited to the guest’s own production experience and to tools he names (LangChain, Hugging Face, MongoDB agent, GPT APIs), which are real and verifiable but not used as evidence in a formal sense. The title’s question is answered directly and consistently with the content, so the title/content fit is good; the episode does not overpromise relative to what it delivers. No advertising sequence was detected in the transcript. No comments were provided for analysis.

427 words

Title / Content Match

The title asks whether one should build a business around ML, and the episode does address this question directly, arguing that ML should serve an existing business rather than be the business itself. The title is therefore faithful to the content, though the episode covers a broader range of topics (RAG, agents, LLM economics).

Quality & Reliability

7/10

The content is an expert interview with a practicing ML lead at Dodo Brands, Kaggle expert and instructor. Claims are grounded in concrete production experience (recommender systems, voice ordering, RAG pipelines) and are internally consistent. However, no external studies, benchmarks or peer-reviewed references are cited; the discussion remains at the level of practitioner opinion and architectural description. No factual errors were detected, but verifiability is limited to the guest's own experience.

Key Moments

Cited Sources

Concurring Sources

External References

Contribution & Novelties

The episode’s original contribution is its pragmatic framing of ML as a business tool rather than a standalone venture, combined with a clear three-path taxonomy for LLM-based products (RAG, LoRA fine-tuning, continued pre-training) and a concrete production case study of voice ordering at Dodo Brands. It also offers a useful distinction between agents that read the web and agents that could write to it, highlighting the governance risk of granting write access. The discussion of when external APIs are sufficient versus when proprietary data justifies fine-tuning is a practical decision framework rarely spelled out so explicitly in popular ML content.

Pour aller plus loin :

  • Retrieval-augmented generation — Overview of the RAG paradigm and its components.
  • LoRA (Low-Rank Adaptation) — Parameter-efficient fine-tuning method referenced in the episode.
  • LangChain — Framework for building RAG pipelines and agents, mentioned by the guest.
  • Hugging Face — Model hub and inference service discussed as an alternative to in-house models.
  • Vector database — Concept underlying the semantic search component of RAG systems.

167 words

Radar Profile

The profile is balanced toward practical information and reliability, with a moderate technical level reflecting the conversational format. Quantity and quality of information are strong for a podcast episode, while technical depth is limited by the absence of formal benchmarks or code-level detail. Overall, the radar suggests a solid practitioner-oriented episode rather than a research-grade presentation.

Reliability 7/10