A Career As Software Engineer
summary
Argues that code is inevitably imperfect and that testing is an engineering judgement not a management checkbox, citing work on TypeScript, MobX and Immer and the difference between open source perfection and product constraints. Recommends practical debugging like using Chrome developer tools dynamic breakpoints and wrapping getters to find state changes. Describes a 2010 Enterprise service bus that becomes a single point of failure after four years and says tech‑lead work means proposing a direction and letting others build it.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:52Imperfect code in engineering
- 3:17Brunel’s lesson on concepts
- 5:30Balancing quality and relationships
- 6:33Testing as engineering judgment
- 7:57Debugging tips for engineers
- 10:28Incomplete knowledge in senior roles
- 12:55Senior to tech lead transition
- 14:01Infrastructure project catch-22
- 16:46Accepting industry imperfection
- 17:29Brunel’s wisdom on progress
related talks
27m'The Art of Software Development'
49mExtreme Professionalism - Software Craftsmanship.
01h 00mThe Influential Software Engineer
06mEngineering You
52mThe Zen of Programming
51mThe Art of Software Development
22mDo We Need Software Craftsmen?
46mThe Zen of Programming. A personal journey towards writing beautiful code.