| I notice that these code smells as discussed are often really a function of the domain the developer is in. Lots of game examples, saw some sql too. What for me is the main reason not to like flags/booleans, is the current hype of MVP. Yeah, sure, a decision cam be yes or no for the current process. But what about, yes, but.... or no, unless.... for later iterations? Also, focussing on current user requirements leads to many booleans. What about, when the process is optimal, is it still a yes/no question? I also notice questions on different levels. In case of visible and static, for instance. One has to do (i guess) with rendering behaviour, while the other has to do with (let me call it) game engine behaviour. Is it then maybe also a case of (re-)defining the data models, as the element you're trying to specify gains depth? Even, possibly, that your definitions have become convoluted? In the game example, a difference between the element as an actor in a game scene as opposed to its representation for a render engine? |