I like to organize my blog around Obsidian which is a Markdown-based note taking application with emphasis on internal linking and note discovery. I want to manage my blog posts as tasks, so I've implemented a custom Kanban-like workflow with Obsidian. In this post I will share my setup, and the alternatives that I've looked at.
So you started a blog, wrote a few articles, configured Google Analytics, and now find yourself constantly checking if anyone is visiting your site? I know how you feel, I've felt the urge to check my stats basically every day since my blog went online. In this post I'm going to share how I changed my mindset to overcome this huge time sink.
Services like Roam Research or Notion have made note taking really trendy recently. The problem with hosted services is that you don't own the platform and the content there, so what do you do if they go out of service or increase their prices?
Python is a great language for writing command line scripts. When you need to run long running processes it is polite to indicate the overall progress to your user. You don't want the user to think that your script has hanged and terminate the execution after a minute. Luckily, adding a progress indicator is really easy!
Historically, the Python syntax hasn't had a switch-case statement. In 2006 Guido van Rossum, the original author of Python, proposed different alternatives for the switch-case syntax in PEP 3103 but they all seemed to have some problems and the idea didn't gain enough popular support. The proposal was therefore rejected. Python version 3.10 changes this.
I've been investigating different methods of personal note management, and I've come to the conclusion that I want to keep my notes as plaintext Markdown files for the best future compatibility. One of the tools that I've been trying out is Obsidian. At some point I will probably write a comparison of the different software I've been trying out, but this post is actually about getting into the flow state of writing.
Normally when you create a Git tag you should just let it be and not alter the history after the fact. But if you really need to move a tag forward how can it be done?
When you run temporary workloads you may not want to leave old machine instances lingering behind. Preemptible VM instances let you run at a significantly discounted price but they are shut down automatically after 24 hours, or earlier if Google needs those resources. The instances will still remain there in shut down state and they can still be turned back on later. What if you wanted to delete the machines automatically when you're done with them?