Up to Code
summary
Worth watching if interest is in a concrete C++ migration case: an actual utility uldb_dump relink with a noisy logging regression, swapping an old lookup API for a new one, and the messy prototype that is not up to code. Covers practical fixes—TSAM level 1 rollout constraints, converting nullable API structs into contracts and strong types, and adding dependency injection to enable unit, integration and environment tests.
AI-written summary · about
chapters (33)
- 0:00Intro
- 8:33Fixer vs Handyman
- 10:56When do you need an electrician
- 12:04Old work and new work
- 14:37From scratch
- 15:37UDB dump
- 16:38TSAM level 1
- 17:50First line of garbage
- 18:41Fixing the logging
- 20:18Latest code
- 21:14Logging
- 21:52Old API
- 22:35New API
- 23:24Error Handling
- 23:46Old vs New
- 24:14What to Code
- 25:48Vocabulary Types
- 27:13Useruid
- 27:55Aggregates
- 28:39Documentation
- 29:15Utility Classes
- 29:56Contracts
- 30:46Why do contracts
- 33:54Dump
- 34:23Environmental dependency
- 35:10Inheritance
- 39:47Other Testing
- 41:09Inspections
- 43:59Summary
- 44:48Standards
- 47:42Support for Software Engineering
- 54:33Mentorship
- 56:59Quality
related talks
53mInvestigating C++ Legacy Design Trends: Newer Isn’t Always Better!
56mThe art of keeping your project from falling apart
32mMaking Sotware Better, Despite Having Users
54mSeeing Like a Programmer - Resiliency, Limits, And Moral Hazards In SE
30mOptimizing for Developer Delight
57mLarge-Scale Refactoring @ Google
01h 09mA CTO's guide to Modern C++
29mAging: Evolving Software, Tools, and Ourselves.