Why I moved toward DevOps

I started my Web Developer career building and maintaining applications in PHP, JavaScript and e-commerce systems.

Over time, I noticed that many real problems were not only in the code, but also in deployment, infrastructure, environments and release processes.

Questions like:

• Where is the documentation?
• How do we prepare the local environment?
• How do we test the code?
• How do we deploy it?
• Why does it work on my machine but not in production?
• How do we rollback?
• Where are the logs?
• What if the server is down?

Each of these problems takes time. Sometimes it requires several people to investigate, fix and explain what happened. It can create a lot of frustration.

• Developers want to code.
• Business wants to see results.
• Users want the application to work.

That’s why I moved deeper into DevOps. I realized that I could use my experience with Linux, Git and coding to solve these kinds of problems - not only by writing code, but also by improving the whole delivery process.

For me, DevOps is about:

• Faster onboarding
• Faster and safer releases
• Easier debugging
• More stable environments
• Better availability

Good code is important but without good deployment, infrastructure, monitoring and release processes, even good code can fail.