The stuff in jenis sets up a lot of stuff way later in the series
The stuff in jenis sets up a lot of stuff way later in the series
Usually it doesn’t matter what abstractions you choose when you try to factor them to support hypothetical future work, because chances are you incorrectly anticipate future needs.
In other words, generic code that only supports one use case will almost certainly have to be deconstructed to allow a good generic implementation for 2 use cases, so it is better to just write simple code and factor code out when you can see the real commonalities.
In other, other words, KISS, YAGNI
I hate reading code like this. It means that there is a bunch of object or global state that could be getting modified by anything all over the place that I can’t see just by looking at the method. In other words, if you say you understand this method, it is because you are making assumptions about other code that might be wrong.
I’ll take a 30 line pure function over a web of methods changing member state every time.
Hollow Knight is pretty different than metroid games and I’m not sure I’d directly compare them. I’m the only person I know that doesn’t like Hollow Knight and it seems like the departures it makes from the classic metroidvania formula that put me off it are part of the reason other people like it
Nature is healing
There is a video