I find this quite interesting because it deviates from what I thought Hemingway's Trick would have been: be a ruthless bastard.
The real Hemingway Trick definitely has its benefits because it lets your algorithm/design/idea develop in your head over time. Brute force coding, even if it works, can lead to sloppy and less efficient code. This leads to an important question: at what point does one trade "beast mode" for rest?
I read an article on HN about how the difference between great and mediocre musicians is the amount of time spent on focused practicing. Total hours mean nothing, only the amount of time spent on meaningful practice matters.
With this being said, it's important to develop a plan of action, and then stay incredibly focused on that for a few short hours. Once that roadblock is hit hit, take a break, let your brain do some processing, and then go back to a focused hack a little later and walk away with substantial progress.
I find this quite interesting because it deviates from what I thought Hemingway's Trick would have been: be a ruthless bastard.
The real Hemingway Trick definitely has its benefits because it lets your algorithm/design/idea develop in your head over time. Brute force coding, even if it works, can lead to sloppy and less efficient code. This leads to an important question: at what point does one trade "beast mode" for rest?
I read an article on HN about how the difference between great and mediocre musicians is the amount of time spent on focused practicing. Total hours mean nothing, only the amount of time spent on meaningful practice matters.
With this being said, it's important to develop a plan of action, and then stay incredibly focused on that for a few short hours. Once that roadblock is hit hit, take a break, let your brain do some processing, and then go back to a focused hack a little later and walk away with substantial progress.