Isn't the whole question what you need to do to get a nice, clean interface?
Also wouldn't it be true that the ideal data structure of a book would depend on whether you were optimizing it for reading or for writing?
Wouldn't it be better to just say we should follow whatever creates nice, clean interfaces but allows the developer access to internals as needed for debugging purposes? The problem I have with the principle of least knowledge (the Law of Demeter) is that it is used to make objects opaque. I think that's what causes the biggest backlash.
I mean the whole point is to create clean interfaces, right?
The law of least knowledge is interesting though, provided it is not an excuse for opacity. Why should my program have to know beforehand what parameters a stored procedure takes? Why not discover them at run-time and map in properties or other variables?
Also wouldn't it be true that the ideal data structure of a book would depend on whether you were optimizing it for reading or for writing?
Wouldn't it be better to just say we should follow whatever creates nice, clean interfaces but allows the developer access to internals as needed for debugging purposes? The problem I have with the principle of least knowledge (the Law of Demeter) is that it is used to make objects opaque. I think that's what causes the biggest backlash.
I mean the whole point is to create clean interfaces, right?
The law of least knowledge is interesting though, provided it is not an excuse for opacity. Why should my program have to know beforehand what parameters a stored procedure takes? Why not discover them at run-time and map in properties or other variables?