This site and its posts stem from my realisation that a significant portion of my time is spent learning solutions to accomplish tasks, swiftly moving on to the next problem, and subsequently forgetting the necessary steps to solve those previous ones.

Frequently, I’ve been engrossed in personal projects for days, weeks, or even months, many of which remain unfinished or unpublished. My development machine and GitHub are littered with dozens of incomplete projects. Some of these projects serve as mere learning exercises, allowing me to experiment with a language or a new framework. They can be considered “throwaway” work.

Instead of simply forgetting what I’ve learned, I should document something about my learning process by writing up the solutions I’ve acquired. This way, I can refer to them later without the risk of forgetting. However, since I didn’t document my learning at the time, I have to relearn what I’ve learned or the rationale behind the solutions. This process often involves searching for similar solutions to common problems.

To address this productivity bottleneck, I need to document the problems and solutions I encounter. By doing so, I hope to enhance my overall productivity. At the very least, it will serve as a valuable reflection tool.

Writing privately may be quick and easy, but it could easily be lost, deleted, or corrupted by disk failure. Alternatively, I could post everything privately to GitHub, but writing something public requires time, effort, and more attention to the detail. It’s too easy to write excessively detailed or lengthy content that can quickly become neglected and unmaintained. My goal is to keep it simple, concise, and easy to read. I suspect that mastering this ambition will take time and practice.