Het deel na de lancering is het deel waarvoor u betaalt
Evaluatie, monitoring, en de fouten die pas opduiken zodra er echte gebruikers zijn.
Concept. Dit artikel hoort bij de artikelensectie als opmaakskelet, en is uitgesloten van zoekmachines en van de site-assistent tot er een echt stuk in staat.
Dit artikel verschijnt in het Engels. De rest van de site is vertaald, de artikelen niet, omdat een machinaal vertaald technisch betoog minder waard is dan hetzelfde betoog gelezen in de taal waarin het geschreven is.
An AI feature is not finished when it is deployed. That sentence is easy to agree with and almost nobody budgets for it, which is why so many pipelines that were accurate in month one are quietly wrong by month four.
Three things that change without anyone touching the code
- The provider updates the model behind the version string you pinned, or deprecates it entirely.
- An upstream API adds a field, reorders a list, or starts returning
nullwhere it used to return an empty array. - Your own data changes shape, because the business changed and nobody thought to mention it to the pipeline.
What a maintenance loop contains
An evaluation set that reflects real traffic rather than the examples used during the build. A scheduled run of it. An alert when a score moves, and a human who reads that alert. None of this is sophisticated; the reason it is rare is that it produces no demo.
This post is a placeholder shipped with the writing section. Replace the body with the real piece; the frontmatter above is the only thing the site reads.