Recent Replies
@devilgate Had to look him up. But - thank you❓
I never knew how old he was. 60 is way too young.
@WiredDifferently it’s funny that this one surfaced in my feed yesterday which I saved for later - it does look good noting that it comes from 2022. How did I miss it?
paging @dave who I’m sure will have an opinion ..
// @johnbrayton @manton @brentsimmons @fahrni
(#BeyondMyPaygrade … but observing how many cool readers have appeared this year .. that all seem to have a slightly different take)
@softrockstar.bsky.social Not wrong
@bradenslen I was just thinki⚡️💥
@bradenslen Real life corollary just from yesterday …
payment submitted, the thingy spins - get a message that it’s failed - check the card - the money has gone.
Wondering - is that a corollary?
@artkavanagh now that IS a ‘longread’ :-)
@stefp i had never even heard of Broadcast until this post Stephen - so properly checked them out and love ’em - thank you.
Shades of Cocteau Twins / This Mortal Coil - though arguably ‘happier’. Maybe even a gentler kind of ‘Wondermints’. Just great stuff.
It did not.
@artkavanagh they are books - so do have an advantage :-) will make a note to check one out.
@brentsimmons BTW - if either are anywhere on your list of fun things to think about in your ‘retirement’ 😉 more than happy to be a volunteer beta tester. CAVEAT - not a developer.
And I guess while I am here - also a big fan of “one ‘opml’ to rule them all” - so point to an OPML - not import.
It’s an edge case - but NNW is my main ‘master’ reader - but I also dabble with others for subsets … so lots of export / edit / import in that process.
A single OPML file managed on a server - that a reader can point to would allow someone to move feeds into different folders / tags - so that sub readers could access different parts and it would be all dynamic. (BUT - I do very much understand that this is not a typical use case.)
@brentsimmons yes indeed.
@numericcitizen > My wife wouldn’t understand if I got one.
I think you’ve just answered your own question.
@devilgate :-) … it seems such a reasonable thing to do - but no.
Hinds offered three explanations for this paradoxical result:
-
When calculating the 11 hours saved, workers aren’t counting all of the time they spend waiting for AI agents to complete tasks (an activity some are now calling “botsitting”).
-
The workers often ignore the cost of toggling between multiple AI tools as they attempt to get a usable response (60% of the sample reported running queries across several tools in search of better outputs).
-
Workers may also be participating in what Hinds calls “workplace theater,” in which they are “visibly performing work for bosses and colleagues, rather than focusing on the actual grind of getting things done.”

That third one? ‘may’?
Put that one to the top - because it reveals the problem of people inside organisations that predates anything to do with AI and everything to do with how people in organisations work.
There is too much going on in the area of
-
arse covering
-
‘to all’ messages - and replies
-
‘everyone’ meetings
-
eternal ‘brownian motion’- confusing movement with direction
-
non aligned objectives
the list is extensive - should I go on?