@inthehands I had a terrible usability experience with the iPhone my first time, though my point of comparison was the HTC Dream.
Mostly my feeling was that the iPhone touchscreen was impossibly awkward for a person with fingertips of my size.
A couple years later, Google's employee holiday gift was a touchscreen phone. And that was the last time I had a phone with a real keyboard.
Touchscreen controls let the designer do everything in software, but they also got us autocomplete as a necessity, and hinder the usability advantages of muscle memory.
@inthehands The financial bubble around generative model technology is pretty much the primary feature I see.
Since there's current value to repackaging any effort around the bubble's hot buzzwords, it makes it that much harder to understand what any given technological effort is doing.
@inthehands I have observed the original poster (of the quote; not the quoted speaker) to make categorical assertions in a style I find difficult to read, frequently enough that I avoid following him, while continuing to follow his well intentioned indie web work.
Even if his condemnations have good reasons that I may agree with, and help to motivate his good work.
@inthehands The one report of LLM-generated / LLM-using code that I found most striking was from Jon Udell, related to generating an app for converting a photograph of an event flier into a useful calendar entry.
Partly it was striking because Udell has been a long-term advocate and a developer of community-run local information resources including calendaring, which have mostly been absorbed by Big Social Media.
The app combines small deployment scale and low cost of error (hand-fix the calendar) with toil reduction around composing APIs -- and makes something possible by making it easy. Not an app I'd want to maintain for others, but a technique for bringing tedious things in reach, so they happen on a relevant time scale.
@inthehands I suspect that answering the question "why is it the _what_, _how_, and _why_ of development are at odds" heads straight into the way human systems get stuck in bad states.
Having the words for the intentions, expectations, and qualities of the work can help people at least not talk past each other.
The field in practice has shipped a million leaky prototypes that demo'ed well. Time to market? Time to capture funders' attention? Those bring their own pressures and problems.
I think of Kingsbury's Jepsen project as a model of asking whether the "what" was actually delivered by testing the fundamentals.
@inthehands Things which ought to be obvious bear repeating, to check that our premises haven't changed.
Brooks' No Silver Bullet and Mythical Man-Month remain relevant critiques and mostly unlearned lessons; an indictment of the information technology field as practiced in the world.
NSB is absolutely worth checking. If you make the "how" as easy as you can, you're grappling with the "what".
Opinions vary on the division between "how" and "what". ("dev" and "product"?)
@inthehands@straphanger Get there with positive social priorities while things are loose, so as not to waste a crisis opportunity? That sounds like the maxim "chance favors the prepared mind" applied to policy advocacy.
The same story has been told for having system resilience plans ready in a box for when a digital service outage opens a window to use them and improve the future now, while you can.
@skinnylatte Our SF laundromat was the "Little Hollywood Launderette" on Market Street which closed a few years ago after 52 years in business. A laundry trip was a little two-hour excursion together.
@skinnylatte I am following your food posts with attention so that I can forward them to the resident college student who does most of his own cooking and enjoys rice and spicy food (sometimes too spicy for me; I would expect not so for you).