tacticsarchitecturedesign patterns
Design patterns are like tools in your workshop. They can greatly simplify both writing code and the code itself. Today, we will start with examples of patterns specifically related to a pattern called Rules Engine.
The rules engine allows you to improve both separation of concerns and high cohesion and low coupling, thereby significantly reducing code complexity.
"Software architecture is the design of API, database and should be robust and stable."
There is almost nothing true about the previous sentence. Modern software architecture is something very different. It's missing the main thing. What the goal of the architecture actually is.
So what is software architecture?
Many things can be regained or replaced. A house, a car, money - all of that comes and goes. There is a resource more precious than money or gold. Time. Time is a great equalizer; everyone has the same amount - 24 hours a day. There is no way to have more. The only thing you can do is manage it.
Have you ever heard people to say "I do not have enough time"? I'm not talking about work. I'm talking about "I want to go to the gym, but I don't have time.".
Is it worth always "being right"? What does it mean to "be right" in software development? How important is it for a leader to "be right"? When does it all becomes arrogance? Have you ever had to deal with someone who always has to be right?
Explore the points of view of developers, leaders, and architects.
Continuing my previous article, we will discuss scale, support and accidental complexity, types you can manage, reduce and even remove.