RUBBERDUCK

Rubberduck is about learning, and paying forward: the project co-founder wrote their very first lines of C# for Rubberduck, and several contributors later did the same. Core contributors are always happy to guide new ducklings toward their first pull request!... Rubberduck builds its own internal representation of the code, and then proceeds to analyze it. Each individual inspection can easily be disabled, or configured to issue inspection results at various severity levels ranging from `Hint` to `Error`. Unless configured otherwise, Rubberduck automatically runs inspections after a parser/resolver cycle completes (regardless of whether the toolwindow is displayed or not), so inspection results are always ready to review when you are. For the best experience, it would be recommended to **first try Rubberduck with an empty project**, add a new module, and write, say, a loop that counts 1 to 10 and outputs to the debug pane - then to parse that and review the inspection results;..