Pretty framework, same old code
Are you a fad-follower? Do you always use the latest new development environment simply because it’s this year’s model? Here’s my axiom: Application architecture is less than optimum if it dogmatically conforms to a trendy framework at the cost of following good design/implementation practices. For example, is it correct to be inflexible and use private fields and getters/setters for a simple data structure (e.g. a DTO)? If a field is transparently readable and writable why not simply make the field public? In most languages you can do that. Granted, in some you can’t. For example, traditionally in Smalltalk all fields are private and all methods are public.In general it’s a good thing whenever you can throw out, or avoid writing, some...