Journey to becoming a Developer: an Administrators story
summary
Claims that operators must adopt a developer mindset and concrete steps to get there: adopt Ansible and Salt (both Python‑based) for automation, favor list comprehensions and the with statement over manual loops and open calls, document functions with docstrings and optional type annotations, and enforce tests using nose and coverage — one utility reports about 90% test coverage. Mentors push idiomatic Python and small projects (e.g. processing personal scuba‑diving data) as hands‑on practice that actually improves code quality.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:56Happy sysadmin day
- 2:57DevOps
- 3:45Features vs Changes
- 5:09Communication Attitude
- 7:26Writing Good Code
- 8:07Thinking about Things Right
- 9:40Stand of Pines
- 10:11Simplicity
- 10:57Explicit
- 12:04Wif
- 13:03Python
- 14:36Hacking
- 14:53Functions
- 15:46DocUtils
- 17:22Coverage
- 17:56Experiment
- 18:58Conclusion
related talks
33mWhat it takes to become a great developer!
27mDeveloping Devopsers
30mForging Your Path to Senior Developer
27mBeyond developer
13mGrowing Developers: Helping Junior Developers Improve & Succeed
01h 00mBuilding better developers
46mThe Developer Journey
30mLessons Learned: A Developer's Perspective on Teaching & Learning