pilord314

you bootstrap it into a library you can include optionally, duh

I've been playing around with an AI generated knowledge base to grok our code base, I think you need good metrics on how the knowledge base is used. A few things is:

1. Being systematic. Having a system for adding, improving and maintaining the knoweldge base 2. Having feedback for that system 3. Implementing the feedback into a better system

I'm pretty happy I have an audit framework and documentation standards. I've refactored the whole knowledge base a few times. In the places where it's overly specific or too narrow in it's scope of use for the retained knowledge, you just have to prune it.

Any garden has weeds when you lay down fertile soil.

Sometimes they aren't weeds though, and that's where having a person in the driver's seat is a boon.

A disassembly diff tool:

input <- old_image new_image

output -> report

Example summary:

================================================================================

TOTAL

================================================================================

  -20 insns, -40 bytes (c.insn→insn +40b)  [spill -22, cmov +3, call -2, br -1]  mem +13, alu -6, mv -4, bitmanip -1

  Added/Removed: +0 / -220 bytes

  Functions: 4 better (-20 insns), 0 worse (+0 insns), 1 removed, 1062 unchanged

When you get into C code sometimes you know the most thinngs that will be in the priority queue is like 3. So bubble sort is fine.

You can also do something like a calendar queue with bubble sort for each bin.