juancrg90 / clean-code-notes Goto Github PK

There maybe miss a comma between 'variables' and 'functions' in the sentence of 'Names are everywhere in software. Files, directories, variables functions, etc. Because we do so much of it. We have better do it well.' in Chapter 2.

There are a lot of information about keeping functions short, not too many parameters for functions and keeping classes small and dedicated specific purpose.

But what about the file-wise organization of classes? What is considered clean code in that aspect? Is it having one class per file? Or is it allowed to have multiple classes in the same file if they are in the same area. And what about languages that can split the interface definition into a different file than the implementation (like C++ with .h and .cpp files)?