Awesome! Thanks for distilling the (significant) value prop and highlighting the author's bona fides, Simon!
It's signal in the noise (which noise includes both the annoying/distracting "mannered" claudisms in the post, and the inevitable complaints in the comments -- which nearly drowned the signal).
EDIT: Also thanks for the link to his index post! Graham's expertise and generosity and suitability as a library maintainer are evident, e.g.:
> Learning it by doing
> Reading about a library only gets you so far, so alongside the posts there is now a wrapture-workshops repository on GitHub containing 24 workshops you can work through to learn wrapture in an interactive workshop format. Each takes one thing you might want to do with wrapture and walks you through doing it in a live JupyterLab session, with the instructions in a side panel whose actions drive the session and check your work as you go. The early workshops track the blog posts, one per post, and the later ones go into areas the posts have not covered yet, such as using wrapture with pytest properly, converting an existing mock based test suite, async code, patching third party libraries, distributed tracing across two processes, and writing an instrumentation package of your own.
> You need nothing installed to try them.
I appreciate how Graham set himself a high bar for what success looks like for his exploration of AI-assisted coding.
A takeaway for me (drawn from what he wrote^1) is that a big increase in velocity can unlock the ability to incorporate things learned along the way into a JIT / as-you-go full redesign (for coherence) vs traditional approach (slower, incremental, features added closer to release can't influence overall design).
Also I'm really impressed by Graham's approach; treating all 3 of (monkey-patching, unit testing, observability / instrumenting / tracing live running apps) as facets of the same whole... it's just beautiful.
Comments
Awesome! Thanks for distilling the (significant) value prop and highlighting the author's bona fides, Simon!
It's signal in the noise (which noise includes both the annoying/distracting "mannered" claudisms in the post, and the inevitable complaints in the comments -- which nearly drowned the signal).
EDIT: Also thanks for the link to his index post! Graham's expertise and generosity and suitability as a library maintainer are evident, e.g.:
I appreciate how Graham set himself a high bar for what success looks like for his exploration of AI-assisted coding.
A takeaway for me (drawn from what he wrote^1) is that a big increase in velocity can unlock the ability to incorporate things learned along the way into a JIT / as-you-go full redesign (for coherence) vs traditional approach (slower, incremental, features added closer to release can't influence overall design).
Also I'm really impressed by Graham's approach; treating all 3 of (monkey-patching, unit testing, observability / instrumenting / tracing live running apps) as facets of the same whole... it's just beautiful.
1. https://grahamdumpleton.me/posts/2026/08/introducing-wraptur...