6 ms·
A simple answer to your conundrum could be how he manages his cadence and deals with pressure. Programming isn't especially difficult in my opinion. In many cas
by rebelos 5y ago
A simple answer to your conundrum could be how he manages his cadence and deals with pressure. Programming isn't especially difficult in my opinion. In many cases, sheer throughput seems to have a lot more to do with success than raw talent. Someone who was previously a chef might have a huge advantage in this regard, since working in a kitchen is a really demanding occupation. He probably has excellent training in dealing with pressure and time constraints. Perhaps being a programmer is even a relief compared to being a chef!
- tomlockwood 5y agoBefore I was a programmer I worked on an industrial site. > Programming isn't especially difficult in my opinion. Spoken like someone who is a programmer! haha
- Arisaka1 5y agoAside the "programming isn't especially difficult" which I think has more to do with how experienced people are poor evaluators of the required skills to be good in something (akin to gamers saying "git gud" when it comes to Dark Souls games), you have a good realization: The faster you iterate the faster you move. When I was learning simple syntax I used to be afraid, almost allergic, to the idea that the code I'm executing will produce errors. I realized too late that the faster I get to the point of erroring and interpreting the errors thrown the better my progress. To put that in the kitchen perspective, it's the point where you're sampling the food that you're cooking to see if it needs salt, you forgot the onions, or it's boiling too fast.