I was experiencing problems to maintain the code in my code, because of the large and poorly defined classes (it grew a lot over time), to simplify the question I will split the timeline of the code in version 1 and 2 .
Version 1:
Virtually all of the screen construction and initialization of the variables occurred in the main method, although we had a relatively large number of external classes (Components, Entities, etc.) and the classes related to the database were divided into Select, Delete, Update and Insert.As reported above the main difficulty here was the maintenance, although it was not so difficult to find the methods ended up getting too much code unused with time and the propagation of errors was difficult to deal with.
Version2:
Almostthewholecodehasbeenredistributed, splitting the packages by functionality and breaking the code in smaller classes with more defined purpose.
Immediate code maintenance has gotten much easier as well as allowing me to extend functionality with almost zero error propagation. However the performance of the application has fallen noticeably.
During university, I believe that because we produce small projects and personal use, we do not have to worry much about the relationship between performance and scalability.
My question is whether, in the real world, these two metrics are irreconcilable , so investing in one necessarily will have to give up the other?
Note: For purists, let us take the response time of the application as a metric for performance.