Code Structure: Keep classes simple or keep usage simple?

Published: 6/08/2019
Code Structure: Keep classes simple or keep usage simple?
Source: SOFTWAREENGINEERING.STACKEXCHANGE.COM

Tl;dr: In terms of the "high cohesion and low coupling" principle, how do I best deal with many simple objects that need to access the strings.xml resource in order to correctly parse an output? I'm setting up an app in android studio that handles accounts and stores payments to those accounts. I have set up a class for payments and accounts respectively and until now tried to keep them as simp

Read more
Related news
Comment
FACEBOOK