4 ms·
Ha! Joke's on them. I type it out so it makes it look like I'm doing more work. (But in all seriousness, I normally do type it out, so it forces me to rememb
by kemiller2002 6y ago
Ha! Joke's on them. I type it out so it makes it look like I'm doing more work. (But in all seriousness, I normally do type it out, so it forces me to remember what I'm using better.)
- mhb 6y agoThe learning works better if you cut and paste it twice, forget to change something and then discover it after a few hours of debugging.
- p4l4g4 6y agoThis, yes! Not necessarily the copy/paste part, but definitely the debug part! I generally like deeper debug sessions, preferably without too much pressure. Getting deep understanding for a problem and figuring out a solution were the most valuable learning experiences in my career. The satisfaction you get from finding a solution to a hard problem, makes them more memorable. Even if the lessons learned afterward are not spectacular, then at least you got a chance to sharpen the tools in your belt to pin point problems as they occur!
- niix 6y agoSame, I've always done this for anything like this (i.e. tutorials), just to make sure what I'm learning sticks with me a bit more.
- kemiller 6y agoWell, hello, Junior. That's thinking!
- kemiller2002 6y agoHa! Nice username :)
- TameAntelope 6y agoRight? Who is literally copy/pasting, that seems dangerous. I'd describe it as learning the concept/tactic/technique from the SO answer, and if me then implementing that concept/tactic/technique in my own code just so happens to look the same as the provided example, that's fine. Frequently it doesn't, either!