Home.DevOps
DevOps
Lights On
We are the ones who keep the lights on.
50% ratio
We spend about 35% operating infrastructure and 65% writing tools to automate operational tasks. (If the ratio approaches 50% operating - 50% coding, then we balance the load together with the product development team.)
Breaking Down Department Silos
Development and operations teams were usually split into two camps, with each camp following their own motivations (often competing):
- Development: more deployments to deliver exciting new features
- Operations: less deployments to deliver service quality (guarantee quality and service)
DevOps is here to solve this by making people from both camps work together in one team, establishing a shared vision.
Various Backgrounds
We spend about 35% operating infrastructure and 65% writing tools to automate operational tasks. (If the ratio approaches 50% operating - 50% coding, then we balance the load together with the product development team.)
Responsibilities
As DevOps engineers we share
these responsibilities:
-
Systems Analysis
We analyze technologies and develop
plans for improving our system -
Development
We design, code, build, configure, install
and maintain IT solutions -
Project Planning
We share our knowledge about systems,
explain their options, risks, impacts, costs
and benefits
-
Testing
We test code, processes, and deployments
to minimize errors and assure quality -
Deployment
We use configuration management software to automatically
deploy updates and fixes into production environments -
Maintenance and Troubleshooting
We perform application maintenance to ensure the
production environment runs smoothly -
Performance Management
We recommend performance enhancements by analyzing
bottlenecks, identifying alternative solutions, and
assisting with modifications -
Documentation
We write specifications, document our architecture decisions
in ADRs and document the
tools we write to automate the infrastructure