Devlog 0xF - Reevaluating Daily Devlogs

Today I will talk about the change in frequency of devlogs and the future of Kirin development.

Devlog Frequency

One of the goals I put forward for myself for the year of 2025 was to publish a daily devlog with updates on my learning. After publishing devlogs for 15 days in a row, here are my main takeaways:

• My schedule doesn't allow for me to spend two hours a day programming side projects and an extra hour doing a writeup of what I've accomplished.
• Writing about my programming tasks and problems is an excellent way to better understand the problem.
• Code within the Kirin project began to get sloppy and hard to manage, likely stemming from the rapid development pace I had set for myself.

With that being said, I've enjoyed the writing process greatly and I think the ability to express what you've made not just in code but also in words is incredibly powerful. Going forward, I plan to do a weekly Devlog that will be published on Sundays.

Limiting the devlog to once a week will allow me to focus on understanding the problems I am trying to solve better and be able to come at them from a more informed position; as well as allow me to focus on school.