What‘s the purpose of separating your code into "independent" modules if each module contains everything anyways?

Well, that's a very good point but it's kinda the monolith vs microservice discussion. I prefer monoliths. If you split up everything completely on module level using it's interface, it's kinda schizophrenic behavior. I think it's considered professional to make everything isolated. But if you write code according to "the book" you'll never finish anything.

@retoor this is not monolith vs microservice. A module != service.
The Linux kernel for example is a famous modular monolith.

Also a microservice architecture is an organisational (people and teams) solution not a code organisation solution. It's a Conway's law thing.

Main reason is that you can group concepts, but being strict about "independent" can be a bit much IMO