Today I think it became apparent why we have so many data and prod issues...

No one understands SOLID design principals... Particularly Separation of Concern. No wonder all the Spring (DI) modules look like a mess of God functions that are impossible to reuse and difficult to extend...

Separation of Concerns == Single Responsibility Principle?

@GinjaNinja yea ok I got the name wrong... Maybe I'm a bit more loose.

But like from a use case perspective, keep things separate and abstract things that are likely to change (input parsers, output options), don't create hard dependencies

My particular problem today:

Dev: Oh we got a daily process and a special process. The logic is mostly the same but there's an issue with expiring old data. We don't want the Special to overwrite Daily.

Me: then in the program add in a run parameter telling it which tables to use

Dev: but why use 2 different tables? We only need 1.

Orz.... Creating a table is cheap, debugging data issues and solving these edge cases are expensive and unnecessary...

Also it's not obvious to a new dev there are 2 different processes using the same table...