About six months ago I put together nevermonetize.com, a single page jekyll application with a couple of paragraphs communicating a simple idea – not pursuing an application or website for monetary gains. At first, I truly thought I would be the only one to use it, but then I began to notice people linking to from around the web. This has created its own challenges, as that text I put together in just a few minutes one night now has to stay consistent. Perhaps there is some beauty in something so hasty becoming solidified – it prevents over-engineering the concept. Some things in life just aren’t about money.

In a world in which things are being removed from the web, it can be amazing to have your own personal collection of gems. Read-it-later apps seek to be the solution, allowing you to save webpages to a location that will be persistent even if the original webpage is removed. There are a bunch of these applications, including pocket, ArchiveBox, and omnivore (which I have written about quite a bit on this blog). This week I discovered Readdeck which may be the perfect solution for those that love the open-source nature of omnivore, but are looking for something much more lightweight.

I had always imagined that email would be hard work. Many VPS providers block outgoing email to help prevent spam, and I was never inclined to setup a gmail for smtp. Instead, I wanted a dedicated email domain that would act like a bot that links up various services and helps me stay on top of notifications. Turns out, it was pretty straightforward, and one day in, seems to be functioning as intended.

There are a ton of videos, articles, even full courses about how to configure the best note taking system. I’ve been through many of them, from Obsidian, to Logseq, to Obsidian again, and then finally resting on mdbook and vimwiki, which have now stood the test of time. If I could go back and give myself some advice, it would be to think about the note taking problem in the reverse direction. Instead of building a system and then modifying your behaviour to match it, start with how you actually use notes, and make a system that meets that need. In this post, I’ll go over some of the key considerations in building such a system, and which ones I think actually matter and which didn’t end up making an iota of a difference after having gone through so much change.

Going backpacking is a surreal experience. There are few moments in modern life where we bundle up everything we think we may need in a single pack and then wander off into the unknown. Before departure, we have plenty of time to check (and double check) our packing list in the comfort of our homes. Once we are out in the wilderness however, all bets are off, you either have a working system or you have a problem.

I have had a mixed relationship with task management software over the years. Sometimes it seems to jive and I am excited to add tasks into it, and other times I leave it to slowly decay until I notice the subscription bill and cancel. One piece of software that I keep coming back to is Vikunja, which is completely open-source and can be either self-hosted, or you can use the hosted option and have it all taken care of for you on Vikunja cloud. Here, I will go over a super easy way to setup vikunja on a debian vps, and then use the vja command line tool to manage tasks from the command line. On mobile, you can either use the Vikunja web app, or tasks.org which will sync through Caldav.

Sometimes it is the small things in life that makes the greatest difference. I’ve had the Casio AE-1500WH-1AVDF for half a year now, and it is easily one of the best purchases I made in 2023. After having a smartwatch for many years, the freedom of not having to worry about charging my watch has been fantastic, and I don’t stress about minor scruffs and bumps. The watch is lightweight and comfortable, and I can use the stopwatch feature while working out. If you are looking for an affordable and easily readable watch, this one would fit the bill. Simple as that.

Online certifications, training courses, or other learning resources can be a mixed bag. It’s unclear how much employers value them, and it can also feel overwhelming trying to retain all of the information presented. When I was doing datacamp after my day job each day, I often felt like I was trying to get to the finish line as quickly as possible, rather than actually focusing on the process of learning. After three years of doing coding practice/learning on the side, I have been reflecting on why I learned so much more with exercism than datacamp.

We consume and generate, a lot of information per day. With more people using the internet and generating data around the world, there will be even more communication: more emails sent, more articles written, and more data to store and recall. During the period 2011 through 2021, the percentage of individuals worldwide using the internet almost doubled, from 31.2% to 59.6% [1]. People are joining the interconnected infrastructure of the modern web at a blistering pace, and yet there are still billions more that remain unconnected. When they too join the global network, we can expect even more ideas to join the chorus.

When I first began migrating repositories from GitHub to Codeberg, the first thing I noticed was that vercel does not support codeberg as a git integration. I like vercel for a lot of reasons, but most of all the ability to preview a build of the site without deploying it to production. Additionally, if something does go seriously wrong, I can always rollback to a previous deployment that was working while I troubleshoot the cause. Using the command line tool for vercel I was able to still deploy just fine but I risked the codebase getting out of sync with the deployments.