The Journey So Far I’m building a web app/Chrome extension pair that allows your bookmarks to “decay” (grow old and disappear) over time; the intention is to encourage you to actually read those tabs you have open as opposed to letting them linger until your browser crashes. Now that I’ve completed the MVP for the extension, it’s time to work on the web app! Missed another part of this project series?

The Journey So Far I’m building a web app/chrome extension pair that allows your bookmarks to “decay” (grow old and disappear) over time; the intention is to encourage you to actually read those tabs you have open as opposed to letting them linger until your browser crashes.1 The first step I’m taking on this project is creating a Chrome Extension to easily bookmark pages and save that data locally. Missed another part of this project series?

I’ve been working on a small personal project for a few days now, and I thought I’d start sharing my progress, just to talk about how I work through things. A bit of rubber duck programming for me, a little bit of content for you (uh, and for me). “Bookmark Decay” The working title of a little project I’ve thought about on and off for a couple years. The basic idea is a list of bookmarks that “decay” (IE, disappear) after a certain amount of time.

I have a friend who talks about programming making you feel alternately like a genius and an idiot, and every developer I’ve mentioned this to since laughs and agrees. Years ago he sent me this picture to illustrate his point: We've all been here. Over and over. I think about this a lot when I’m wrestling with a problem, whether it’s a new concept, bug in my code, or whatever. It’s actually a salve to my wounds, because it reminds me that whatever issues I’m having today will probably be gone tomorrow - or even maybe in the next hour.