Thoughts on architecture (Category Architecture)

I realized that in my pet projects I architecture I'm getting better from the idea that I want to cut chips fast, but

• I do not want to spend a lot of money on maintenance - you need effective CI / CD piplins and the optimal scheme for working in a product.
• I don't want to spend a lot of time on maintenance - applications should be self-healing, and the evolution of the solution is easy in the right direction for me. I don't want to spend a lot of words explaining to agents how to saw new features. (||Explain that we are ready to waste time.)|| A clear architectural framework should be established.
• I don't want to waste a lot of energy on a review and deal with regression bugs - you need a lot of deterministic checks.

It seems to turn out well, but when I mess up, I immediately see that the limits have run out or the budget has begun to quickly leave - then this is a direct trigger to figure out where I set up:) In large companies with such triggers and quick feedback is bad and therefore by the time people decide to tackle the problem, systems have not just shortness of breath, but obesity. 4 degree and fatty plaques in the heart, which can no longer pump blood normally for the whole body.

P.S. Thoughts appeared during study whitepaper about AI for software architecture, well, within the framework of fixes of the next problems, where I a little bit screwed up architecturally.

#Architecture #Engineering #Software #SystemDesign