Keep iterating

I worked on the priorities I raised yesterday, using a new prompt structure. There was more to do today, but much of it was volume: yesterday I had already done the hardest work on quality. With a stronger Gem, I could carry out a series of more focused tasks.

I can see the result in my research notes. They used to be long and diffuse. Today’s versions are about half as long and far more direct—perhaps almost too utilitarian. I also tailored the help my Gem gives me when I think about a trading system. Working together in the new structure brought out new questions and ideas.

At first I wanted the Gem to work across all my conversations. Now I am less sure. If everything flowed together, topics might bleed into each other and make a response worse. When I ask a question in one conversation, I want the answer to use the context there. What I may really want is a careful way to bring over a useful answer from another discussion when it is relevant. That is worth considering, though perhaps not urgent.

After finishing yesterday’s essential tasks, what should I build next? I keep returning to the structure of a “one-person company.” It is a large, complex aim, and I need to think through it regularly. I am drawn to the way a sound structure might let work accumulate and create leverage. First comes the framework; then I can fill it in and grow its branches.

Do not underestimate iteration or the effect of time. Organizations and complex software are built through repeated changes. But speed alone is not enough. I also need taste and judgment to decide what to improve. A system for teaching myself will be the foundation of that work.