Less Input [en]

In the spirit of shortening things, I’m taking a few moments during my lunch break to share some thoughts I’ve been having recently. Various things have contributed to these thoughts:

  • my permanent struggle with “too many ideas” and “too many things I want to do” (which predates my accident, but is now exacerbated given my reduced energy)
  • pondering on how to manage my energy (already underway since my accident, but now fed by the occupational therapy programme for energy management that I’m in the middle of)
  • my training at IGB, and the two-day course I just did in Paris (the recurring focus is “how something that works for the person at some point becomes the thing that feeds the problem”)
  • my exploration of AI and in particular the framework/project/took that was previously called PAI (now LifeOS) (output is cheap now: feed a genAI model a few lines and it can spit out thousands of words for you).

I’m not going to be able to reconstruct how my ideas around this have shifted in a chronological or well-organised way, but here’s more or less where I’m at: I’m somebody who believes that “knowledge is power”, that “more information is better”, that by learning and analysing and understanding, I can find answers.

That works a lot of the time, for me. It has worked very well for me. But I’m starting to see how this is part of what is trapping me, right now.

At some point in my struggles with my AI infrastructure (trying to get the PAI Digital Assistant up and running correctly, fixing bugs, making sure it learns correctly, setting up workflows for the things I want it to do for me) I realised that it had a built-in bias (the model, most probably) towards “producing more is better”. LLMs are verbose, we all know that by now. The more you feed them, the more words they spit out – but not necessarily the more useful information.

I kept giving instructions for concision. I would provide examples of how to write things up. I would set up guardrails, have it self-correct, hunt for fluff and filler content. At some point I realised that “the system” was just growing and growing in terms of content (the number of words and files that contained the instructions), and the output was not improving – more like the contrary. This is nothing new, right. We know that complex systems balloon up and lose efficiency. And I’ve seen more than once in my dealings with AI that I pretty much always end up spending more time “fixing the system” than actually using it. This, actually, is something I’d noticed about myself in general; but it’s easier for me to rein in when I don’t have an LLM at the other end of the keyboard. So here, it became even more visible.

So here it is. The mantra I keep repeating to people in all sorts of context: “less is more”; “better is the enemy of good” (that’s what we say in French). If I feed my AI system less input, I get less bloated output in the system. I read somewhere (can’t remember the source, probably have it stashed away somewhere) that in the age of generative AI, the bottleneck was shifting from content production to content consumption. What we can “ingest” is the limiting factor, now that we have machines that can spew out words and sentences and paragraphs and essays and reports like there’s no tomorrow. But it’s worthless unless we can read it and understand it and do something with it. Just feeding that AI output to another AI is just going to magnify errors and biases and produce more slop, unless there is a humain mind in charge that understands what it’s doing and what it’s asking.

Early on, in 2024, I remember reflecting at some point that the AI I was using seemed “more ADHD than me”. And what my more recent experiences have helped me understand about myself is this:

  1. My problem, my “slop/bloat” is ideas and things I want to do. I am somebody for whom ideas are cheap. I have ideas all the time. I can come up with stuff I’d like to do all day. My problem (bottleneck) lies in selecting what I run with, and that is a difficult exercise – even more difficult since my accident.
  2. The more “input” I get, the more – just like the LLM – I produce ideas and desires. I read an article, there are 5 more I want to read. I have a discussion on a topic, I want to read more stuff or write articles or create a community around it. I learn about something new, oooh it’s nice and shiny and I want to do it.

Having a large capacity for input and lots of ideas, followed by enough energy to take a handful of them and run with them (OK, frustrating to have to leave so many aside, but at least I’m busy doing something useful/interesting with some of them) has, as I said above, served me very well in life. But trees don’t grow to the sky. At some point, what has worked well becomes the source of the problem.

And I’m realising that the way out of this, at least now, is not better prioritising. First of all, it’s reducing input.

Less input, less ideas, less “oh I want to do this thing”, less slop to sort through, less frustration with everything I’m not doing.

Exactly how to achieve that is still a thought in progress. But that’s what I’ve been thinking of this last week or so.

WordPress Finally Has Tags! [en]

[fr] Après des années d'errance, WordPress implémente enfin un système de tags qui ne sont pas des catégories. Un billet un peu plus complet en français s'impose probablement. Qu'en pensez-vous?

I’ve known for some time that version 2.3 of WordPress would support real tagging. Today, Matt has just announced the deployment of tagging on WordPress.com.

From the start, I’ve been a very vocal supporter of the differentiation between tags and categories — and I really appreciate Matt acknowledging this in his announcement.

When I first met Matt offline for the first time nearly a year ago, at Blogtalk Reloaded in Vienna, I jumped on the occasion to pester him about tags and categories. He listened — but I don’t think he was convinced at the time.

