I am sure it stops a significant portion of people opening them still. I'd really want to take one apart before going through the hassle of buying special tools.
Kinda like how companies makes unsubscribing hard, not impossible.
I feel like this is covered already. Before I start coding I will always draw out diagrams of the components visually, where as the code is the details to make it actually work.
Using box and arrow diagrams for documentation can give you a lot of these benefits without needing to adopt a radically new paradigm.
I think actually teaching people is a great way of getting mastery at something. If you teach people and they get good results you can be confidant you know enough about the subject.
Yes! I’ve heard of the “plus-minus-equal” learning concept. You need someone with more knowledge to learn from (your plus), someone at the same knowledge to work through problems with together (your equal), and then someone to teach (your minus) so that you can be sure you’ve truly mastered the material.
While imposter syndrome might be uncomfortable, I think its generally trait that helps someone become a good developer.
By realizing you don't know everything you are more inclined to continually improve your knowledge.
I think teaching and writing are also good ways of getting over it. Once you explain a concept to people you will know you don't have gaps in your knowledge to arrive at a working understanding.
I think of it as a feeling everyone feels at some point if they care about doing a good job. If you never feel it, you are probably playing it too safe and aren't growing as fast as you could be as a result.
