Developer discovers Go project file with complexity score of 524, warns against delaying code quality analysis

A developer building a VibeCode project in Go ran a complexity analysis and found one file with a complexity score of 524

An LLM initially flagged files with complexity scores above 20 as concerning, but discovered extreme outliers in the codebase

The developer humorously compared the high-complexity code to a 'geological event,' emphasizing how badly the code had deteriorated

Post highlights the importance of running linters and complexity analysis early in project development rather than waiting until later stages