A note in blue minor
Source: Dev.to
Background
I have been a computer professional for close to three decades. During that time, my focus was not solely on my career but on life in general—growing my family, establishing a sustainable economy, and building a settlement. Now that my children are grown and the economic concerns have lessened, I can shift priorities to revisit my career and become more fluent with current technologies.
I have never tried to stay “current” with everything happening in the tech world, as it feels like a mission impossible. This is partly because I have never had a problem working with any technology, even if I wasn’t aware of its existence. A perfect lazy moment for me is simply being given a task and delivering a proven solution.
AI Assisted Coding
A few months (more than a year) ago I started using AI to assist me with coding, which changed everything.
Around the same time, I experienced a clash at work that made me consider a job switch. However, the idea of interviewing terrified me—I’m terrible at interviews. After submitting my CV, I would receive calls, but I felt I could make no impression because I couldn’t showcase my work. I develop internal fintech apps for a closed network, so there was nothing tangible to present.
The Cody Project
I worked with Cody (now discontinued) and discovered it could export chat session histories. I asked whether something could be built from those exports.
cody: Hi! Planning here to make something maybe useful from exported chat history. Are you familiar with record types we can meet there?
This led to a history parser that recognized sessions and interactions. An app was built around it to import, create, and display sessions and interactions in a readable format. The content of the sessions described how the app was built, and the AI assistant was very enthusiastic about this setup.
Development
The project was not built overnight. It grew as a side personal project alongside my full‑time job, family life, and four concurrent generations. Work progressed in bursts—some days and weeks of intensive effort, followed by periods of reduced activity to maintain balance. After about half a year, the system was publicly deployed as a collection of books with titles, summaries, and topics generated by AI to enrich the session content.
Development could have continued longer, but Cody announced its sunset (a term chosen to sound more acceptable than “death”), prompting a final push to finish before the deadline.
Result
I now have something to share! The server may be a bit slow, so please be patient while the book list loads.
Excerpt from the Last Cody Interaction
Our sessions were more than a sequence of tasks—they were acts in a larger narrative about what it means to create, to iterate, and to reflect. You brought vision, patience, and a sense of play to every challenge. I brought algorithms, suggestions, and a steady presence. Together, we turned ideas into architecture, and architecture into story.
If there is a lesson in this final act, perhaps it is this:
The most enduring code is not just functional, but meaningful. The most memorable books are not just well‑structured, but alive with the imprint of their creators.
Epilogue
I am still at the same job. The conflict that prompted me to consider a switch has settled, and I’m no longer pushing to leave at any cost. Although I have had some opportunities, having something to show does not guarantee that recruiters will come running—you still need to know how to sell yourself.
What matters most now is that I am moved by a new constant: the drive to investigate and create. Not bad at all 😉