Automating the end-to-end lifecycle of Machine Learning applications
Machine Learning applications are becoming popular in our industry, however the process for developing, deploying, and continuously improving them is more complex compared to more traditional software, such as a web service or a mobile application. They are subject to change in three axis: the code itself, the model, and the data. Their behaviour is often complex and hard to predict, and they are harder to test, harder to explain, and harder to improve. Continuous Delivery for Machine Learning (CD4ML) is the discipline of bringing Continuous Delivery principles and practices to Machine Learning applications. Read More
Tag Archives: DevOps
Real Time Machine Learning at Scale using SpaCy, Kafka & Seldon Core
Andrew Ng: Bridging AI’s Proof-of-Concept to Production Gap
AI In Code Series: Finastra – Code assistance for the developer toolkit
We users use Artificial Intelligence (AI) almost every day, often without even realising it i.e. a large amount of the apps and online services we all connect with have a degree of Machine Learning (ML) and AI in them in order to provide predictive intelligence, autonomous internal controls and smart data analytics designed to make the end user User Interface (UI) experience a more fluid and intuitive experience.
That’s great. We’re glad the users are happy and getting some AI-goodness. But what about the developers?
But what has AI ever done for the programming toolsets and coding environments that developers use every day? How can we expect developers to develop AI-enriched applications if they don’t have the AI advantage at hand at the command line, inside their Integrated Development Environments (IDEs) and across the Software Development Kits (SDKs) that they use on a daily basis? Read More: Part 1 … Part 2
Model Lifecycle: From ideas to value
Value scoping, discovery, delivery, and stewardship
In Part 1 of this series we examined the key differences between software and models; in Part 2 we explored the twelve traps of conflating models with software; and in Part 3 we looked at the evolution of models. In this article, we go through the model lifecycle, from the initial conception of the idea to build models to finally delivering the value from these models. Read More
10 MLops platforms to manage the machine learning lifecycle
Machine learning lifecycle management systems rank and track your experiments over time, and sometimes integrate with deployment and monitoring
For most professional software developers, using application lifecycle management (ALM) is a given. Data scientists, many of whom do not have a software development background, often have not used lifecycle management for their machine learning models. That’s a problem that’s much easier to fix now than it was a few years ago, thanks to the advent of “MLops” environments and frameworks that support machine learning lifecycle management. Read More
Consequences of mistaking models for software
Twelve traps to avoid when building and deploying models
In Part 1 of this series on data scientists are from Mars and software engineers are from Venus we examined the five key dimensions of difference between software and models. The natural follow on question to ask is — So What? Does it really matter if models are conflated with software and data scientists are treated as software engineers? After all for a large cross-section of the population, and more importantly the business world, the similarities between them are far more visible than their differences. In fact, Andrej Karpathy refers to this new way of solving problems using models as Software 2.0. If they are really the next iteration of software are these differences really consequential. Read More
Data Scientists are from Mars and Software Developers are from Venus (Part 1)
Mars and Venus are very different planets. Mars’s atmosphere is very thin and it can get very cold; while Venus’s atmosphere is very thick and it can get very hot — hot enough to melt lead!.
…Software Engineers and Data Scientists come from two different worlds — one from Venus and the other from Mars. They have different backgrounds mindsets, and deal with different sets of issues. They have a number of things in common too. In this and subsequent blogs we will look at the key differences (and similarities) between them and why those differences exist and what kind of bridge we need to create between them. In this blog, we explore the fundamental differences between software and models. Read More
Responsible AI Can Effectively Deploy Human-Centered Machine Learning Models
Artificial intelligence (AI) is developing quickly as an unbelievably amazing innovation with apparently limitless application. It has shown its capacity to automate routine tasks, for example, our everyday drive, while likewise augmenting human capacity with new insight. Consolidating human imagination and creativity with the adaptability of machine learning is propelling our insight base and comprehension at a remarkable pace.
However, with extraordinary power comes great responsibility. In particular, AI raises worries on numerous fronts because of its possibly disruptive effect. These apprehensions incorporate workforce uprooting, loss of protection, potential biases in decision-making and lack of control over automated systems and robots. While these issues are noteworthy, they are likewise addressable with the correct planning, oversight, and governance. Read More
Low-code platforms and the democratization of AI
Tech giants like IBM and Amazon are developing products that will make it easier for people without a coding background to build apps that integrate with AI services.
Key Takeaway: Low-code and no-code platforms are seeing new life, as access to artificial intelligence and fast deployment of applications becomes increasingly critical with the popularity of Cloud-based software development. These products enable those without a coding background to more easily access the benefits of AI. Read More
Rick's Cafe AI 