How 'Up & Running' Culture is...
summary
Claim: the prevalence of “easy start” pieces like up and running guides for Docker, Kubernetes, Ansible and AWS actively lowers how non‑engineers value deep engineering work, which causes shorter timelines, smaller hires, more piled tasks and higher burnout. Evidence: concrete blog and talk titles promise speed while omitting scale, failure modes and dependencies; decision makers treat tools as solved and beginners get discouraged. Remedies include explicit levelling, stating assumptions, citing sources, sharing failures and using the perceived value equation to show benefits versus real costs.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:10Perceived Value Equation
- 10:13In The Wild
- 12:30Memes
- 13:28Why do we participate?
- 14:51Decision Makers
- 17:19Beginners
related talks
34mThe Return of the Dull Stack Engineer
45mThe DevOps Revolution: We Haven't Always Known Everything
25mWork On The Wrong Things First
30mHow to talk like an Engineer
52mSecrets of a Strong Engineering Culture
05m5 ways to burnout your engineers
27mDevOps and Baking
14mIt's Like Coding in the Dark: the Need for Learning Culture in Engineering Teams