A few months later, I was in San Francisco — and one of the first things Matt told me when we met again was “you know, I finally saw the light about tags and categories”. He told me version 2.3 would have both. I was overjoyed. I’ll never know exactly what role I played in Matt’s “seeing the light”, but I like to think I contributed 🙂

Looking back in time, Technorati started indexing tags in January 2005. They weren’t new for me then (I’d been tagging things on del.icio.us since May 2004 and on Flickr since October of the same year) but clearly, being able to tag posts was a great thing. You know me — my brain can’t sit still — two days later, I was rambling about some ways to combine tags in searches/sorting. Some of the stuff I talk about in there isn’t possible yet, but I hope it will someday.

Two days after that, I wrote my first WordPress plugin, Bunny’s Technorati Tags — which became quite popular and which I still use to this day.

I’m really glad to be able to retire this plugin, specially as Peter Westwood has written an importer for it. That means you should have no problems converting your bunny-tags into wp-tags. Thank you very much, Peter.

Bear with me while I dig though my archives: weighted tags by category is something I’d forgotten I’d wanted… does anything like that exist now?

My only gripe with the implementation of tags in WordPress, for the moment, is that they will be comma-separated. No! Please! We’ve been typing space-separated tags into Flickr and del.icio.us for three years now. Three years! When I chose space-separation for the tags in my plugin, it was because the existing interfaces for tags did it like that.

Spaces, please. Or at least an option to input them space-separated. Or a simple plugin. Tags separated by spaces, and multi-word tags between quotes.

Call to WordPress Plugin Developers [en]

Call for help to WordPress plugin developers. I have a bunch of hacks and modifications I’d like to turn into plugins, but I am unfortunately as plugin-challenged as ever.

[fr] Un descriptif des plugins que j'écrirais pour WordPress si je ne faisais pas un vilain blocage sur le sujet. Ne vous gênez pas si vous voulez contribuer!

If I was fluent in WordPress plugin coding, here are the plugins I’d write. If you feel like coding one of them yourself, or helping me get it done, you’re most welcome. Carthik has already pointed me to Plunge into Plugins, which I will have a close look at once I’ve finished writing this post.

Of course, if you know of a plugin which does precisely what I’m describing here, leave a link to it in the comments!

Keywords plugin

This would be a pretty straightforward one:

  • add a “keywords” text input to post.php
  • save the value of that text input to a custom field called “keywords”
  • add those keywords as an HTML meta tag on the individual post pages.
Excerpt plugin

This one would also be pretty straightforward, as all it would do is add the “excerpt” field to the “simple” post.php layout.

Customize post.php plugin

This would be more complex, but allow for more flexibility than the previous plugin. I don’t yet have a clear idea of how to make it work, but the basic principle would be to allow the user to select which fields should appear on the post.php page. Instead of having “simple” and “advanced” controls, this would add the option to have “custom” controls and define them.

TopicExchange plugin

As far as functionality is concerned, this plugin would do what my TopicExchange hack did:

  • add a “trackback TopicExchange channels” text input to post.php
  • store the space-separated list of keywords in a meta value named (e.g.) ite_topic (one record for each value)
  • for each value, trackback the appropriate TopicExchange channel
  • display the trackbacked channels (with link) on each post.
Bilingual plugin

This would be a clean version of my language hacks:

  • add a small “language” text input to post.php (with a default value)
  • add an “other language excerpt” textarea, which posts to the corresponding custom value
  • display the “other language excerpt” at the top of each post
  • provide a function to return the post language, and the other-excerpt language (so it can be declared in a lang attribute, allowing the use of language-dependant CSS formatting, in addition to being semantically correct)
  • if this is not already possible with the date function in the WordPress core, provide an alternative date function which will format the date correctly corresponding on the language of the post
  • optional: figure out a way to adapt text like “comments”, “categories” etc. to the post language; make the plugin usable with more than two languages.
Smart Linkroll plugin

I love the way ViaBloga manages blogrolls and would love to see a plugin for WordPress that does the same thing. In ViaBloga, you simply enter the URL of the site you want to add to your links. ViaBloga then retrieves the title, description, RSS feed address, and even (yes!) a screenshot for the site. No need to fill in fields manually anymore…

Wiki-Keywords plugin

I haven’t through this through yet completely, but it seems to me that a plugin which would add wiki-like capability to WordPress, like ViaBloga does with keywords, could be an interesting idea to explore.

Technorati plugin

This is really a simple one: add a function which will allow easy display of the Technorati cosmos of each post, like I have done manually for this weblog.

On the subject of multilingual blogging, Kevin Marks has some interesting markup suggestions I need to look at more closely.