Is it possible to make mvp without nagovnokodiv?

Question

Mobile development

Is it possible to find this "perfect balance" / to sit on two chairs? So, in order to quickly write the main functionality, as those who stood at the origins of the project like to say, "on the knee" at the same time, "put" the rudiments of architecture, DI, tests, etc. So that when the project goes to the "people", there would be no (over) difficulties in introducing features and it would be possible to slowly finish the "fragile" places, without breaking anything.

Is there a big difference in time - if I write, balancing 50/50 on solid, dry, kiss, yagni, etc, how much time will I save than if I write, like Rahul from India, "roughly" speaking in a 100000 file lines. More than 2 times or not?

Answer 1

IMHO, there are no objective metrics. Time itself is a subjective concept, because for us, people, it has a value.
Perhaps if your MVP does not come out today, then it will lose its potential, the need will end or someone else will cover it. And perhaps it is just not needed today, but tomorrow it will be needed.
Perhaps the product is not very demanding at the time of release, but it does not live very long, in the sense that it brings profit in a short period of time, and is not suitable for long-term development. Perhaps it's the other way around.
The longer the project is going to live, the more effort should be initially put into the architecture. The longer you write, the worse you write. Principles, paradigms, patterns are designed to reduce the rate of deterioration.
What I'm trying to say is that how much time you gain or lose depends purely on your project and your understanding of the project's requirements. In one case, you will double the speed if you initially invest in architectures and designate a strict code quality framework. In another, it is enough to lay down the minimum quality standards, and it will be the fastest. In the third, Rahul will win.
And no one from outside will tell you what your case is, simply because we are not involved in the project and do not bear any responsibility for it.

Answer 2

If you don’t write a second Google, then the smaller the project, the more write fast shit code. If it starts to make a profit, then you will at least have a chance to rewrite it, if you come up with an "ideal architecture" you will not have a profit and sooner or later you will run out of money / desire / niche.