Application Fundamentals for DevOps: From Code to Production Systems

Most engineers think DevOps starts with CI/CD. It doesn’t. It starts with understanding how applications are built, packaged, and executed. Because before you deploy anything… you need to understand what you’re actually deploying. Shift Focus: From Coding to Operating DevOps is not about writing code. It’s about operating code in production. That shift introduces new responsibilities: Version control → managing source code Build automation → compiling or preparing execution Package management → handling dependencies Deployment pipelines → automating delivery Containerization → standardizing environments As shown in the diagram on page 2, DevOps expands the scope from development to full lifecycle ownership. The Execution Divide: Compiled vs Interpreted Not all applications behave the same. There are two core execution models: Compiled (Java, C, C++) Code → compiled into binary Requires build tools Platform-dependent Interpreted (Python, Node.js) Code → executed directly No compilation