About the Least Powerful Abstraction

Regular Programming

Imagine Andreas going around making annoying electronic sounds all the time.

Strike that. Andreas and Lars discuss using less power - less fancy abstractions - to make things easier to understand. Andreas likes to do a de-powering pass to code.

Avoid making something which is more general than is useful.

Lars goes into the lure of event sourcing - going for very high data resolution - it might come in handy! - at the cost of a lot of other things - how do we prevent duplicate user names?

You've got to love a JSON blob.

Finally, Lars derails Andreas' arrow of time and discussion of locking things down early when possible.

Links

• Power glove
• Ghost in the shell 2
• Stand alone complex
• Unlimited power!
• For-comprehensions
• Nerveshub
• REST
• Squiggle
• The lenses paper - Functional Programming with Bananas, Lenses, Envelopes and Barbed Wire
• Not hot dog
• Domain-driven design
• Event sourcing
• CQRS
• Saga - event sourcing pattern
• Data lake
• Data lakehouse
• Ecto
• Penny Arcade - On discomfort
• Prince of Persia: The sands of time