It's easy to add new things that fit the abstraction
What and how isn't enough.
Over-abstraction could be avoided.
What if we need to exchange X with Y?
That could be better than complexity.
Except you're creating a library or a framework
Simple isn't easy.
They know the stuff!
And don't believe me as well ;)
There are problems:
10.000 hours could make one a superhero.
But there will be mistakes still.
Ask, learn, understand.
Frameworks are tools.
But they're often treated like authority sources.
Framework won't always save your ass.
Do what works for you and your team. Learn best practices to adapt for your use cases. Do not blindly copy them.
Rely on facts, not opinions
Often it's hard...
Junior stock exchange worker failed and lost $5M. He thought he would be fired...
Next day he was not and asked why...
The answer was...
We've just invested $5M in your eduction. Why should we fire you?
How to fix it, not who's to blame.
They work at the company level.
Sometimes punishment is the best possible solution.
Colleagues or community
What colleagues would say?
Someone may not like it. I'd better keep it to myself.
I'd use all the cool patterns in my next lib cause people like it.
There was a tale in ancient greece...
Nothing changed since then :)
Confidence comes with experience!
But where to get it?
Try all the cool new things!
* Not at production server
Learn from authorities.
But dig down to facts!
Share your stuff.