aposd-vs-clean-code

The pendulum has swung too far in the direction of class, function, cyclomatic complexity (and here, CRAP) and similar idiotic metrics. This reminds me of a talk Sandi Metz did called "All the Little Things" where she covers the Gilded Rose kata. In the talk, she reworks her solution until there's almost nothing left showing the essence of the problem being solved. The cyclomatic complexity metric is touted at each step as a proxy for goodness of design and removal of complexity. However, a weakness of the measure itself is that it doesn't account for the control flow indirection that happens through OO method dispatch itself. At the same time, Kevlin Henney's talk called "Gilding the Rose" takes the same kata and arrives at a far more sane solution he works up to and reveals at the end. Short functions used to be hot. Uncle Bob used to p

For some actual code and comparison of principles behind Clean Code see: https://github.com/johnousterhout/aposd-vs-clean-code

Yes, but the problem is the advocate for it, and the text on it arrived at the correct conclusion using a bad implementation/set of standards. c.f., https://github.com/johnousterhout/aposd-vs-clean-code and instead of cleaning your code, design it: https://www.goodreads.com/en/book/show/39996759-a-philosophy...

New pasta paradigm unlocked. Sounds like a case of premature optimization, leaning too hard on DRY. Am reminded also of a discussion of software engineering between John Ousterhout (of whom I'm a big fan) and Robert Martin[0][1]. [0] https://github.com/johnousterhout/aposd-vs-clean-code [1] https://youtu.be/3Vlk6hCWBw0

For an example of what happens when he runs into a real programmer see: https://github.com/johnousterhout/aposd-vs-clean-code _A Philosophy of Software Design_ is an amazing and under-rated book: https://www.goodreads.com/en/book/show/39996759-a-philosophy... and one which I highly recommend and which markedly improved my code --- the other book made me question my boss's competence when it showed up on his desk, but then it was placed under a monitor as a riser which reflected his opinion of it....

https://github.com/johnousterhout/aposd-vs-clean-code is a great find from that list. Thanks!

The world would be a better place if _Philosophy of Software Design_ would replace all mentions of the second book. https://github.com/johnousterhout/aposd-vs-clean-code

This is yet another very good critique, but it's long past time that we stop paying attention to Uncle Bob. Not only are his ideas about how to write software patently bad, but he is willfully obtuse when asked to provide nuance or discuss trade-offs. John Ousterhout's dialog with him, published as "A Philosophy of Software Design vs Clean Code" gave him every opportunity to think critically about his own suggestions and he just doubles down. https://github.com/johnousterhout/aposd-vs-clean-code/blob/m... He's just trolling us at this point.

A Philosophy of Software Design by John Ousterhout is often recommended, and is very good. There was an interesting debate between John and Uncle Bob on their differences in style recently[1], with a related HN discussion[2]. [1] https://github.com/johnousterhout/aposd-vs-clean-code/blob/m... [2] https://news.ycombinator.com/item?id=43166362

Thanks for taking one for the team. I had zero expectations for Clean Code second edition after reading Uncle Bob's dialogs with John Ousterhout. I thought Ousterhout bent over backwards to give Uncle Bob the benefit of the doubt and discuss the tradeoffs and Bob just dug in on his bizarre dogmatic approaches. https://github.com/johnousterhout/aposd-vs-clean-code/blob/m...