Your architecture is bad, but I don't care.

Hi, is your application architecture perfect? Yes, that's why you haven't released your application, you are still waiting all night to worry about the separation of responsibilities between functional modules (you don't have time to care about the traffic and renewal rate of applications ).

 

However, besides me, who will tell you that your architecture is bad? Why do I need to care about your architecture? Because I am only your user, and I don't care what your program looks like, how it is called, or in what language. What I care about is that it can solve my problems in the simplest and quickest way.

 

Your users do not care about the architecture. They only care about whether your application is easy to use.

 

I used to be a victim who did not understand this truth. In
I was obsessed with architecture when I was a company before friendly dingo. I hope that my code is the most concise for anyone. I hope that every file, DLL, and class meets any encoding standards you have heard. And I did it. It's perfect. However, my product was delayed because I had to spend more time organizing the program architecture (by the way, no one knows that I am doing this ), then I processed the customer's request for adding features. The final result is a medium product rating and poor sales. But my friends, my program is perfect.

 

Now, in the first week of development, I have selected the architecture and then set up this architecture. When the first release date of the product is approaching, I am confident that I will not care about the architecture any more, even though it is still unsatisfactory in some aspects, because I know that the functions of the program are all the work I have done.UserWhat you really want and care about. The architecture can meet the needs of applications.

 

So the next time you find yourself refactoring your code, stop and ask yourself if your users will benefit from this? In the end, this is the most important thing.