Keynote: Learn Programming, then Learn how to Be a Programmer
summary
Founders describe building open source libraries like CopperSpice and DoxyPress, swapping out autotools for cmake (one commit touched about 150 build files), and keeping a temporary default to handle a 50-camera streaming load that ran in production for years. They show concrete failures: unit tests hiding bugs due to undefined behavior, a 40-server cost estimate that forced rethinking, and a repeated scheduling tradeoff of three weeks versus six where pragmatic redesign beats overtime.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:06Barbara Geller
- 5:19Data Types
- 11:25What Does Effective Mean
- 26:27How To Handle the Scheduling Issue
- 33:37Explain the Purpose of the Code
- 40:35Is There an Art to Testing
- 44:41Confuse the Theory of Programming with the Art of Being a Programmer
- 56:10Tandem Programming
- 1:01:53Do You Design and Write the Best Code You Possibly Can Given Your Skill Set Today
related talks
40mThe Best Programmer I Know
43mKeynote: A tech görl origin story
59mKeynote
01h 12mKeynote: "Am I A Good Programmer?"
43mThursday Keynote -- What Programming is Really About
57mKeynote: How To Address 7 Major C++ Pain Points with Tools
01h 00mKeynote
01h 01mKeynote: Software Craftsmanship – Growing a Technical Culture