Unsolved Problems in MLOps
gnyeki
47 points
4 comments
July 15, 2026
Related Discussions
Found 5 related stories in 181.2ms across 9,716 title embeddings via pgvector HNSW
- Show HN: We Beat MLPerf: Modern Storage for KV Offload and LLM Training arnav__1 · 35 pts · September 05, 2026 · 50% similar
- Mesh LLM: distributed AI computing on iroh tionis · 176 pts · July 11, 2026 · 48% similar
- I Find Problems to Solve as a Staff Engineer birdculture · 14 pts · July 26, 2026 · 47% similar
- open-slopware – Alternatives to FOSS projects choosing to use LLMs/AI smartmic · 28 pts · October 09, 2026 · 46% similar
- Learning to solve hard problems in RL for LLMs by never giving up natolambert · 73 pts · September 15, 2026 · 46% similar
Discussion Highlights (3 comments)
juancn
TLDR AI Summary of the thing: https://gist.github.com/juancn/9bc654ccffbba113271a068a2d854... (I found the flourished language of the original a bit too much for my taste)
occupant
Non-pdf link: https://queue.acm.org/detail.cfm?id=3762989
ks2048
Summary (at end of PDF): As discussed at the beginning of this article, the excitement with AI is carrying us along in a big wave, but the practitioners whose job it is to make this all work are scrambling behind the scenes, often more in dread than excitement. In some cases, they are using outdated techniques; in others, approaches that only work for now; and every so often they are doing nothing at all in order to meet significant operational, technical, and business challenges. In MLOps terms, it sometimes feels that we are using older paradigms to manage a thoroughly new situation, and it’s not entirely clear that we really see it like this. We should be casting about for either a better paradigm or a better patching-up of the existing paradigms than is available today. Regardless, we hope that the summary of the problems presented here is a useful stimulant to people attempting to think about them more holistically and, hopefully, helps to provide some answers.