Microservices

A species would be a combination of roles [DCI?], instead of being characterized as an animal, which would not necessarily be the best description. At a larger scale, microservices are a very similar case [of composition instead of inheritance / ISP], they are pieces of a system separated by responsibilities, instead of being a great monolith.

https://hackernoon.com/solid-principles-made-easy-67b1246bcdf

Procedural vs OO

In any complex system there are going to be times when we want to add new data types rather than new functions. For these cases objects and OO are most appropriate. On the other hand, there will also be times when we’ll want to add new functions as opposed to data types. In that case procedural code and data structures will be more appropriate.

https://medium.com/mindorks/how-to-write-clean-code-lessons-learnt-from-the-clean-code-robert-c-martin-9ffc7aef870c

On the necessity of having multiple models in your code base

You cannot under any circumstances have a single model that does everything for you and does it well. It doesn't exist!

-Greg Young https://www.youtube.com/watch?v=JHGkaShoyNs

User stories and use-cases are terms that mean the same thing

And nobody quite understood that there's no difference between a use-case and a user story: they're the same thing.

 The Principles of Clean Architecture by Uncle Bob Martin

CPU Transistor Usage

The trick to cache design is finding an algorithm that gets key information into L1 cache when it's needed. This is so important to performance that more than half of a processor's transistors may be used for a large on-chip cache.

https://www.computerworld.com/article/2584352/computer-hardware/inside-a-microprocessor.html

Diodes vs Transistors

Since all diodes having only two terminal means no controlling action possible whereas Transistors (BJT, FET’s e.t.c) have three terminal.Thus configuration of transistors allows for controlling action due to presence of controlling terminal (i.e for BJT ‘Z’ is Base and for FET’s ‘Z’ is Gate terminal).

http://qr.ae/TUTsSg

JSF vs Struts 2

JSF was designed in part by the authors of Struts to create a "Struts" that did a more accurate implementation of MVC (Struts is technically "Model 2") and to get rid of all the interface and subclass dependencies. The idea being that POJOS are more re-usable and easier to unit-test offline than framework-dependent code. Which is why I chant endlessly:
The more JSF-specific code that is in your JSF webapp, the more likely it is that you're doing it wrong.
The other thing that the Struts folks didn't like about Struts was that you had to define too many classes for each component. In JSF, you define a view template file, a backing bean (model), and that's basically it. There's no separate "action" class to transition data in and out of the MVC part of the webapp, just POJO methods that are defined in the same class as the POJO model.

https://coderanch.com/t/625642/java/Struts-JSF