My Colleagues Are Terrible Programmers
summary
Discussion of the concept of “bad programmers” (горе‑программисты): what causes poor coding — individual skills, development practices, soft skills, or company/project-level issues — and how to identify such people reliably. The panel describes methods to self-test for being a bad programmer and proposes ways to keep improving and maintain code quality despite those challenges; participants include Nikolay Ashanin (moderator), Alexander Cherny, Evgeny Suvorov, and Daniil Popov.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:21Defining bad programmers
- 10:10Technical vs soft skills
- 27:57Is 'good enough' acceptable
- 31:43Bad code examples
- 42:09Beyond incompetence
- 55:51Self-assessment and growth
- 1:03:40Good programmers look bad
- 1:12:45Q&A
related talks
57mHow to Become the Programmer Everyone Wants
01h 12mKeynote: "Am I A Good Programmer?"
20mKeynote: Programmers Don't Like People...or Do They?
48mWhy Johnny Can't Code Good
01h 01mRound Table: Developer Interviews. What’s Good and What’s Bad
08mThe Noobs and the Programmers: On Teaching Programming
01h 38mPanel: How to Grow Strong Developers
55mDeveloping and evaluating programmers in product companies