[senux]

> I call BS on dogmatic rules like that. Good architecture is analysing the requirements at hand and explicitly articulating and weighting the trade-offs.

I particularly like your point above. I apply that same perspective to several other domains. For example, purchasing a new phone, choosing a new tool for work or personal use, purchasing a car.

It's easy to make decisions based on personal preference or, like you mentioned, dogmatic rules and call them "the right way of doing things".

[smoe]

I agree, but it also fairly easily to be dogmatic overanalyzing things instead of executing.

Especially early stage, you have limited knowledge what the requirements of a product that will stick might be.

I think considering cost of future change and try to keep it low as a general rule is more important, than trying to make all the right choices from the get go for something you don't yet understand. You might have a good understanding of the problem, but that doesn't mean your solution will work and you have to adapt.