Interesting article I read today
Why Doctors Hate their Computers by Atul Gawande
Mrinal Mukherjee – A DevOps Confessional
- Not about accidents, it is about Planned Blunders that people are doing in DevOps
- One Track DevOps
- From Infrastructure background
- Job going into places, automated the low hanging fruit, easy wins
- Column of tools on resume
- Started becoming the bottleneck, his team was the only one who knew how the infrastructure worked.
- Not able to “DevOps” a company since only able to fix the infrastructure, not able to fix testing etc so not dilvering everything that company expected
- If you are the only person who understands the infrastructure you are the only one blamed when it goes wrong
- Fixes
- Need to take all team on a journey
- But need to have right expectations set
- Need to do learning in areas where you have gaps
- DevOps is not about individual glory, Devops is about delivering value
- HR needs to make sure they don’t reward the wrong thing
- MVP-Driven Devops
- Mostly working on Greenfields products that need to be delivered quickly
- MVP = Maximum Technical Debt
- MVP = Delays later and Security audits = Your name attached to the problem
- Minimum Standard of Engineering
- Test cases, Documentation, Modular
- Peer review
- Evolve architecture, not re-architect
- Judgemental Devops
- That team sucks, they are holding things up, playing a different game from us
- Laughing at other teams
- Consequence – Stubbornness from the other team
- Empathy
- Find out why things are they way they are
- Collaborate to find common ground and improve
- Design my system to I plan to work within constraints of the other team
