3 ms·
>"In order of importance: 1. TDD 2. OO-design 3. Increase Rails mastery 4. Algorithm basics (refresher on different sorts, etc.) 5. Learn the basics of one JS M
by phantom_oracle 13y ago
>"In order of importance: 1. TDD 2. OO-design 3. Increase Rails mastery 4. Algorithm basics (refresher on different sorts, etc.) 5. Learn the basics of one JS MVC framework (leaning toward Angular)."
1-4 are all related. You can learn them all by building something (as someone has mentioned). The problem with saying "learn by building" is how? Nobody ever explains how.
This is how: Learn from whatever resource you learn best (like a cookbook-style tutorial, or a textbook or a video) and then take that knowledge and apply it to the bigger project. If you have your own "how", then go with that.
As for 5, avoid the JS-frameworks for now. Dabble with them, but be flexible enough to try more than 1 out. They're all pretty much in their "hipster" lifespan, so wait until the hipsters move on and then consider picking up one of those frameworks (unless you are a hipster yourself).
- franl 13y agoHaha, no framework hipster here. I feel like people force the use of JS frameworks on projects that don't really need them. So along the lines of what you said, dabble with a few, and when you recognize a project that could benefit from one, dig in. Thanks for the "how"!