The short answer is, the bricks in the wall! 😊 Let's check it via an example Imagine, we are participating in a bigger project with multiple developers for a long time. We have just started the project from zero without any common agreements on how to build up the project. There are no best practices on how to develop the project, we all just apply the changes ad-hoc, as it is. The goal is to finish the project fast! ...time passes by... We have already spent quite a lot of time on the project next to the other developers, and we are starting to think it is getting harder and more complicated to implement new features in the app -> it is challenging to figure out which code to modify, what is safe to be extended. Things get even more complicated when requirements change at the very last minute, and the project's code is not dynamic enough to handle these unexpected changes in an acceptable time. And we have these many new annoying, unexpected bugs! ..and this list could go...
How to develop web applications with ASP .NET Core and Blazor