| I am an ML engineer, but I come from a software engineering background: years of full-stack work, with heavy DevOps and Terraform experience. I come from teams that deploy to production five times a day with real continuous deployment. And honestly? Pressing the button still feels weird sometimes. Every engineer knows that feeling, no matter how good the safety net is. So I wrote down the list that settles it. Ten commandments, one flow, written with data scientists and ML teams in mind, but it works for batch jobs, realtime inference, and LLMs alike. Answer honestly, and if all ten are true, you can ship to production anytime, in any form or way. [link] [留言] |
DevOps
Read original: https://www.reddit.com/r/webdev/comments/1wbip1q/the_deployment_decalogue/
The deployment decalogue
/u/SuspiciousPavement Reddit r/webdev
20 views
← Previous
SQL Joins in PostgreSQL: Patients, Doctors, and the Rows That Go Missing
Next →
DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
Related
Upgrading a Locked-Down Linux Fleet with Nothing but kubectl
DevOps
53
Dev.to (EN Zone)
PasteSwitch: 108 crypto-theft ads on a hijacked HBO Max Reddit account
DevOps
39
DEV Community
Code Hosting vs CI/CD: GitHub Actions, GitLab CI, Jenkins, CircleCI, Argo Workflows and More — What Actually Fits Your Stack?
DevOps
40
Dev.to (EN Zone)
My build finished in 0 seconds and thirteen test suites passed. They had run yesterday's binary.
DevOps
37
DEV Community
Comments0
No comments yet — be the first