Value Oriented Programming. Part 1: You Say You Want To Write A Function
summary
Argues that small, testable functions reduce complecting by taking only what they need (pass orientation/tolerance values, not a whole Projector object), separates pure calculation from side-effecting apply steps (separate calculating from doing), and prefers returning results (std::vector moves, not in/out params) to void/in-out patterns. Shows practical C++ details: use const-ref, rely on move semantics, prefer free functions to fat class APIs, check code on Godbolt, and notes real benefits for testing, threading safety, and long-term maintainability.
AI-written summary · about
chapters (13)
- 0:00Introduction and setup
- 1:07Why we write functions
- 10:19Koan about functions
- 13:55Passing minimal parameters
- 20:30Value oriented programming basics
- 24:01Separate calculation from doing
- 28:55Functions and maintainability
- 36:05Avoid bloated classes
- 42:06Member vs free functions
- 47:10Parameter direction and naming
- 53:13Real-world code examples
- 57:03Refactoring and future-proofing
- 59:31Encouraging better practices
related talks
01h 42mValue Oriented Programming Part V - Return of the Values
01h 02mObjects vs Values: Value Oriented Programming in an Object Oriented World
01h 02mFunctional C++
45mPostmodern Programming
51mFunctional Principles for Object Oriented Development
01h 36mObject-Oriented Program: Best Practices
01h 01mFunctional C++
01h 02mFree Your Functions!