I have a habit of accumulating things to read which never actually get read.
To combat this, I went through and actually read everything that I wanted to at some point in time with the goal to open-source the knowledge gained from it.
Usage
I highly suggest using your browser's search box to navigate to where you want to go
Please click through to the original article or project to see it from the source if you find it interesting!
This is very much just a cursory ELI5 of each link mostly to have them all in one place
Let me know if this is helpful 😘
Build Process
This is built using GitHub Pages and Jekyll, though the original lists are in my GitLab Snippets.
It's mainly dev.to links and Medium links, though I have a snippet of more dev.to articles and a ton of GitHub repos to add to it after I do write-ups.
I’m a web developer & data visualizer working at a think tank in D.C. I'm a self-taught dev trying to better my skills. I spend most of my time on the front end of the stack.
Location
Washington, D.C.
Work
Lead Developer at Center for Strategic and International Studies
That is a really great repo! I have the same problem as you said in your opening statement in the README - I've accumulated so many articles that I want to read, but don't ever actually sit and read them. My notes are written in markdown now, I wonder how difficult it would be to write a script to export them into a repo like this so I can access it even when I don't have access to my note-taking app.
Born and raised in Montana. I love drawing and technology. I lost my job in home construction due to the economic downturn. It was then that I realized I loved to code.
In an attempt to break the cycle, I will first look at the length of the article. If I think I can read it in 5 minutes, I read it right away. That's been helping, but I still have a crazy backlog.
I've started keeping a GitHub repo of my bookmarks and notes, though I still need to flesh out the notes some more.
itsasine.xyz/resources/
Notated and organized personal bookmarks, open sourced
Table of Contents
About
Why?
I have a habit of accumulating things to read which never actually get read.
To combat this, I went through and actually read everything that I wanted to at some point in time with the goal to open-source the knowledge gained from it.
Usage
Build Process
This is built using GitHub Pages and Jekyll, though the original lists are in my GitLab Snippets.
It's mainly dev.to links and Medium links, though I have a snippet of more dev.to articles and a ton of GitHub repos to add to it after I do write-ups.
That is a really great repo! I have the same problem as you said in your opening statement in the README - I've accumulated so many articles that I want to read, but don't ever actually sit and read them. My notes are written in markdown now, I wonder how difficult it would be to write a script to export them into a repo like this so I can access it even when I don't have access to my note-taking app.
In an attempt to break the cycle, I will first look at the length of the article. If I think I can read it in 5 minutes, I read it right away. That's been helping, but I still have a crazy backlog.
My main motivation for using Markdown was to use something like Gitlab snippets to have it available all the time on all devices :)
The repo motivated me to get my dev.to Reading List from 140 down to 0, so I recommend it!