How to be an Ethical Engineering Leader
summary
Eight concrete leadership rules: a numbered list of eight guidelines focused on ethics and engineering at Lightstep, including POC is not the final product with explicit warning about shipping POC shortcuts as long‑term technical debt, developers are not commodities illustrated by swapping failures, and instrument your own code tied to observability and traces rather than outsourcing instrumentation. Specific examples include resetting a failing feature by replacing a lead developer, a team recovering by starting over, and pride blocking overdue stability work.
AI-written summary · about
chapters (12)
- 0:00Ethical engineering leadership
- 1:05Cutting corners frustrations
- 2:30Developers not clones
- 3:33POCs not final product
- 4:56Reset failing project
- 6:43Paradigm shifts fail
- 9:08Own your code
- 12:01Safe learning space
- 14:09Kindness in tech culture
- 15:54Pride blocks improvement
- 19:46Eight ethical leadership tips
- 21:21AI and new technologies Q&A
related talks
49mThe Ethical Engineer
18mAn Engineer’s Code of Ethics
22mWhat the Best Engineering Leaders Do Differently
42mPanel: Becoming an engineering leader
49mEngineering Leadership in Turbulent Times
27mAn Engineering Leadership Roadmap
15m7 Leadership lessons for the engineer that AI can't replace
32mThe Care and Feeding of Software Engineers