4 ms·
This has nothing to do with scientific programming and everything to do with "best practices" being mind blowingly awful. Coupling execution and data is good f
by CyberDildonics 10y ago
This has nothing to do with scientific programming and everything to do with "best practices" being mind blowingly awful. Coupling execution and data is good for data structure initialization, cleanup, and interface. Everywhere else they should just be kept separate. Data structures should be as absolutely simple as possible, not as full and generic as possible.
Where people get into trouble many times is thinking that every transformation or modification of data should be inside one data structure or another, when really none of them should be except for a minimal interface.