3 ms·
Backend web dev for the most part these days. Trying to simultaneously learn a language or system and produce something deployable has been a huge headache for
by throwaway81523 4y ago
Backend web dev for the most part these days. Trying to simultaneously learn a language or system and produce something deployable has been a huge headache for me. I prefer to learn something new by starting at the beginning, with small exercises and study until I'm fluent enough to work on a real project without making bad mistakes from ignorance. The other approach, which everyone seems to expect, seems like madness to me.
If you're a good pianist and you have to learn the violin, I think it's best to start with scales and arpeggios just like any other beginner, except you go faster because your existing knowledge transfers to the new instrument. Trying to make your way through Beethoven's violin concerto starting on your first day with the violin seems to me like a ridiculous approach.
- psalminen 4y agoAfter a moment of scales, learning "twinkle twinkle little star" or similar is the obvious next step, which I think is what the post is asking about.
- throwaway81523 4y agoI see. Maybe some Euler problems? There used to be a good site called rubyquiz.com that had nice exercises that were less math-like, and that (mostly) worked well in multiple languages. Rosetta Code might be another such place. Or just think up your own. There are two issues as I see it. One is to be able to code something that seems to solve your problem. The other is being able to code with reasonable surety that you haven't committed some subtle error that will bite you if you actually deploy the code. You need deeper fluency for the latter than for the former.