20 field-tested AI/ML rules: never let coding agents run commands themselves

kmeanskaran · x · 2026-11-19

An AI/ML practitioner shares hard-won lessons: - Don't chase every trend; make every project end-to-end. - Learn high-level ML system design; explain projects via business, data pipeline, model/agent, eval, deployment, and numerical results. - Never let coding agents run commands themselves — have them produce commands and run them yourself; always check vibe-coded results against expectations. - Companies care about impact, not your stack; interviewers want knowledge, not buzzwords. - MLOps is mandatory — no specialized ML role remains; know Airflow, MLflow, Linux, Docker, CI/CD, Terraform, Redis; Bash/YAML/Markdown/JSON are 90% of engineering. - Automate low-level coding with LLMs but keep a human in the loop. - GraphRAG is the most important thing to learn; ETL design is high-leverage. - Firms treat AI, ML, MLOps, and data as one department — learn all of it.

Original post →

More from coding & agent

coding & agent channel →