How does static typing help you to tame the use of classes, reflection, configurations, rest interfaces, db interfaces, ...?
Just on friday I was talking to someone, where he said that his developers don't like the code and feel the constant urge to rewrite it... with the core functionality being a huge mess.
Comments
I can imagine, but the strong typing does help keeping a bit of order.
How does static typing help you to tame the use of classes, reflection, configurations, rest interfaces, db interfaces, ...?
Just on friday I was talking to someone, where he said that his developers don't like the code and feel the constant urge to rewrite it... with the core functionality being a huge mess.
Most of the enterprise projects I work on, developers tend to "forget" about unit tests after the first few sprints.
Never coming back to them unless ordered to do so by management.
Without static typing the chaos would be even bigger.
s/strong/static/