Question

What are the problems if modules are tightly coupled?

Answer 1

The code base will be very rigid and thus very resistant to change. This is because when modules are tightly coupled a change to one module will most likely impact another module.

If in the above scenario the automated test coverage is bad or nonexistent then you will never know for sure where else you are breaking when making a change. This usually leads to a psychological phenomenon where software engineers get a phobia of making any changes to existing code.

I would recommend the book Working With Legacy Code by Michael Feathers that further extends this topic.

______________________________
how is it??? tell me in this comment
and follow me for more great answer
and also mark me brainillist ☺️☺️