At some unknown point, I started perusing most of the comments for each of the lectures in this course (sometimes learning just as much from the conversations as from the lectures themselves, which is brilliant! ), and often enough when I felt I had something to add, someone had already mentioned it, so they would get a like, and I would move on There’s something I’ve not seen spoken of though (I may have missed it, so apologies if this is redundant), and wanted to give it a respectful nod, and that topic is “Refactoring”.
Every chance I get, I try to tackle as much of each challenge as I can (sometimes even managing to complete a future challenge before it’s mentioned flex) but I’ve always found myself slightly paranoid about writing code that’s “optimized” or even just written “the right way,” and those ideas (which may have sprouted from listening to too many elitists on a certain online overflowing stack that shall remain nameless ) have held me back from being bold in really digging into C#. The idea of writing code that you never have to touch ever again is lovely, but after watching the lectures to this point, I know it’s a fantasy. In short, thank-you for showing us (me) that refactoring is absolutely A-OK; that I can write code, come back a bit later, feel contented in my previous efforts, and then tear it all to pieces, making any number of alterations without feeling any guilt, sense of inadequacy, or personal failure. For a stark-raving perfectionist like myself, this means a lot. Cheers!