As someone who is near-native Japanese speaking ability and who happens to practice BJJ, jujutsu is a profoundly corny name for a version control system.
But it looks good so I'm probably going to try it.
That way we can start a fresh session by saying "this is a continuation of sessions/2025-10-12-something.md, so read that and get up to speed please" and continue from there.
My recent Claude Code adventures are focused on context gardening, making sure each session leaves useful info behind for future work.
CLAUDE files are a good start, but I prefer to have context files for each work item and keep a session log.
If you are:
- Experienced in some hard skill involving knowledge work
- Have good judgement in that skill
- Are good with words
Then the opportunity here is obvious and huge.
But those three together are rare enough that the average person won't see it.
Claude code is like rocket fuel for programming. Things I wouldn't even attempt because they would take weeks I can now put together in hours.
This is not vibe coding. I'm talking well tested, security audited, refactored, readable code that I'd be happy to put my name to.
Using LLMs to write code is a given in 2025...
But what exactly are you going to make that isn't going to be subsumed by LLM based tools in the near future?
Think of any SaaS product or software tool. Surely LLMs are going to be able to do whatever that is in a few months time?
My advice to junior software developers: ignore the advice from senior developers. Smack us over the head whenever we say “simple!” (We just mean “familiar”). Explore ideas, go down rabbit holes, over-use patterns, make mistakes. There’s no better way to learn in depth.