One thing that is often overlooked is that time spent in practice doesn't necessarily make you better in the way you want.
If you practice doing things incorrectly, you get better at being wrong.
You need to make sure you practice getting things right.
In programming, I often see people get attached to models of things which mostly work most of the time, but are more complex than need be, and fundamentally incorrect, so as problems are encountered they end up making the model even more complex and ever more subtly incorrect.
Attachment to practicing understanding things incorrectly is the greatest stumbling block for programmers in my experience.
When someone tells me that they know C, I ask one question.
charc[3];// what is the type of c?
The vast majority give the wrong answer, because they have been handicapped with a defective model of how C works.
that is definitely right, one of the biggest sentiment in my article is implicitly about correct practice. What correct means also differs from the individual. That is why it is difficult for people to improve. They incorrectly identify where they should improve on and thus are stepping in the same spot no matter how much time spent.
If you practice doing things incorrectly, you get better at being wrong.
Where is the bookmark/highlight quote feature on dev.to
I see this mistake being made a lot. The most (in)visible form is "experience in years". Just because somebody has 10 years experience in a field doesn't mean they are good. They could have been doing the wrong thing for a long time. The experience is "measured" on the scars. That is, mistakes people made and learned from.
People don't learn from success. People don't even know why something was successful, too many variables. Failure is easier to diagnose.
Want to get better? Then get good at failing and analyzing the causes.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One thing that is often overlooked is that time spent in practice doesn't necessarily make you better in the way you want.
If you practice doing things incorrectly, you get better at being wrong.
You need to make sure you practice getting things right.
In programming, I often see people get attached to models of things which mostly work most of the time, but are more complex than need be, and fundamentally incorrect, so as problems are encountered they end up making the model even more complex and ever more subtly incorrect.
Attachment to practicing understanding things incorrectly is the greatest stumbling block for programmers in my experience.
When someone tells me that they know C, I ask one question.
The vast majority give the wrong answer, because they have been handicapped with a defective model of how C works.
that is definitely right, one of the biggest sentiment in my article is implicitly about correct practice. What correct means also differs from the individual. That is why it is difficult for people to improve. They incorrectly identify where they should improve on and thus are stepping in the same spot no matter how much time spent.
Where is the bookmark/highlight quote feature on dev.to
I see this mistake being made a lot. The most (in)visible form is "experience in years". Just because somebody has 10 years experience in a field doesn't mean they are good. They could have been doing the wrong thing for a long time. The experience is "measured" on the scars. That is, mistakes people made and learned from.
People don't learn from success. People don't even know why something was successful, too many variables. Failure is easier to diagnose.
Want to get better? Then get good at failing and analyzing the causes.