Mar 16–22, 2026
The biggest chunk of my contract work is done, and I also wrapped up my personal app and submitted it for review. It was a surprisingly relaxed week, and that alone made me feel a lot lighter. A few other things also started settling into place, so since spring is here, I bought some freesias I like and kept them at home. I finished one thing, but it also feels like something new is about to begin.
This week, my physical condition was worse than I expected. I kept feeling a sharp, poking sensation in my lower abdomen. I wasn’t exactly exhausted, but it kept bothering me enough to make me feel worn out and irritable anyway. As a result, my work efficiency wasn’t very good. I also had a regular hospital checkup this week, and now I only need to go once every four weeks. The bone has healed to about 95 percent. Physical therapy is done too, and they told me I can just come back if it hurts. Now I just need to recover well until it’s time for the surgery to remove the metal hardware.
I feel like I’m finally starting to get a sense of how I should use AI when programming. I don’t focus well when I have several projects or several kinds of work running in parallel. The context keeps breaking, so it’s easy to lose track of what I was doing, and sometimes AI heads in a different direction and I have to step in and correct it. So I need to delegate work to AI while also checking whether it’s actually doing the right thing, reviewing the output, and confirming that it worked in the direction I intended. That’s why I focus on core work or contract work in the morning and afternoon, and then switch to my personal project in the evening. I’ve also automated repetitive workflows through SKILLS, so when I enter a command, it follows the process I want. Once a week, I review everything and remove any SKILL I no longer need or update the ones I still use. When work moves too fast, I sometimes forget what I’ve done, so I also made SKILL-based workflows for summarizing what I worked on during the week, or for reviewing what I did yesterday and what I need to do today before I start. Because of that, I can see and record much more clearly what I’ve actually been doing.
Lately I’ve been seeing people say that token usage may become an important metric. The idea is that token usage can serve as a proxy for project time. Development speed is definitely accelerating exponentially. By spending more tokens, you can cut down a huge amount of time. Work that used to take weeks or even months can now sometimes be done within a single week. But it also means we’ve entered an era where you have to spend money to develop. If you want to build more, you have to spend more tokens, which means more money. That kind of cost didn’t exist before, but now it comes with the work. I think I need to gradually accept that reality.
I watched Project Hail Mary. I saw the film before reading the book, and it felt like the first genuinely good movie I’d seen in a long time. The story was good, but what stood out most was the direction and how beautiful so many scenes looked. I liked the ending too, and I could feel my heart warming a little as I walked out of the theater. I got curious and borrowed the book from the library, and it has its own kind of pleasure once I open it and start reading. It even gave me a new app idea for the first time in a while.