3 Things I Learned From @dan_abramov That Can Help You To Cure Your Imposter Syndrome And Save You From Wrong Coding Decisions

↓

1. Clean code is not a goal

I remember myself trapped into “abstraction monkey” mindset

It's a phenomenon when you become a “clean code adept” and start seeing code that can be replaced by abstractions everywhere

Because why not?

Lots of loosely connected & independent components sound like heaven on earth

Maybe, but only in theory

In practice, it doesn’t work (tried it 3 times and miserably failed to develop & maintain a codebase with tons of abstractions)

Dan:

“Clean code is not a goal. It’s an attempt to make some sense out of the immense complexity of systems we’re dealing with. It’s a defense mechanism when you’re not yet sure how a change would affect the codebase but you need guidance in a sea of unknowns.”

Dan’s article that can save you from wrong coding decisions: https://overreacted.io/goodbye-clean-code/

2. It’s okay to have knowledge gaps

Experienced developers might look like rockstars that can play guitar, drums and sing like Freddie Mercury

But in reality, they often know how to do only one thing very well

Dan:

“Even your favorite developers may not know many things that you know. I’m aware of my knowledge gaps (at least, some of them). I can fill them in later if I become curious or if I need them for a project.”

Dan’s article about his knowledge gaps that can cure your imposter syndrome: https://overreacted.io/things-i-dont-know-as-of-2018/

3. Redux

That's it, I hope you'll find this thread useful

Cheers, Nick