3 ms·
For a single modder, it may have to do with being a single developer, working on it over a long period of time and being a passion project. For a while, I was
by pnt12 5y ago
For a single modder, it may have to do with being a single developer, working on it over a long period of time and being a passion project.
For a while, I was the only developer working in a small module of a bigger project: I started the code base, discussed requirements with clients, implemented the needed features, tested the whole product end to end. I developed a very good instinct about it and about what any change would do, much better than any other project. My theory is that the code base matched my way of thinking, so thinking about it was pretty easy.
- MauroIksem 5y agoThis description has been life the last 4 years.
- Breza 5y agoWhat are you working on?
- smaudet 5y agoFewer (in charge) developers makes for a more stable product - even open source products fair better when they have a long term maintainer versus ownership changes frequently. The other thing is style - when used well, state machines don't require testing. There's nothing to test - either your machine works or it doesn't, there is no point testing state transitions because that is the fundamental job of the state machine. You may as well test that addition works. Ofc, they must be used well - problems may be difficult or overly complex to model as a state machine or even set of state machines - the pattern excels for small problems, less for large ones.