Really good Go template - simple to grasp, good architecture basics!

gamedev

GIF / WebM Demo Recorder, customizable recording and quality and everything.

Cross-platform zettelkasten Editor

Go Code Quality

From previous experience, I found that I was making too many knowledge items while reading, which made it hard to identify the really important ones. So now, I read through the entire document (article PDF or chapter of a monograph) and mark down possible knowledge items (yellow highlight in citavi PDFs, pencil or 3M flags in printed materials). Then when I've finished, I write a summary knowledge item in 2 paragraphs—the first outlines the argument, the second (in italics) gives my evaluation and thoughts about possible uses. (I don't use the evaluation field in the contents tab as I want to be able to see this quickly in the knowledge view.) Now I'll go back through the marks I've made and work out which ones I want to input as knowledge items. As part of the input, I will assign to as specific category as possible. Every few days, I will have a look through my outline to see where the holes are (not a lot of knowledge items), and to see if anything in the NOT SURE YET category sparks any new thoughts on organization.

Entity Component System - Inventory systems and general advice

Stress testing markdown notes.

Food and Calory Tracker

gamedev Entity component system game engine

golang coded GUI for nvim

• Build dependencies
• Docker Dockerfile creation
• Automatic Versioning and Version and Build injection
• makefile automations
• Licensing

and much more