For the last few years, Craft has been my main place for personal knowledge management. I have rated it highly for a long time, and I still think it is an excellent tool. It helped me build a proper documentation habit, organise my technical notes, and keep a useful personal knowledge base that I could rely on. But over time, the way I used Craft started to change. I was still using it regularly, but I was using fewer of the features that originally made it so appealing. My notes were becoming more about durable knowledge: technical references, project notes, personal documentation, snippets, workflows, and things I wanted to be able to search, edit, automate, and reuse over time.

I’ve always liked finding useful apps, command line tools, and resources. Some are things I use every day, while others are more situational, but still worth remembering and sharing when the right moment comes up. For a while, I kept that list in Craft as a simple table. That worked well enough at the start. Craft is still where a lot of my knowledge lives, and it is excellent for notes, documents, and personal knowledge management.

I was casually browsing the gallery on my AI Art Hub app, on my iPhone when I noticed something slightly off. Whenever I tapped on an image to enlarge it, the image wasn’t properly centred on screen. It wasn’t a critical issue. Just one of those small UI details that immediately stands out once you notice it. Normally, this would have meant waiting until I was back at my desk with my Mac nearby. Instead, I decided to try fixing it entirely from my phone using Codex inside the ChatGPT iPhone app.

For a long time, my personal website was something I had online, but not something I felt fully in control of. It was hosted with a web hosting company, which worked well enough on the surface. The site loaded, the domain pointed to it, and it did the basic job of giving me a small presence online. But over time, the limitations started to bother me. I did not have the level of control I wanted over the source files. Making changes felt more awkward than it needed to be. I also had limited visibility over useful metrics and the way the site was actually being served. On top of that, I was paying an annual hosting fee for something that had become quite a simple personal site.

When I first started using Codex, I felt completely out of my depth. I remember thinking, “What am I doing? I’m not a developer.” It felt like I was stepping into a world that was built for developers. Sure, there are developer workflows you need to be aware of, but I wasn’t sure if I belonged there. However, coming from the ops side of DevOps, I had some relevant experience which I could use to bring the ideas that I had, to life. I decided to stick at it and work with Codex daily and it has now become a fundamental part of my workflow.