My old boss in Boston told me my code was 'too clever' back in 2019.

I was trying to make a simple image tagger way too complex. Now I start every new model by asking 'what's the dumbest way to solve this first?' Anyone else get that kind of blunt advice that stuck?

3 comments

3 Comments

noahs371mo ago

That "dumbest way first" idea is solid. I'd just say it's not about being dumb, it's about being clear. Clever code breaks when you're not the one fixing it. Starting simple means you can actually explain it to someone else later.

elliot_mason621mo ago

Ever notice how this applies to more than just code? I've seen people write emails that are so fancy you need a dictionary to understand them. @noahs37 is right, it's about clarity. The best instructions, recipes, or even directions to your house are the simple ones. When you start with the clear, "dumb" way, you build a foundation anyone can follow. Getting clever too early just leaves everyone else lost.

brian_taylor151mo ago

Right? It's like those furniture assembly guides. The good ones have pictures so clear you can't mess up. The bad ones try to be "efficient" with words and you're left with three extra screws. @noahs37 has it, it's about making sure the next person gets it. My buddy tried to give me driving directions using only landmarks that don't exist anymore. Just tell me to turn left at the big red barn, not "where the old Johnson place used to be.