@jdubray Not yet. I've never been hugely opinionated as a developer. I constantly see zealous adherance to one pattern or another, and given a personal fault of mine- always assuming that others know more than me, I tend to find myself testing out others' viewpoints on the assumption that they seem to know what they're talking about. Eventually I come to my own thoughts about things and have to learn to trust those thoughts as valid, even though they may contradict, or even just be slightly divergent from, what is being preached. Even so, in recent times I'm starting to feel strongly about one particular viewpoint: there is no "one true way". There are many ways to skin a cat, and many different types of cats. Different approaches have different pros and cons, and true power and skill in architecting a solution comes from understanding different patterns and being able to compose different patterns into larger systems so that each pattern used is doing what it does best, i.e. is applied to subsystems it is most appropriate for. Saying things like "everything is a stream" or "mutability is always bad", or "never do X/always do Y", is shortsighted I think. I really like the Cycle pattern, but I'm not sure I agree with "everything is a always stream", or "only side effects should exist behind drivers", etc.