We have built a library which can handle RESTful requests based on configured endpoints.
Are there any benefits to delegation over subclassing/inheritance in the case of a singleton?
Example:
How can I centralize authentication of an AzureResourceManager and write testable classes that use it?
I have to update app code running in a container on AKS to use a WorkloadIdentityCredential. I have to test code that I update in order to pass CI quality gates.
How can I centralize authentication of an AzureResourceManager and write testable classes that use it?
I have to update app code running in a container on AKS to use a WorkloadIdentityCredential. I have to test code that I update in order to pass CI quality gates.
UML diagram feedback
I am currently learning design patterns and I have decided to develop a chess game.
Why blaming “global state”, instead of my user requirements, makes program state unpredictable?
According to Why is Global State so Evil?, I know I should not allow the existence of global state, one of the reasons is so called “it makes program state unpredictable”.
Class inheritance design with protected methods and run time base handlers
Using C#, I got a class called BaseConfigurations which handles CRUD operations. This class also contains a protected method which is used inside the CRUD handling methods:
When shall one ignore the absurdity of some code diagrams?
I wrote a relatively small user interface for Unity, whose job is to ease working with parts in a scene, i.e. show/hide/toggle objects to reduce clutter.
Does the Mediator Pattern Solve the Same Problems as a Queue?
I am very unfamiliar with the Mediator Pattern in practice, but it seems that the core is decoupling events from handlers (“Colleagues”). The benefit being “lose coupling” in the sense that you can change code in a “colleague” without breaking the caller and vice-versa.
Design for adding an additional version of a service to live side by side with the first one
This is a follow up question to this question: