Software: Weekly Summary (January 19-25, 2026)

I’d say this week in software felt a bit like a busy local market where some stalls shout about shiny new gadgets and others quietly fold away classic tools that still work beautifully. There’s talk of tools and craft, of AI doing the heavy lifting (sometimes clumsily), of grief for apps people loved, and of small projects that glue things together in the background. I would describe the tone across the posts as part-hesitant, part-excited, and part-nostalgic — like three different playlists playing at once on a Sunday morning.

Writing, agents, and storytelling in code

Dan Corin takes a slow, reflective tack on the change in how we write about software. To me, it feels like someone saying, “writing used to be handwriting in ink; now it’s live-coding with a helper leaning over your shoulder.” He’s noticing the split between old-fashioned, single-author prose and this new collaborative riffing with coding agents. I would describe his tone as steady — not celebratory, not panicked — more curious and stubbornly personal. The post hints that the craft of explaining code is changing. That’s not just tech talk; that’s about how a joke, an aside, or a tiny example survives the translation between human intent and machine suggestion.

There’s a through-line here with Philip I. Thomas, who goes a bit further into what I’d call the era of “code abundance.” Philip says software is easier to produce now. Too easy, maybe. He writes about how ideas for small projects used to be special and now they flood in, and you can end up with decision fatigue — a cupboard full of ingredients but no idea which meal to cook. He coins a nice little term: digital proprioception. It’s a way to talk about software that helps you feel what your data is doing — like knowing where your keys are without looking. To me, that’s one of those neat sparks: code as content, code as feeling.

These two pieces together make a small argument — sometimes explicit, sometimes not — that storytelling still matters. Even if an agent helps write a function or a paragraph, someone has to choose the example, the metaphor, the moment of human clarity. That’s something you can’t fully hand over. If you like the smell of that argument — the warm bread smell of old-school writing meeting AI — go read both.

The nostalgia lane: Aperture and the art of software craft

There’s an unmistakable thread of grief this week. Two posts — one by Nick Heer and another by Michael J. Tsai — both eulogise Aperture, Apple’s pro photography app, which many readers still miss. They aren’t just missing a feature set. They’re missing a design sensibility, the kind of engineering attention that seemed to cradle a particular user need. Nick’s piece strikes me as almost elegiac; it’s like someone talking about a favourite record player you can’t replace. Michael layers in the community response and the long tail of what the app meant to professionals. There’s a small, sharp complaint running through both pieces: current offerings feel thinner, more piecemeal, and less lovingly crafted.

This isn’t just tech nostalgia. It’s cultural. Losing Aperture, for these writers, is like losing a local cinema that used to show films slowly and properly. The apps that replace it feel like multiplexes — lots of screens but less soul. If you’ve ever been fussy about buttons on a kettle, you’ll get this feeling.

Apple polish, or the lack of it

That note about polish shows up again in Erlend’s rant on the new macOS. He calls out icon scaling issues, interface glitches, and other signs that the place that used to sweat the small stuff is now sloppy in parts. It’s a fast, sharp take — the kind of post that makes you check your machine to see if you’re one of the unlucky ones. Read it if you like a bit of kitchen-sink complaint with your software news. It’s satisfying in the same way cold tea is, if you’re the kind of person who notices when a spoon sits odd in the drawer.

Bruce Lawson’s reading list (Bruce Lawson) touches similar territory but from a different angle: policy, standards, the economics of cloud providers in Europe, and how big tech’s dominance shapes what developers can do. It’s less about interfaces and more about the plumbing under the city.

Small projects, connectors, and the joy of useful hacks

Not every post is a elegy. Some are practical and quietly brilliant. Artur Piszek writes about Jackpoint — a way to run Claude sessions via Matrix DMs. That’s the sort of tidy little tool that feels like a pocketknife. It fixes one friction: mobile notifications and quick replies without babysitting a terminal. It’s not headline-grabbing, but it’s the kind of weekend project that saves hours of annoyance. I’d say these projects show up like good street food: simple, practical, and oddly comforting.

Similarly, Tim Riley gives us a peek into a framework project, Hanami. The update is practical: i18n support, a mailer rebuild, website improvements, and a ship-schedule for May. It’s the steady maintenance work of an ecosystem. People often skip this stuff in favor of flashy new frameworks, but if you’ve ever tried to patch a leaky ceiling, you know you appreciate steady maintenance. Tim’s update reads like a friendly neighbour saying, “We fixed the roof. We’ll patch the gutter next.”

There’s a pattern here: the week’s most useful posts are about glue and care. Whether it’s a Matrix bot or a fuller-featured web framework, people are doing the quiet work that keeps things running.

Platform choices and the itch to move

Jack Baty has a short, warm report about toggling between Linux and macOS. It reads like someone who’s been in a small town their whole life and keeps flirting with the city. Linux has power and a certain friendliness for people who like to tinker. macOS still brings polish and some apps that refuse to exist elsewhere. Jack’s piece captures the everyday friction: file sharing awkwardness, missing proprietary tools, and the social awkwardness of sending a file to someone who expects a Mac. It’s practical; it’s also quietly human. You can hear the little sigh when he chooses a distro and the little grin when something just clicks.

This toggling is a recurring real-world problem. People choose platforms not only for technical reasons but for what their coworkers, clients, or friends expect. That social dimension is often bigger than we admit.

AI, finance oddities, and weird ripple effects

