At last we have some rain down in the south of England. It’s been a long time coming and desperately needed as well, if I hadn’t been on a work call and didn’t have the plumber here I think I would be outside standing in it.

I’ve set my old MacBook Pro up as a home server and I’m slowly experimenting with various different things I can do with it. It’s like a fun summer side project.

I’ve set up Plex and Navidrome on it so far, I’ve been rediscovering my old mp3 library while I work. This afternoon I set up Home Assistant, although I’m not sure how much better it is than the Apple Home app, I do like the way it handles my TV. More experimenting to come.

My attempt at watching and capturing this evenings eclipse.

Filming for Amazon’s Young Sherlock in town today.

This flow:

  1. Have a thought.
  2. Start writing a short post about it.
  3. It’s not working. Expand into a full-length blog post.
  4. Still no good. Delete the draft and copy the text into a note.
  5. Months later, pull the draft into a better blog post about a larger topic.

In other words, always write things down.

Manton with the wise words again. This is something I need to get in the habit of doing more often, so many times I think I need to write about that, start a post and then Cmd-A delete it.

In Perils of the New Armchair Scholarship Dan Cohen finishes with a summary that hits exactly where I am landing on using AI in design. Emphasis mine:

This is the professorial equivalent of the cognitive decline that we worry about with our students who have been using AI for years — and what atrophies in the seminar room will surely atrophy on the page as well. The solution seems clear: if you would like, use AI for the parts of scholarly work where it excels and check all automated output, while retaining human seniority in orchestrating and expressing the meaning of your research.

For me, as I explore how to use these new tools in my work, this is where I am landing. I do all the design thinking, the layouts, and interactions but the AI does the building. What would take me maybe a week or more to build a prototype to test a design, takes Claude an hour or two, and as a result my work is richer.

Design for me has never stopped in the design software. When I worked for myself as both designer and developer, design would continue as I built. I would move back and forth between Sketch and code, my problem was that sometimes I was aware a better solution was out there, I just couldn’t build it. When I moved to an in-house design team that symbiosis of design and dev was lost. The design software we used to prototype would influence my design thinking, I didn’t always know how to do something, or it would take too long to build so I couldn’t explore it.

In contrast, the workflow now emerging for me is much closer to what it used to be when I was self-employed, the difference now is that I am less constrained by my own technical ability. I am able to push designs further and see how they work in the browser, my work has become both quicker and deeper.

Atlas looks like an interesting app for collecting an inspiration library. Along time ago I used Yojimbo and a now long gone app (whose name escapes me) specifically for collecting screenshots as my inspiration library. I often wondered how I could return to that practice of collecting things for inspiration, perhaps this might be it.

I’ve been trying to watch Foundation Season 3 but I can’t get in to it. Such a shame as the first season was very good, seems to have been in decline ever since. 📺