Comments by "" (@retagainez) on "" video.

  1. That's what I typically understood Clean Code to mean in the first place. Is there something that states otherwise? That clean code is meant to prevent bugs instead of just having well-structured code? Isn't creating your own well-structured set of principles in effect your own interpretation of Clean Code ? The opening argument that Clean Code is about finding out about "the places that changes need to be made now" is something more like what Working Effectively with Legacy Code discusses. Every other point after that where you explain how you don't read the entire file or "read top to bottom" consistently lines up with Clean Code principles, so it's odd and slightly hypocritical to claim to be against one thing but still advocate for similar points. Most of what your code example shows about the so-called 'includer' shows a particularly erroneous example to what Clean Code might mean. I personally think the example might be coupled to the setup/teardown of the fitnesse library. It took me about a minute to arrive at that just from reading function names though, and the odd one-liner here or there. So i think the code itself is clean and clear, but perhaps the naming and practicality of setting up such a test might be lost on people and this is the problem with the example. Otherwise, it's relatively clear. Am I wrong about this? The content appends suggest that I'm more-or-less on the right track. Reading bottom-up is when you have no test suite. It is completely fair to say that companies end up in awful situations without test suites, so all that's left is to read bottom-up. This is what the Working Effectively with Legacy Code book is about though. I think the strength of Clean Code or agile is that it is vague. Clean Code in particular has always pushed the need to develop an intuition in my mind which vaguely aligns with various principles, but doesn't contradict them. If you have a code smell or something you generally dislike, Clean Code is generally supposed to help you recall the typical things you might check off and analyze to solve the problem.
    2