The term DevOps is everywhere. But is not a job description. DevOps is a set of practices that combines software development (Dev) and information-technology operations (Ops), which aims to shorten the systems development life cycle and provide continuous delivery and integration with high software quality. As JavaScript Devs (front, back or full stack), we can usually think that we have nothing to do with the infrastructure or operations. Wrong. Your code, your responsibility. As a matter of fact, we are talking more and more about the tools, processes, responsibilities, and definitions of the new fancy Web Operations role (WebOps), which refers to a domain of expertise within IT systems management that involves the deployment, operation, maintenance, tuning, and repair of web-based applications and systems. With the rise of web technologies since mid-1995, specialists have emerged that understand the complexities of running a web application. Hey! Maybe you are thinking it’s simply too much. In this talk, we are going to see how a traditional web developer can assume DevOps functions avoiding some common mistakes or the well-known burnout.