Skip to main content

Banana Monkey Jungle

Why functional over OO?

https://medium.com/@cscalfani/goodbye-object-oriented-programming-a59cda4c0e53

Inheritance

Banana Monkey Jungle
The diamond relationship
Fragile parent class
Categorical (Taxonomy) v. Containment (or Exclusive Ownership) Hierarchies

 Encapsulation

 Object passed by reference to an Object Constructor is not safe
Deep cloning
MC Hammer v. Immutability
Global Scope

 Polymorphism
https://www.cs.utexas.edu/~mitra/csSummer2013/cs312/lectures/interfaces.html

Design by Behavior not Data

Comments

Post a Comment

Popular posts from this blog

There’s a lot of talk about transformation and some metrics around what we are lacking and need to do better. Do we also know what we do well and the good things about our work processes and environment that we want to keep? I’m concerned that if we don’t diagram this as a spectrum we risk running over those good things that we do in the course of transforming. Running agile retrospectives at team levels could provide us with this feedback DAKI – drop, add, keep, improve | Fun Retrospectives www.funretrospectives.com/daki-drop-add-keep-improve/ 1.         2.         DAKI is a great data gathering to foster the thinking around practices and the value the team get from it. It helps team members to understand each other ... KALM – Keep, Add, More, Less | Fun Retrospectives www.funretrospectives.com/kalm-keep-add-more-less/ 1.         2.       ...
Post a Comment
Read more

Microservices Design Patterns

functional decomposition or domain-driven design well-defined interfaces  explicitly published interface  single responsibility principle potentially polyglot http://blog.arungupta.me/microservice-design-patterns/ http://blog.arungupta.me/microservices-monoliths-noops/ https://go.forrester.com/blogs/13-11-20-mobile_needs_a_four_tier_engagement_platform/ three-tier architecture — presentation, application, data vs. 4 tier -- client, delivery, aggregation, services
3 comments
Read more