How to be an inefficient developer?
summary
Engineering tradeoffs and concrete practices for getting real feedback fast: shorten loops with CI/CD pipeline and automated tests so juniors deploy in week one without breaking production, capture telemetry across seven billion transactions, and build small shared scripts that grow into team tools. Balance speed and quality with SRE-style error budget thinking, avoid premature overengineering, and limit context switches that can reduce IQ by 20%. Emphasize practiced learning and applying one shortcut or refactor at a time.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 1:35Engineering at Infobip
- 6:14Avoiding over-engineering
- 8:21Feedback loops and automation
- 11:28Agility and ownership
- 13:30Simple design and discipline
- 17:10Continuous learning
- 21:03Soft skills and wellbeing
related talks
25mEgoless Engineering
11mAccelerating Your Career: Becoming a 10x Junior Engineer
23mHow To Win Designers And Influence Developers
01h 06mTeaching New Tricks – How to enhance the skills of experienced developers
47mContinuous Deprovement will eat your product for breakfast
26mSolving the problems in front of you
51mCommon pitfalls in engineering teams and how to avoid them
54mRuin Your Systems By Making Them Perfect