<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: aaron-boodman</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/aaron-boodman.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2025-10-28T02:08:57+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Aaron Boodman</title><link href="https://simonwillison.net/2025/Oct/28/aaron-boodman/#atom-tag" rel="alternate"/><published>2025-10-28T02:08:57+00:00</published><updated>2025-10-28T02:08:57+00:00</updated><id>https://simonwillison.net/2025/Oct/28/aaron-boodman/#atom-tag</id><summary type="html">
    &lt;blockquote cite="https://x.com/aboodman/status/1982898753607741502"&gt;&lt;p&gt;Claude doesn't make me &lt;em&gt;much&lt;/em&gt; faster on the work that I am an expert on. Maybe 15-20% depending on the day.&lt;/p&gt;
&lt;p&gt;It's the work that I don't know how to do and would have to research. Or the grunge work I don't even want to do. On this it is hard to even put a number on. Many of the projects I do with Claude day to day I just wouldn't have done at all pre-Claude.&lt;/p&gt;
&lt;p&gt;Infinity% improvement in productivity on those.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="https://x.com/aboodman/status/1982898753607741502"&gt;Aaron Boodman&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/productivity"&gt;productivity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai-assisted-programming"&gt;ai-assisted-programming&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/claude"&gt;claude&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/aaron-boodman"&gt;aaron-boodman&lt;/a&gt;&lt;/p&gt;



</summary><category term="productivity"/><category term="ai"/><category term="generative-ai"/><category term="llms"/><category term="ai-assisted-programming"/><category term="claude"/><category term="aaron-boodman"/></entry><entry><title>Fixing MSDN with Greasemonkey</title><link href="https://simonwillison.net/2005/Jan/8/greasemonkey/#atom-tag" rel="alternate"/><published>2005-01-08T13:09:52+00:00</published><updated>2005-01-08T13:09:52+00:00</updated><id>https://simonwillison.net/2005/Jan/8/greasemonkey/#atom-tag</id><summary type="html">
    &lt;p id="p-0"&gt;Site specific browser customisations have been a &lt;a href="/2004/Jul/15/persite/"&gt;a&lt;/a&gt; &lt;a href="/2004/Jul/20/innovate/" title="Site-specific extensions"&gt;recurring&lt;/a&gt; &lt;a href="/2004/Aug/19/specific/" title="Site specific stylesheets in Mozilla"&gt;theme&lt;/a&gt; on this site over the past six months. Thanks to the ever inventive Aaron Boodman that problem is pretty much solved. &lt;a href="http://greasemonkey.mozdev.org/"&gt;Greasemonkey&lt;/a&gt; is a plugin for Firefox that lets you create user site customisation scripts (&lt;code&gt;.script.js&lt;/code&gt;), easily install them in Firefox and then set which sites they should be run on. Michael Moncur has a &lt;a href="http://javascript.weblogsinc.com/entry/1234000273026520/"&gt;handy tutorial&lt;/a&gt; on getting started.&lt;/p&gt;

&lt;p id="p-1"&gt;I've already found reason to write my first script. For all of its faults, one thing that can be said for Internet Explorer is that its technical documentation runs rings around its competitors. Safari and Opera have virtually no technical documentation at all, while Mozilla's is piecemeal to say the least (let's hope they listen to &lt;a href="http://www.infoworld.com/article/05/01/07/02OPstrategic_1.html" title="Open source documentation"&gt;Jon Udell&lt;/a&gt; and &lt;a href="http://www.tbray.org/ongoing/When/200x/2005/01/07/TechWikiDoc" title="TechWikiDoc"&gt;Tim Bray&lt;/a&gt;). Unfortunately, &lt;acronym title="Internet Explorer"&gt;IE&lt;/acronym&gt;'s documentation is hidden away on the always frustrating &lt;a href="http://msdn.microsoft.com/"&gt;MSDN&lt;/a&gt;. The good stuff is in the &lt;a href="http://msdn.microsoft.com/library/default.asp?url=/workshop/author/dhtml/reference/dhtml_reference_entry.asp"&gt;HTML and DHTML reference&lt;/a&gt;, but information on which versions (and platforms) of &lt;acronym title="Internet Explorer"&gt;IE&lt;/acronym&gt; can cope with which objects is no where to be found.&lt;/p&gt;

&lt;p id="p-2"&gt;Or at least that's what I thought, until someone on &lt;acronym title="Internet Relay Chat"&gt;IRC&lt;/acronym&gt; told me to hover over the &lt;samp&gt;event&lt;/samp&gt; box at the bottom of &lt;a href="http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/cancelbubble.asp" title="cancelBubble Property"&gt;this page&lt;/a&gt;. Nothing happened (in Safari), so I tried Firefox and IE5/Mac. Still nothing, so I viewed source and discovered that the platform information is hidden away in a made-up &lt;code&gt;platinfo&lt;/code&gt; attribute on the link and revealed using IE/Windows specific JavaScript. Doh!&lt;/p&gt;

&lt;p id="p-3"&gt;A few minutes with Greasemonkey and I had a solution: &lt;a href="http://simon.incutio.com/code/greasemonkey/msdn-platinfo.user.js" title="msdn-platinfo.user.js"&gt;this user script&lt;/a&gt; restricted to &lt;acronym title="Universal Republic of Love"&gt;URL&lt;/acronym&gt;s matching &lt;code&gt;http://msdn.microsoft.com/workshop/author/dhtml/reference/*&lt;/code&gt;. It's not pretty, but it works - and I'm sure it could be made to look quite decent given a little extra effort.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/greasemonkey"&gt;greasemonkey&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/aaron-boodman"&gt;aaron-boodman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="greasemonkey"/><category term="aaron-boodman"/></entry></feed>