Life After Business Objects - Confessions of an OOP Veteran

on YouTube ↗34m

" summary

Team replaces OO business objects with F# and reports handling gigabytes of media per hour while cutting time to production and reducing failing unit tests dramatically. Domain model uses algebraic data types and many small immutable records so illegal states disappear, optional/null usage drops, and each processing stage has its own type. Concurrency becomes simpler via immutability, workflow code composes with piping, and deployment cadence and operational stability improve.

AI-written summary · about

" chapters (9)

1. 0:00Intro
2. 5:10Modeling a point
3. 8:13Principle difference in initial sets of defaults between OOP & FP
4. 11:54Business objects
5. 18:08Order processing
6. 22:06Domain modeling in F#
7. 28:12Can't we adopt FB style in C#?
8. 33:26What advantage did we gain with F#?
9. 34:07Outro

" related talks

• 35mLife After Business Objects - Confessions of an OOP VeteranVagif Abilov · GOTO Oslo 2020
• 37mLife After Business Objects: Confessions of an OOP VeteranVagif Abilov · GOTO Copenhagen 2021
• 44mLife after business objects. Confessions of an OOP veteranVagif Abilov · Build Stuff 2020
• 59mLife After Business ObjectsVagif Abilov, Maksim Arshinov · DotNext 2019 Piter
• 52mF# in the real worldYan Cui · Lambda World 2015
• 29mSingle Value Objects: where DDD and Functional Programming Share ForcesCorniel Nobel · Build Stuff 2020
• 01h 08mWhy Every Day as a Developer Would Be Easier with F#Urs Enzler · JetBrains .NET Days Online 2021
• 46mFunctional developer in object oriented worldBartosz Sokół · 4Developers 2017