This kind of explains why Claude will find the right solution, but then the more it thinks and keeps “improving” the more over-engineered (and sometimes wrong) the solution is. Interesting to see this coming up in formal research.

I do something similar when interviewing, asking candidates to walk through a project they’ve worked on that didn’t go as planned, and what they learned.

Usually it’s work-related, but sometimes the personal stories like this sailing one give a better insight and show real understanding of systematic failings and that they really have the right mindset. Those real world examples speak volumes.

Could definitely see using this for docs. We end up with HTML scattered through our markdown files whenever we need something beyond basic formatting, which is ugly. The ecosystem support is the real question though - Markdown works everywhere because it's been around forever.