Asciidoc was the sweet spot of features and readability for me. Really wish it had more tooling.

John Cleese had an amazing talk on this - https://youtu.be/nvKeu46jgwo?si=vIRHSJWXff8Kyf2l on being creative

I also immediately thought about his book on creativity. Thanks for the talk. For me, instead of staring at a wall, I just take a short walk. I think doing any activity with low mental load helps creativity.

What a gem! Thank you for sharing.

This sadly is true in so many segments. The worst is cars. “I’d like the highest trim… oh it’s only available in three boring colors?”

If you’re just looking for the TDD part - https://github.com/nizos/tdd-guard - is the only project I’ve come across that actually enforces it with hooks and blocks edits rather than relying on a prompt that gets context rotted away.

Creator of TDD Guard here, thanks for the mention!

TDD Guard was built when Claude Code was the only one to offer hooks. Plugins didn't exist and the models were weaker, so the validation context and instructions took more work to get right. This is why it ended up requiring test reporters for different languages.

I have started a new project that does the same TDD enforcement, also through hooks, but without reporters. It works with any test runner, and it is vendor-agnostic, it works with Claude Code, Codex, and GitHub Copilot. The validator also sees recent session history which helps it handle cases like refactoring better.

The TDD instructions are still pretty basic compared to TDD Guard's, which have been dogfooded for a year. One thing I noticed while testing across agents is that some follow TDD a lot better than others, Codex struggled the most with the basic instructions.

Feedback welcome:

https://github.com/nizos/conduct

This article is why I replaced all the usb dock cables in the office to make sure the usb cable connected to the laptops was transferring enough power so the laptop wouldn't silently lower its frequency for the lower power draw. 10-30% speed bump just because.

Just write a hook that runs claude -p after whatever you want and update whatever memory system you want. You can use a channel to inject back what topics were update or what have you.

I am not sure how using Claude -p is going to help you imitate Claude’s memory system for any ai agent…

Sure, but the idea is not to have this in Claude Code, the idea is to be able to use something like LibreChat with proper memory. I don’t really need that good of a memory system for my coding agent, it’s definitely more something I need for my chat agent.

Well… I think you’re conflating the stated reason for solving a problem versus what these “solutions” are actually trying to do.

This is cool - just wanted to note https://marginlab.ai is one that has been around for a while.

are there any tools anyone knows to collect this kind of telemetry while using the tools instead of offline evals.

running evals seems like it may be a bit too expensive as a solo dev.

https://sequencing.com/our-difference/privacy-forever seems the best choice these days.

I can believe the company does their best to keep the records private.

...until they're inevitably sold.

Note guidance for 4.7 specifically calls out being more specific compared to 4.6. Though the system prompt seems to say the opposite.

Tldr I would expect different outcomes with 4.7 with not being specific.

Honestly I'd heard so much seemingly conflicting information about the quality of 4.7 that I've got an override in CC to stay on Opus 4.6 (1 million token context) for the time being.

For reference, in the .claude/settings.local.json

  {
    "model": "claude-opus-4-6[1M]"
  }