Image of the Week
This is a (mostly) random picture I took on one of my photowalks. I like the scene of the lost-but-busy travelling salesman in a brutalist scenery.

This is a (mostly) random picture I took on one of my photowalks. I like the scene of the lost-but-busy travelling salesman in a brutalist scenery.


Recently I was at a conference that only published their agenda as a .pdf
file. While I had ample time to manually transcribe the agenda into my
calendar, I wanted a more automated approach, maybe using one of these
newfangled LLM things that are said to be able to extract text from images
based on a simple prompt. Extracting event information from the agenda
would likely also expand well to pictures snapped of concert posters with
my phone camera, just to get a placeholder in my calendar.
If you subscribe to one of the large phone ecosystems, a lot of this functionality already exists. Google Lens can extract the event dates from pictures for example. But I don't share my calendar with neither Google nor Apple, so I want a more custom and more streamlined application.
Since toying around with Net::CalDAV::FindEntry, I feel familiar enough with CalDAV and Net::CalDAVTalk to see the import as no problem. The resulting application should be a two-page basic web application that is reachable via my private network. Extracting the information is easy by using GLM-4.6V. This means of course sharing that information with some outside party, but it is only potential events and not my whole calendar that I'm sharing.
The code also lives on Github, at least until I move back from Github to self-hosted git repositories.
As usual, I wrote the app in Perl, using Mojolicious and I also sprinkled some HTMX 4 on it, for some interactivity. For example, the image upload form does not need a second click to actually upload the selected image. Also, while processing the image with the LLM, the page automatically refreshes until the results are in.

Uploading consists of an image and also an optional prompt, to maybe reduce the number of events created. I found that some nudging for events in the past or in the future was needed. Uploading the image happens together with pressing the camera icon. This is not great if you selected the wrong image, but that happens rarely to me and adding another image isn't that bad.
I was too lazy to capture the reloading while the extraction is processing.

The results page allows to select events for import and also shows the preview with title and description. The text recognition isn't always great, but it is Good Enough for my needs.
At least for debugging, I also wanted a quick way to inspect the generated
.ics calendar data, so I added the "raw" view. This displays the raw
data in all its g(l)ory.


After importing, the app also checks my calendar whether the event has already been imported. This is highly convenient for me to see whether everything actually worked.
I used GLM-5.3 for parts of the development. I had the model write most of the
test suite and also had it review the HTML and the use of HTMX. It found some
things that would have been annoying for me to find, like double id
attributes on HTML elements, old HTMX attributes that HTMX 4 does not support
anymore.
The fixes the model proposed were also of acceptable quality, but I did not let it create new features alone. Everything was tightly guided, which results in code quality that I am content with.
This is one of my favourite pictures. It is an unedited snapshot of an unoccupied restaurant.

We did the almost-annual unconference, this time at the Saalbau Bornheim. The attendance was expectedly low at 5 persons, one person joining us from Amsterdam and one person joining us from Darmstadt, the rest being Frankfurt.pm regulars.
None of us had prepared anything in a presentation format, with slides, but we had a lot to talk about regarding the use of LLMs and what that means for the economy and also for us personally. I spoke a lot about how I don't see that the AI frontier labs can ever recoup the money they've pledged on datacenters. We also mused about why Chinese labs are giving away their models and also why Mark Zuckerberg is doing the same with Llama-2 and Llama-3. We concluded that this is their strategic approach to prevent a hegemony by the other two frontier labs.
Tech-wise, we looked at some approaches to LLMs. I showed my (yet) unpublished skeleton files for Perl modules and Mojolicious applications. I've found that giving LLMs like GLM-5.3 files to work from tends to prod the model to produce code close to that style. Since I prefer that style to other styles, I've found this approach very successful.
In addition, we also looked at how superpowers works and that a good side benefit of using it is that you get some test files written by the LLM already. We all found that creating test files is a good use of LLMs. Since the code in test files is disposable and if the test file is written in a too complex way, you can just delete it or rewrite it without consequences on the main code.
My main comparison was between the two approaches I'd used for writing two
applications. One application was an extractor that creates CalDAV entries
from a picture of an event poster. I had created that script using GLM-5.3
as a one-shot without superpowers. The resulting code worked, and used GLM-4.6V
to parse the image and create the .ics output. The resulting code also
was very icky to work with, spending far more lines on various configurability
I would never use and precautions against missing tools that would never be
missing.
The other application was a web frontend to the pi agent, to make it more
convenient for me to use LLMs. Using the browser allows me to create fancy
widgets to display the status of the test suite and also submit screenshots
to the LLM for reference. I created this frontend using a relatively detailed
list of features and also described which functionality should be implemented
in what file, providing structure to the LLM. This approach resulted in much
better and much more maintainable code than the one-shot leaving the LLM
to implement things all on its own.
For lunch, we went to a new Chinese-style place with handmade noodles. I had a reasonably priced beef soup with handmade noodles. It was very spicy but otherwise good.
After lunch, we discussed the use of Perl to tie together some tools for language and speech analysis. We looked at how different Chinese is from other languages, and how different Cantonese and Mandarin are.
I was revisiting some old pictures and found this series of pictures shot in the MyZeil shopping mall.
