How shouldn't you do DevOps?
Sort By:
Oldest
Sr. Director of Engineering in Travel and Hospitality2 years ago
Devops can be challenging operationally and financially, it lacks standardisation, skilled persons and lack of automation. The deployment becomes complex with more apps and releases coming over time and can be challenging if the persons lack skills, there's no automated deployments/failover mechanisms are in place. Chief Technology Officer in Healthcare and Biotech2 years ago
How *shouldn't* you do DevOps? Ok!1. Use a GUI and point-and-click your way through thousands of server installations, hoping you set the right things each time. Don't script it!
2. Save files and scripts all over the place, and if you want to make a change just edit it somewhere and have mismatched versions all over the place. Don't use version control systems.
3. Think of a server as a pet. Keep it alive, keep it running, keep patching it. If something goes wrong spend hours and hours to figure it out. Don't treat all your servers like cattle, spinning up and tearing down and rebuilding via automation as needed.
4. Leave resources running 24/7 that you don't need. Don't worry about consuming cloud costs.
5. Don't work with your colleagues on how you can continually, incrementally be doing things better and smarter with automation and documentation. Do whatever you want, whenever you want, no matter if you remember it later.
Is that what you were after?
CTO in Healthcare and Biotech2 years ago
As a band aide to overcome problems. Have a well thought out schedule for the number of users for each piece and design your architecture to meet those needs while minimizing complexity and technical debt. Technical Product Manager in Software2 years ago
DevOps fails when engineering teams underestimate the effort to maintain a prod environment that is representative of production workloads Yes there are day0 deployments but these early deployments often do not catch issues at scale
Senior Director in Healthcare and Biotech2 years ago
Do not bring in tools without the process fully laid out, and each team member knowing their role within the process. Do not toss DevOps out there without full immersion and training for the team. Set up intentional communication channels and points for the team to ensure discussion occurs.