3 ms·
I suspect there may be better ways to practice, rather than just doing it more? Some people put effort into memorization of commonly used idioms. Here's anothe
by skybrian 8y ago
I suspect there may be better ways to practice, rather than just doing it more? Some people put effort into memorization of commonly used idioms.
Here's another dubious analogy: when learning music, you do need to practice, but playing a song all the way through a bunch of times is a rather inefficient way to practice it.
- munchbunny 8y agoCreate your own mental frameworks. For example (personal mnemonic to cover my own blind spots) when designing my feature, consider: * Flighting, especially protocol changes, will this change cause clients to be unable to talk to services? * Risk: if this change breaks its service, what else breaks? What is the recovery path? * Security: does this unintentionally relax or circumvent existing security boundaries? How much damage can an abuse of any code that writes/modifies do? This is not a complete list on purpose. I use it to shore up the things I tend to forget to think about.
- megous 8y agoOther way of doing it more, is not just doing the same/similar thing again and again, but writing/reading large amount of very different programs. One day you do web app, other day you write a kernel driver, third day you write a scraping app, fourth day you write a tunel driver to get networking over USB, fifth day you reverse engineer some random piece of HW you have laying around and write alternative firmware for it to teach it new things, and so on. (it may not be days :)) Each of these things will branch out into different areas. You may need to write a text parser. You may need to design a USB protocol to relay packets. You may need to learn a processor architecture, calling convention, assembler mnemonics. Over time you'll gain a lot of knowledge and you may be able to cross-apply plenty of it accross the domain boundaries.
- sinuhe69 8y agoI believe it’s almost identical to other fields: review, revise and reflection is the best way to learn. If someone want to improve his code quality, he should continuously review his code, best together with a “better” programmer. After finding the weak spots of his code, he should try to improve them by himself. To do so, he need to learn from good examples, exploring the reason behind through computer literature and experienced coders. After achieving a better version, he should reflect on his practice, how he might come to the solution himself in the first place, why did he choose the first solution and very soon he will start to recognize certain patterns. Regarding technical expertise, he should find where the challenge lies and start studying and practicing to make the knowledge sticks. He should go out of his comfort zone, challenge his ability and make mistakes. That is the only way to mastery.