1 min readfrom Machine Learning

Are there some textbooks that take a primarily engineering approach to machine learning (as opposed to a "scientific" approach)? [D]

Our take

Many find the transition from theoretical machine learning to practical software implementation challenging, especially when navigating complex organizational structures. While many textbooks prioritize a scientific, statistical foundation, fewer focus on the engineering principles needed to build robust, production-ready ML components. If you're seeking a more pragmatic approach—one that emphasizes efficient software development and integration—consider exploring resources that prioritize engineering workflows. As discussed in "Platform Engineering for Everyone," successful ML implementation requires more than just technology; it demands a well-defined platform.

The frustration voiced by /u/ConstructionBoth6461 resonates deeply with many who’ve navigated the complexities of operationalizing machine learning models within businesses. Their lament about the sprawling, often inefficient, ML model lifecycle – the layers of middle management overseeing feature extraction, data pipelines, and infrastructure – highlights a critical disconnect between the theoretical promise of AI and its practical application. It's a challenge exacerbated by the current business climate, demanding rapid iteration and demonstrable ROI, making the traditionally academic approach to ML feel increasingly burdensome. The core issue isn't a lack of mathematical understanding, as evidenced by the author’s strong statistical and operations research background, but rather a deficiency in engineering-focused methodologies for building *software* *with* AI components. This echoes the points made in [Presentation: Platform Engineering for Everyone - Success Can’t Be Coded], which emphasizes that successful internal development platforms require more than just technology; they necessitate a holistic approach to process and people. Similarly, the discussion around Strands Agents, as explored in [Podcast: Strands Agents with Clare Liguori], touches upon the need for streamlined workflows and efficient tooling to bridge the gap between model development and deployment.

The absence of a distinctly engineering-driven approach to ML education is a significant contributing factor to this problem. While many curricula prioritize algorithmic nuances and statistical rigor – the “scientific” approach – they often neglect the practical considerations of building robust, scalable, and maintainable ML-powered software. A textbook that framed machine learning through an industrial engineering lens, emphasizing optimization, reliability, and system-level design, would be a valuable addition to the landscape. Think of it as applying principles of manufacturing and process control to the development and deployment of ML models. This might include a greater focus on modularity, version control (beyond just model weights), automated testing, and infrastructure-as-code for the entire ML pipeline. The current environment, where organizations are scrambling to leverage AI, demands practitioners who can not only build models but also architect and operate them effectively within a software engineering context. The challenges outlined by /u/ConstructionBoth6461 are amplified when considering the sheer volume of data and the increasing complexity of modern ML systems, as highlighted by Current AI’s efforts to create a decentralized, accessible AI landscape [Nonprofit Current AI is racing to build the World Wide Web of AI, free for all].

The problem isn't simply about technical skill; it’s about organizational structure and process. The 'mountains of middle management' described by the author point to a lack of clear ownership and accountability within the ML lifecycle. Siloed teams, each responsible for a specific component, lead to communication bottlenecks and inefficiencies. An engineering-focused approach would necessitate cross-functional collaboration and a more streamlined workflow, potentially leveraging platform engineering principles to abstract away the underlying complexity. This shift would require a cultural change, moving away from a model-centric view of ML to a system-centric view, where the model is just one component within a larger, integrated software system. Furthermore, a focus on observability and monitoring – often overlooked in the rush to deploy models – becomes paramount when building production-ready ML applications.

Ultimately, the call for a more engineering-focused approach to machine learning education and implementation is a call for pragmatism. It’s about recognizing that building useful software with ML components requires a different skillset and mindset than simply developing and evaluating algorithms. The future of AI in business hinges not just on the sophistication of our models, but on our ability to effectively integrate them into the software we build and operate. Will we see a surge in textbooks and educational resources that bridge this gap, or will organizations continue to struggle with the operationalization of their ML investments, leading to disillusionment and a return to simpler, albeit less powerful, solutions?

As someone who studied stats undergrad and industrial engineering operations research grad, and who thinks about the practical business of ML components in software....

I get lost and a bit hopeless when I think about how to make useful software out of ML models in a reasonable amount of time, and in the current business environment.

And when I look at the businesses where I have worked that have mountains of middle management running tiny bits of the ML model lifecycle (think feature extraction, data ingestion and integration, training infra, hosting infra, more hosting infra, applied science)... that only makes my head hurt even more.

How do you go about making practical software out of ML components?

Edit: I should mention that I mean from scratch ML components, not just a call to a third party hosted tool.

submitted by /u/ConstructionBoth6461
[link] [comments]

Read on the original site

Open the publisher's page for the full experience

View original article