4 ms·
I don't have formal CS knowledge so everything I say might be wrong. I came to realise that you only gain grounding by working with a stack/framework/set-of-to
by atmosx 11y ago
I don't have formal CS knowledge so everything I say might be wrong.
I came to realise that you only gain grounding by working with a stack/framework/set-of-tools every day. Everything else (reading a book, etc.) is just scratching the surface.
Since you can't know everything about everything, I'd say that the best way to learn is to build something. But it's one thing to build your own CRUD test-app to learn Rails and another thing to design an app that will need to stash 20 million entries per day in a DB. The choice of the DB becomes, suddenly, a complex matter. Same if you need to handle 100.000 req/s ... You can't really learn these things on your own.
The best thing IMHO to get good grounding is to never stop learning.
- yolesaber 11y agoYou're not necessarily wrong, but missing the point. He wants to learn about CS fundamentals so he can discover what powers the framework / stack, not get a grounding in the stack's capabilities itself.
- atmosx 11y agoAnd what CS fundamentals do you need to discover Rails, Node, React or django?
- yolesaber 11y agoOf course, you don't need to know any CS fundamentals to "discover" them and start using them. But if you want to learn the CS behind them and how they operate on a theoretical level, I'd say start with the algorithms that power networking and the internet and then progress up to data structures used by these frameworks to deal with databases, caching etc. I'm not too familiar with any of them except for django so I can't get into that much detail.