I'm very disappointed that he starts out with a diagram and "This is what ugly code looks like.", but doesn't follow it up with "This is what beautiful code looks like."
Then again, maybe that part's just in the book this excerpt is trying to sell.
Then again, maybe that part's just in the book this excerpt is trying to sell.
Of course, "beauty" is a hard sell. What you really get with maintaining code with these "beautiful" qualities is massive productivity and choice.
Of course, the prioritization between these three is up in the air.
Also: what does HN recommend for creating such a diagram for my code (say C# and C++ codebases)?
Not that I'm sure it is really an ok measure: I'm a heavy adept of DIY and have a ton of small utility functions which are used all over the place (mainly missing pieces in the STL). This should lead to a whole lot of extra lines in a diagram which might look like spaghetti as well.
* up to a point