Reduce / fold from #FP is incredible…
Given some initial state, and a new event / command / action / update, get the next state.
Understand that, and you might never want to throw out the events / commands / actions / updates again!
| Website | https://theaidia.com |
| Fave Language | Typescript |
| Fave Cloud | AWS |
| Fave Stack | Event Sourced Microservices |
Reduce / fold from #FP is incredible…
Given some initial state, and a new event / command / action / update, get the next state.
Understand that, and you might never want to throw out the events / commands / actions / updates again!
One day, I woke up to find 500+ unread junk emails in my inbox.
That was my wake up call. I resolved to finally go through the effort of unsubscribing. 1-2 minutes every morning and I would clear through a dozen different, awful unsubscribe flows.
And now, my inbox is quiet.
Use the same approach for compiler warnings, linter issues, and so on to finally get that peace of mind.
I wonder if there are any aspects of model based development that people miss when they are doing #eventsourced systems?
(And, if so, can these be recreated on top of a #ES system?)
https://engineering.fb.com/2022/11/22/developer-tools/meta-java-nullsafe/
IMO, languages that allow NPEs should have been retired already; languages that offer nullable types are better; those that, additionally, allow opting in to treat possible NPEs as compiler errors are in the right direction (Scala 3 explicit nulls); and those that lack the concept of Null, altogether, are the ones that we should be using in the 21st century.
Idk… the complexity starts with the name and only gets worse 😅
Kuber nuts?
Kibble ettes?
Kegel nutty?
Something many people in tech will have to deal with is the uncomfortable question of Elon actually pulling this thing off.
How will you survive the regression back into the dark ages?
Today’s poem is called ‘Word Crunching’.