I spent a little time with the blog last night and pulled together two new site features using Claude Cowork. The last time I experimented significantly with Claude like this was to use Claude chat to build the link log from scratch, walking it through my thinking in plain language, then copying and pasting its suggestions into the backend of the site and hitting publish. This time I used Cowork, the tool that runs in the browser, and it clicked through the screens itself, fully taking on the execution of tasks. I have some coding skills, but not the kind these changes required. If I were taking this on, I would need YouTube, Hugo for Dummies, and my own personal IT guy, and still probably couldn’t pull it together.
Last night I asked a few things of Claude:
I asked Claude Cowork to get into the backend of the micro.blog site and change my theme to link each line in the linklog back to my original post. The date field in the right column now links back to the original post for each link logged. No problem, easy request with easy execution. I made the request, confirmed the plan, and went about my business while Claude made the edits.
I also asked it to analyze my post content and suggest category tags for groups of content, then to label that content correctly in the backend. Claude reviewed about 500 posts and suggested I add a few new categories to my blog: AI in Practice, Books & Reading and Writing & Language. Then I set up some auto-filters to run at publish time to automatically categorize posts based on keywords moving forward.
Finally, I manually added the archive page, which lets you sort posts by category or year. This means I now have a functional archive here. Enjoy my anodyne thoughts, dear reader.
Adjacent to my day job, I’ve been toying with Claude Pro now for about a year; in my experience, it has improved significantly within the last six months. It’s not perfect: my requested edits were completed, but it also changed the CSS on the linklog so some of the text is too light to read, which I didn’t ask for and don’t want. But it has arguably extended my ability to execute on work that requires skills I don’t otherwise have (such as design and coding). What I do bring to the table is an expansive practical background in publishing and production, and all the language to describe it.
A friend of the blog shared the Embroidered Computer, a programmable 8-bit computer created by using a combination of magnetic and glass beads, gold wire, and traditional gold embroidery techniques to fix material elements to cotton cloth. When complete, it has the processing capacity of a 1950s mainframe computer without the modern silicon microchip. Something about this reminds me of Ellen Ullman’s observation that computers are made of boxes and wires, written on chips and tape. (via)
I can’t believe it’s mid-August. I’m terribly behind on my reading list. Still, I did want to draw attention to this entertaining and extremely shareable article on the glory of Record Head, a legendary record store in Milwaukee. Make sure to watch their public access TV commercials at the link.
Winer on the purpose of web standards: “I find that most standards that come out of the standards bodies aren’t developed by implementors or with them in mind. They avoid trying to solve any specific problem, rather focusing on the elegance and flexibility of the format. This makes interop much less likely. I saw the differences several times as the web standards were growing up.”
I watched “Obsession” with my teenager last night, and dare I say, I liked it as a little genre story, a morality play about romance, relationships and consent. I also enjoyed the practical horror effects.🍿
A colleague hosted a nice discussion of the work of David Dylan Thomas, who advocates for using human-centered design concepts to bring humanity back to tech. New and novel approaches abound, especially on whether and how to let engagement metrics drive decisions on design teams.
