Why WorkLog became a notebook
Retiring a work logging prototype helped me narrow its purpose. The useful next step was a place for engineering lessons inside the portfolio I already maintain.
I retired WorkLog and archived its repository on 7 October 2026. The idea behind it still matters to me: preserve enough detail about my work to understand it later. I am continuing that purpose through The Software Engineer’s Notebook, an extension of this portfolio.
That decision came from narrowing what I wanted to do with the records. For my own engineering writing, I needed somewhere to explain a problem, the decision I made, and what I learned. Those explanations belong close to the projects they describe.
From recording work to explaining it
WorkLog started as a Flask and MongoDB prototype for recording completed and planned work. Entries held a title, description, status, and additional context. It offered a way to preserve details that are easy to forget when preparing an update or reflecting on a contribution.
I considered a broader professional log with project links, milestones, evidence attachments, and a NestJS backend. That expansion remained a proposal. It would have introduced more features to build and maintain before helping me publish the lessons I wanted to share.
My project repositories already hold engineering decisions and implementation history. The portfolio gives readers background on those projects. A notebook can connect the two by turning selected experiences into explanations that make sense to someone unfamiliar with the code.
Extending the portfolio
The notebook uses the portfolio's existing Eleventy and Markdown workflow. An entry has a title, a summary, a publication date, and space for the problem and its lesson. Entries can link to relevant projects, and those project pages show their related notes.
This gives the writing a home without introducing a separate application, account system, or database. It also keeps the work close to its context: a reader can move from a specific lesson to the project behind it.
The original engineering records stay in their repositories. A public entry selects what is useful to explain, supplies the background a reader needs, and preserves the distinction between what was proposed, implemented, and confirmed in use.
What retirement means
The WorkLog source repository remains available as an archived prototype. I have stopped developing the standalone application and am keeping its project page as a historical case study.
The notebook has a narrower purpose than WorkLog. It supports my personal engineering writing; it does not provide task tracking for other users, and this change does not migrate accounts or work records.
The useful lesson for me is to revisit the purpose before expanding the software. Once I made the writing the priority, extending a site I already maintain gave the idea a clear next step.