▲ 327 ▼ OOP at home: (thelemmy.club) submitted 6 months ago by freddo@feddit.nu to c/programmer_humor@programming.dev 89 comments fedilink hide all child comments
[–] jenesaisquoi@feddit.org 63 points 6 months ago (2 children) Needs more AbstractDefaultProxyBeanFactoryFactories permalink fedilink source parent hideshow 4 child comments replies: [–] Supercrunchy@programming.dev 24 points 6 months ago (2 children) And dependency injection! Every class needs to use DI for calling other classes, even though we'll have anyway just a single implementation for all of them, and we won't be using this flexibility at all (not even for tests where it might be useful for mocking dependencies). permalink fedilink source parent hideshow 4 child comments replies: [–] jenesaisquoi@feddit.org 14 points 6 months ago Methods calling other methods? Heresy! There needs to be two or three interceptors on there, and some indirection over RabbitMQ using spring-integration, at the very least. This is how you write proper enterprise-level software: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition permalink fedilink source parent [–] VibeSurgeon@piefed.social 2 points 6 months ago Why even use DI if you're not planning on faking dependencies for unit testing purposes permalink fedilink source parent [–] VibeSurgeon@piefed.social 2 points 6 months ago I managed to organically create a StrategyFactory at work once. It was a good design, but it felt extremely wrong permalink fedilink source parent
[–] Supercrunchy@programming.dev 24 points 6 months ago (2 children) And dependency injection! Every class needs to use DI for calling other classes, even though we'll have anyway just a single implementation for all of them, and we won't be using this flexibility at all (not even for tests where it might be useful for mocking dependencies). permalink fedilink source parent hideshow 4 child comments replies: [–] jenesaisquoi@feddit.org 14 points 6 months ago Methods calling other methods? Heresy! There needs to be two or three interceptors on there, and some indirection over RabbitMQ using spring-integration, at the very least. This is how you write proper enterprise-level software: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition permalink fedilink source parent [–] VibeSurgeon@piefed.social 2 points 6 months ago Why even use DI if you're not planning on faking dependencies for unit testing purposes permalink fedilink source parent
[–] jenesaisquoi@feddit.org 14 points 6 months ago Methods calling other methods? Heresy! There needs to be two or three interceptors on there, and some indirection over RabbitMQ using spring-integration, at the very least. This is how you write proper enterprise-level software: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition permalink fedilink source parent
[–] VibeSurgeon@piefed.social 2 points 6 months ago Why even use DI if you're not planning on faking dependencies for unit testing purposes permalink fedilink source parent
[–] VibeSurgeon@piefed.social 2 points 6 months ago I managed to organically create a StrategyFactory at work once. It was a good design, but it felt extremely wrong permalink fedilink source parent