Answer the question
In order to leave comments, you need to log in
How to think about the architecture of a java application?
How to learn to think over the application architecture correctly?
That is, which classes are needed by the application, which are superfluous.
Can you recommend a textbook?
Answer the question
In order to leave comments, you need to log in
Why bother thinking about it? We write a class, we write 10 more. Oh! Then we start the package! Oh, 10 more bags. Something went wrong... Refactoring - Martin Fowler chuckles viciously.
More refactoring, more and more.... Icon - Martin Fowler.
Customers are in a trance, developers too... And we are all refactoring and refactoring..
(sarcasm)
But the application still needs a structure.
1) Start with a problem statement
2) Then define the architecture of the application
3) Determine how this architecture will expand
4) Start writing
5) Well, if it doesn’t work out, refactor
6) Close the project - it’s useless ...
Oh, well, I forgot about tests. And they can be refactored too.
Agile Way to Hell.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question