The solution is ironically, LLMs. You can construct a set of Claude skills to walk you through a code review, or understand code (anything, even course) fast.

This complexity to understanding compression will be a big market going forward.

There is a treasure trove of interesting stuff if you have the LLM look at the chat history as well.

I’ve been building skills and agents to help walk my projects history and chat to answer specific questions or find nuggets. For example I’ve got an agent that lets me ask “find me instances in this project where I demonstrated engineer vs product tradeoffs”. It will mine the chat history, git logs, documentation files I wrote looking to answer that.

Someday soon I’ll publish my techniques. It isn’t magic, the hard part is shaking the bias out of your mining agents so they don’t get loaded with “pre-discovered” wisdom and do nothing but confirm what the orchestrator told them they should find.