11–18 of 18 posts
It's interesting that Node.js is mentioned quite a bit but php or python aren't mentioned at all. Node is a great and powerful tool, but is not the only tool in the tool shed.
what's with all these resources lately that are just a bunch of links? what value are you adding? you realize we have search engines now right? we don't need directories.
Generally it's that all the resources are located in one place, and hopefully someone has actually looked at the links and decided they're of sufficient quality to include in the list. Having one place to look makes it easier for someone to read through things, rather than having to search and evaluate articles and resources themselves (especially as a new learner).
What the idea behind of that? Are you using all this tools, services or whatever? And how do you manage to stay up to date on such a wide area of stuff?
Earlier quoted context omitted.
Generally it's that all the resources are located in one place, and hopefully someone has actually looked at the links and decided they're of sufficient quality to include in the list. Having one place to look makes it easier for someone to read through things, rather than having to search and evaluate articles and resources themselves (especially as a new learner).
I agree with this, that the added value of lists like these is that it's "curated" - a person collected these links over time, gathered from various sources including search results, while filtering for quality subjectively.
It's still very much a "curated" list, it's just that I've done a _lot_ of curation :)
> This document originated from a bunch of most commonly used links and learning resources I sent to every new web developer on our full-stack web development team. What the idea behind of that? Are you using all this tools, services or whatever? And how do you manage to stay up to date on such a wide area of stuff?
> @acemarke your react-redux-links repo is a godsend. how do you keep up with all the articles that the community puts out?
My reply:
> Wayyyyyy too much time spent reading, bookmarking, and organizing :) The "to add" queue has been bouncing between 100-200 items lately. Comments like yours definitely encourage me to keep up with it, though :) As I've said, 1-man project, would love help, but don't expect it.
what's with all these resources lately that are just a bunch of links? what value are you adding? you realize we have search engines now right? we don't need directories.
As a beginner, stuff like this is more overwhelming than useful. It would be more valuable if it instead clustered resources by what to start with, and maybe a timeline (i.e. "Week one, read these 10 articles"). It's just grouped by topic, rather than "what to read first."
On that note, I can recommend the "GrabSE Front End Guide" at https://github.com/grab/front-end-guide , based on Sacha Greif's "A Study Plan to Cure Javascript Fatigue" article at https://medium.freecodecamp.com/a-study-plan-to-cure-javascr... . It has exactly that ordered list of concepts and links with timelines that you're looking for. I also have a more specifically-targeted list of links for React, Redux, and re…