Message Oriented Programming

on YouTube ↗40m

" summary

Claim: messaging, not classes, is the core design primitive and treating internal calls as networked messages forces clearer contracts. Concrete work: a Ruby example turns a bare divide method into a message-oriented protocol using module prepend to validate inputs and always return a result-and-error hash. Tools and precedents named: Ruby, JSON APIs, Erlang/actor model, microservices and Docker. Outcome: protocol code increases reliability at the cost of added complexity, and runtime message contracts catch edge cases tests miss.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 15:29Protocols Are Valuable
3. 22:52Trivial Example
4. 23:47How would you fix it?
5. 31:35How do we start?

" related talks

• 36mThe Power of the ParadigmDouglas Crockford · Codemotion Rome 2018
• 43mGo Ahead, Make a MessSandi Metz · GoGaRuCo 2012
• 01h 01mValue Oriented Programming. Part 1: You Say You Want To Write A FunctionTony Van Eerd · CppNorth 2022
• 30mService Oriented Design in PracticeBryan Helmkamp · MountainWest RubyConf 2011
• 47mExpressing Design in Code: Architecturally-Evident Coding PatternsDr. George Fairbanks · Agile Roots 2010
• 33mPrototypes: Object-Orientation, FunctionallyFrançois René Rideau · Scheme 2021
• 38mWhat Object-Oriented Programming Was Supposed to Be: Two Grumpy Old Guys’ Take on ...Diego Miller Peterson · Onward! 2022
• 45mBeyond design patterns and principles - writing good OO codeMatthias Noback · Dutch PHP Conference 2019