Interview with Ashwanth Kumar, Indix on the challenges of being a DevOps engineer
summary
Claims that developers must own operations not just code and gives concrete examples: debugging GC pauses, setting up backups and replicas, and keeping stateful services available so users never see outages. Describes on‑call and long hours — mentions teams working 12‑hour and 18‑hour days — and validates ideas via meetups and post‑talk feedback. Mentions Indix as context and emphasizes production monitoring, incident response, and the cultural shift that makes ops skills essential.
AI-written summary · about
chapters (5)
- 0:00Introduction and background
- 1:39Learning operations as a dev
- 3:16Infrastructure and uptime
- 4:28Importance of tech community
- 6:33Conference takeaways
