> I think this generate phantom requirements that doesn't contribute for the solution. Just change the code when you need it. YAGNI -> You Aren't Gonna Need I

> I think this generate phantom requirements that doesn't contribute for the solution. Just change the code when you need it. YAGNI -> You Aren't Gonna Need It [1] If you want to know more about about Python I recommend Raymond Hettinger's videos [2] About ECA (which I presume is Entity Component Architecture) I have to say two things: 1) I've seen this pattern/concept be called many different things: Entity-Component, Game-Object Game-Component, Entity-Systems, etc. And at least two major ways of implementing it. 2) Like most design patterns, they exist to help you design program using languages that use heavy class-based OOP and static typing. In Python everything is dynamic and it uses duck typing, so can "draw some inspiration" from the pattern instead of implementing it by the book. [1] https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it [2] http://pyvideo.org/speaker/138/raymond-hettinger http://pyvideo.org/speaker/138/raymond-hettinger