Introduction: The Code Smell Dilemma

A developer’s journey into compiler design took an unexpected turn when their Go-based project, krabbascript , faced harsh criticism. The feedback? “Your codebase is awful.” This single statement triggered a cascade of questions: Is the criticism valid? What specific issues exist? How can the code be improved? The investigation begins by dissecting the developer’s situation, the feedback loop, and the systemic gaps that may have led to this point.

The code development process for krabbascript likely involved iterative design, implementation, and testing phases. However, the absence of a structured code review process —a critical mechanism for catching issues early—may have allowed problems to persist. Without peer feedback, the developer relied solely on their own judgment, which, in the absence of clear code quality standards , left room for subjective interpretation.…