before we begin too long to really be able to see the effects of experiments with programming this is not the caseyou can write piece of code and then run it for instant feedback this allows you to course correct and ultimately reach an acceptable solution if you go one step further and write solid tests for your codeyou get even more feedbackand you are able to arrive at the solution much more quickly than if you had to test the process manually each time you made change another trick to help you learn from the process more rapidly is to make prediction as to what the outcome of the block of code you want to write will be make note as to why you expect this specific outcome now write the code and check the result against the expected result if it does not match uptry to explain why this is the case and how you would verify your explanation with another block of code thentest that keep doing it until you have attained mastery you will find yourself getting feedback on different levelsand each has its own merit level one is simply whether the solution works or not nextyou might begin considering questions such as "how easy was the solution to implement?or "is this solution good fit for the problem?lateryou might seek out external feedbackwhich can take the form of simple code reviewworking on projectsor discussing solutions with like-minded people stretch yourself what are the things that you shy away fromthese are the areas of programming that cause you slight discomfort it might be reading from file on disk or connecting to remote api it makes no difference if it is some graphical library or machine-learning setupwe all have some part of the craft that just does not sit comfortably these are usually the things that you most need to work on here are the areas that will stretch you and force you to face your own weaknesses and blind spots the only way to get over this discomfort is to dive deep into itto use that tool so many times and in so many ways that you begin to get feel for it you must get so comfortable with it that you no longer have to look up that file open protocol on stack overflowin factyou have written better one you jump rope with the gui and suck data out of database with one hand tied behind your back there is no shortcut to this level of masterythe only way is through the mountain that is why so few people become true masters getting there means spending lot of time on the things that are not easythat do not make you feel like you are invincible you spend so much time in these ego-destroying zones that very few masters of any craft have lot of arrogance left in them