Cercles
Machine Learning
Discussion
MLOps for a team of three: minimum viable pipeline that doesn't become a second job
You can't hire a dedicated ML engineer. What tooling and practices covered 80% of the reliability needs without requiring a specialist to maintain them?
5 replies
We made this call differently and I'm genuinely unsure who was right. Team size and ownership clarity tip it for me.
The hard part is governance: speed without guardrails becomes compounding debt within a quarter.
Worth being explicit about assumptions before starting — we wasted two weeks discovering constraints that were knowable upfront.
The failure mode I keep seeing: solving the symptoms quickly and never addressing the root.
Defining 'good enough' before starting rather than after the work is done made a real difference for us.
Join the conversation.
Log in to reply