As I begin to clock in certifications from Anthropic on the Claude system, it dawned upon me that the value of knowledge is next to worthless these days, so to stay relevant, or at least to be able to relate to my Gen Z students, I have to go through what they will eventually go through when they hit the work force, which I think is 10x worse than looking for a job during my time. In the early 2000s, most engineers secured a job by their final year of schooling and could enjoy working on their final-year project, with a secure job waiting for them after graduation.
For this current batch of graduates, they need to contend with the uselessness of knowledge and possibly the deteriorating power of signalling conveyed by degree certificates. To remain relevant, they need skills, but to prove that these skills matter, they will need a portfolio of products that need to display to a potential employer.
So I've decided to join in the fun.
My first practical product using Claude Code in VS Code is a simple To Do List, just to get some initial momentum and make me more efficient on a daily basis, but I want it to be more powerful than the usual To Do lists out there, so I decided to make the application a Bullet Journal.
But there are three complications :
- I no longer know how to code Windows applications in Python. The last time I did that seriously was in C++ using Microsoft Foundation Classes.
- I don't even understand the Bullet Journaling approach, as the book is quite thick and I've not read it yet. I know it's popular, and some hipster executives love it. But I prefer to pick up new AI programming skills.
- I don't even have the technical skills to write software specifications because I was more of an IT Governance professional.
So here's my strategy:
I explained the context to Claude and got Claude to create a first draft of a specification, mentioning bullet journal, Python as the only language I know, and the final product as a Windows executable.
It was able to generate a specification which I can read and amend slightly to my taste.
I got Claude Code to generate my program before I took my son to school, and when I came back, my application was ready to be compiled and run.
And it ran, so I suddenly have a private electronic bullet journaling app that tracks daily tasks and lets me strike them off as they get done. My application is actually chock-full of functionality, and I have no idea what it can do in totality, given how little I know about Bullet Journaling.
I've been using the application for a couple of days, and it has really supercharged my productivity. I can list my priorities early in the morning and slowly strike off each task as I go through the day, freeing up my evenings to contemplate how to improve the application.
On day 2, I suddenly felt that the program was kinda boring and monotonous, and I wanted every completed task to provide a dopamine rush, so I incorporated nice sounds and confetti into the app, and it made me even more productive as completing a task gave a satisfying "ping". Making this modification was a painless task.
Then I had a crazy idea.
Why not make the application comply with the "Getting Things Done" philosophy as well, a kind of productivity system that is over 20 years old, which I tried to understand but never had the willpower to turn into a habit?
Fortunately, AI was able to summarise the GTD philosophy, allowing me to consciously get Claude to modify my software to delegate tasks or KIV them.
And so my Frankenstein application now combines two systems: a Bullet Journal and the GTD philosophy.
You should now be able to see where I am going here.
For every productivity philosophy or system I learn, I can use it to add features to my program. Over time, the more I use my program, the more bugs I encounter, and the more bugs I can get Claude to fix.
I think this might be an entirely new way of consuming software. We just dream of what kind of software we want, and an AI builds it for us on the spot. They won't get it right 100% of the time, but you can recode and recompile the software. Over time, the application becomes seasoned and customised for the individual user.
Because I'm focused on personal efficiency, every new system can inspire slight improvements in my application.
My next objective is to incorporate an Eisenhower matrix into each task, labelling it as urgent or important.