AngularJS Learning Resources Update

Last year while learning AngularJS, I started compiling links to Angular blog posts that I liked, by adding them to a simple text file. After a couple of weeks of gathering links, I thought “hey, maybe other devs new to Angular would find this useful, too”. So I created a Github account, and created a project called AngularJS Learning Resources (which you can find here). I didn’t know anything about Github at the time, so the project wasn’t (and still isn’t) fancy. After creating the project, I decided to mention it on Hacker News, and I was rather surprised at the results. It ended up making it into the top 3 spots on the front page, and stayed there for almost a full day. Within a week, I believe it had 3000 followers, and is over 6000 now. I hope folks have found it useful, and I truly appreciate all the pull requests from others to add new links. Anytime you come across a nice Angular article, feel free to submit a pull request (or comment) to get it added.

Now that the list is about 15 months old now, it needs some attention. At this point, there are approximately 550 links in the list, and not all of them belong any more. I need to devote some serious time to going through all of the links, and “trimming the fat”. And I would like to reorganize the sections a bit. But first, the goal is to remove some links.

If anyone would like to help, I would certainly appreciate it. Reading the content of 550+ links is quite a job. For this first round, if you want to help, I would like to concentrate on removing links that meet one of more of the following criteria:

  1. The post is out of date (though just being old doesn’t matter, if the content is still relevant. But I would think most links over 12 months old are dated)
  2. The content is ‘fluff” and can easily be found in other places (like answers on Stack Overflow). In other words, if the content is high level and isn’t very useful, or doesn’t offer anything beyond the Angular documentation, it should be removed. That way the list isn’t cluttered with articles that don’t offer much in the way of  Angular teaching or insight.
  3. The content suggests something that goes against current Angular best practices.
  4. Similar to #3 above…the article uses bad JavaScript coding in general, or otherwise could lead developers new to Angular down the wrong path.

To prevent multiple people from editing the same sections, I will start a thread in Github repo for the project. If you would like to help, just leave a comment here and let everyone know what section you would like to clean up.

If you have other suggestions for the repo, feel free to comment here in this post.

Thanks in advance to anyone that wants to help out!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s