You'll be a junior forever if you don't learn

Source: Dev.to

The Issue

You’ll always remain at a junior level if you treat “it works” as an excuse for bad code.

When a more experienced developer points out problems, it isn’t about finding faults—it’s about saving the product.

The Codebase

I recently reviewed a codebase that was a disaster: thousands of lines crammed into two files, zero structure, essentially a “big ball of mud.”

I took the following steps:

• Segregated the code into logical groups.
• Introduced a folder hierarchy.
• Analyzed imports, logic, and functions.
• Refactored the project into modular components.

The Feedback

“This wasn’t necessary. The original code worked.”
“He just wants to make us look wrong.”
“If you do your job well, mine takes me 10 minutes instead of hours.”
“There’s always something to ‘fix’ with him. Why change it if it runs?”

Why Modularity Matters

Breaking code into modules isn’t about ego; it reduces the cognitive load for anyone who has to read or maintain it later.

If you view modularity as optional or merely an opinion, you haven’t mastered simplicity—you’ve mastered laziness and mediocrity.

Until you appreciate why structured code is enforced, you aren’t ready for the next level.

Question for developers

Does “it works” ever justify a 2,000‑line file?