Paul Kedrosky has a rapid-fire “Rough Notes” post that rattles among topics: AI’s effect on software production, an odd market bump where toilet-maker shares rise because of AI demand (yes, really), and a mention of Yuval Harari’s thoughts on intelligence shifting history and money. The style is note-like — quick observations rather than deep essays. It’s useful as a barometer: AI is reshaping things in predictable and silly ways. The toilet-maker example is the kind of quirky economic ripple that makes you smile and then think, “Huh. Supply chains are weird.”

These notes tie back to the earlier thoughtful pieces about code abundance. When there’s more software than attention, markets and people react in odd ways.

Community, standards, and the small victories

The metacpan weekly report from niceperl.blogspot.com is another shade of that maintenance-and-community theme. It’s a favourites list for CPAN distributions, complete with votes and build dates. This sounds geeky because it is. But I find it comforting: people voting, maintaining, and celebrating the small libraries that make big systems possible. It’s like watching local gardeners share tips at the community centre. If you’ve ever depended on a small crate or gem and wondered who tends it, this type of post is a handshake.

Likewise, the IndieWeb Carnival interview (James' Coffee Blog) digs into “Tools” as a theme for creative work. The conversation isn’t about corporate APIs or venture capital. It’s about how local, grassroots tools shape what people make. That matters. You get a sense that some folks still want a world where tools are personal and messy and generous.

Running themes and a few disagreements

A few themes recur across posts:
- Nostalgia for well-crafted software (Aperture, polish on macOS). People miss the days when specific apps seemed to show love for users. I’d describe this as a tug-of-war between craft and scale. Some posts are clearly on the craft side; others shrug and accept change.
- AI-driven abundance and decision fatigue (Philip, Paul). There’s excitement but also a weariness. More code, more options, more noise. To me, it feels like a supermarket where everything is on sale and you can’t choose what to cook.
- Practical glue-work and little hacks (Jackpoint, Hanami updates). These show up as hope: small tools fix daily problems, and that matters more than grand claims sometimes.
- Community and maintenance (metacpan, IndieWeb, Hanami). There’s warmth here. People maintaining libraries and organising community events keep things from fracturing.
- Platform sociality (Linux vs macOS). Choices are technical but also social and practical.

On disagreements: some posts are clearly critical of big vendors, others are more forgiving. Nick Heer and Michael Tsai are pretty firm about Apple losing its way. Bruce Lawson’s list is more systemic: regulation, cloud economics, and standards need attention. You can see two different responses to the same worry: one says, “They stopped caring about craft,” and the other says, “The system’s incentives promote this, and we need to fix the system.” Both views have merit.

There’s also a quiet split about how to treat AI. Philip and Paul point out fatigue and weird market effects; Dan is more focused on the craft of writing with agents. Some people leap to dystopia; others are quietly building better workflows. That mix keeps the conversation honest.

Little metaphors, little pleasures

I keep thinking of everyday analogies while reading these posts. Aperture’s loss is like losing an old toolbox where every notch on the handle fit your palm. Jackpoint is like a pocket lighter that never leaves your jeans. Hanami’s maintenance work is a neighbour fixing the fence so your dog can’t wander into the street. Decision fatigue from AI is a fridge full of condiments but no idea what dinner is.

There are regional flashes too. Some posts nod to Europe’s cloud concerns — feels a bit like British tea cup etiquette: a small but important protocol that keeps things civil. The macOS polish complaints land with a North American, metro-tech vibe: expectations of shine and seamlessness.

Who might like which piece

• If you like methodical craft and mourn lost apps, read Nick Heer and Michael J. Tsai. They’ll poke that soft spot.
• If you’re curious about how writing and AI meet, start with Dan Corin and then poke at Philip I. Thomas for the tech-and-feeling side.
• If you want practical weekend tinkering, check out Artur Piszek for Jackpoint and Tim Riley for Hanami updates.
• If you like quick thought-dumps and odd economic notes, Paul Kedrosky is the snack-sized pick.
• If you care about community work and small libraries, the metacpan post from niceperl.blogspot.com and the IndieWeb Carnival chat at James' Coffee Blog are the kinds of posts that make you nod and bookmark.
• If you’re switching platforms or planning to, read Jack Baty for the reality check.

A few small takeaways, and a small digression

One tiny takeaway: writing about software still matters. Even if an agent writes a snippet, someone needs to pick the example and make the joke land. That decision — the human edit — remains important.

And a small digression: there’s something comforting about quick project updates and maintenance notes. They read like farm reports. You might not think farm reports are thrilling. But they tell you the crops are okay, and someone’s fed the hens. That matters.

Back to the posts — there is also an emotional economy here. People invest love in apps (Aperture), in projects (Hanami, CPAN), and in small helpful hacks (Jackpoint). When those things fray, the reaction is personal, not just technical. That’s worth noting because it changes how you respond.

If you’re skimming for a mood instead of a headline: expect a mix of grief, practical fix-it energy, and a smattering of bewildered amusement at market oddities. The conversation is living in the small details this week.

If one of these snippets tickles your curiosity, go visit the author page — the posts hold more texture than I can fit here. The long reads have examples, code, or little rants that are worth the time. And honestly, the delight of a tiny tool or a careful essay is one of the best parts of following software commentary. It’s like finding a perfectly ripe mango in winter.

So, pick a post and dive in. There’s grief for old favourites, yes — but there’s also a lot of fixing, building, and arguing happening in small, useful ways. And sometimes the small stuff — the little bot that saves you five minutes, or the update that finally makes translations not awful — is the part of software that keeps life humming along.