Keynote: "Am I A Good Programmer?"
summary
Three quick self checks for being a competent programmer: avoid outrageous catastrophes — systems that fall over at three concurrent users or require a full rewrite from a bad assumption are red flags; others ask your advice — people copy your fixes, return to report "it worked", or ping you on Slack/Stack Overflow; do you enjoy it — you finish work with tests, docs, and updates. Improve by practicing with Git, using coroutines and constexpr where appropriate, reading blogs, joining communities, speaking, and shipping small finished projects.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 0:46Defining a good programmer
- 10:39Imposter syndrome and growth mindset
- 21:59Avoiding programming catastrophes
- 32:12Do others seek your advice?
- 32:34Do you enjoy programming?
- 44:15How to improve your skills
- 59:17Self-evaluation checklist
- 1:00:06Q&A session
related talks
40mThe Best Programmer I Know
01h 18mKeynote: Steps to Wisdom for C++ Developers
52mKeynote: Steps to Wisdom
43mYou Belong In A Room Full of Wizards
01h 04mKeynote: Learn Programming, then Learn how to Be a Programmer
50mHow I'm Becoming a Programmer
27mEvergreen skills for software developers
48mEnding Keynote: 7 Principles of Productive Software Developers