> I've worked with people that always feel the need to "add a level of abstraction" or "build a framework" for (and out of) everything This is my experience wi

> I've worked with people that always feel the need to "add a level of abstraction" or "build a framework" for (and out of) everything This is my experience with the Java folk, and they're certainly not being inspired by category theory. Indirection isn't abstraction. What I usually come across is someone wanting to make a REST POST, but they wrap it in a networkconnection in a networkclient in a networkworker in networkmanager, which can only be instantiated by a network factory. CT-thinking (not that I've studied any) is more like: a POST is an arrow from request to response. Can we join such items head-to-tail? Is it ok to substitute createUser.then(createPassword()) for createUserAndPassword? Can we map over the arrow without unpacking it and repacking it, etc. Have a read of https://www.haskellforall.com/2014/04/scalable-program-architectures.html https://www.haskellforall.com/2014/04/scalable-program-archi...