Software: Weekly Summary (September 29 - October 05, 2025)

There was a quiet hum this week in the software blogs. Not one loud trumpet. More like neighbours talking over the fence. Some whispers were about control — who gets to decide what runs on your machine. Some were about how we actually use software — the small, sweaty bits: calendars, notes, tutorials. And then there was the usual arguing about AI, demos, and whether those shiny things do real work or just look pretty at parties.

I would describe these posts as a handful of people trying to make sense of two things at once: what software does to our heads, and what it does to our lives. To me, it feels like the same fight playing out in different rooms. There are five or six themes that keep coming back. I’ll walk through them, and point at the posts that pushed those ideas. If you like poking at software with a cup of tea, you might find a thing or two to chew on. If nothing else, you’ll be able to follow the rabbit-holes yourself.

The creeping installs: Windows, Microsoft 365, and the little surprises

If your computer were a kitchen, this week felt like finding a new utensil in the drawer you didn’t ask for. Martin Brinkmann wrote a clear notice: Microsoft will start auto-installing companion apps for Microsoft 365 on Windows 11 in early October. People, Files, Calendar — little helpers meant to glue Copilot-ish features into everyday tasks. Home users will get them without a heads-up. Admins can turn it off if they know where to look.

It’s one of those things that feels small, until you notice the pattern. The company nudges the system a little bit every update, and a day later you’re wondering why your Start menu has a new face you didn’t pick. I’d say this move is like a neighbour fixing your fence without asking because they thought it would look nicer. Maybe they were right, maybe it’s annoying. Either way, it changes your yard without your say-so.

Then Chris Hoffman chimed in with something related but different. His piece on Windows 11 25H2 called it the smallest major update yet. Mostly housekeeping. A marker more than a makeover. Which is interesting because it shows Microsoft’s rhythm now: little pushes, monthly fixes, and an annual label slapped on top to keep release numbers tidy.

Together, those posts point to a larger question: convenience versus consent. People like features when they help. But people dislike surprises when they feel like someone else decided for them. It’s a tension we’ve all lived with — like letting someone borrow your car and them returning it with the radio preset to their favourite station.

Calendars, side projects, and the slow joy of small fixes

A lovely, low-key thread runs through the week about small tools that quietly improve life.

Zach Holman wrote about building calendars and introduced "Calendearing," a project that merges multiple calendar feeds into one neat subscription. It’s the kind of thing that is both obvious and slightly magical. You know like when you untangle a drawer and suddenly everything fits? That’s the feeling Zach describes. He’s been there — making small, practical stuff that saves friction.

Related in spirit, Nate pushed a case for no-code building with his "Lovable" platform. This is the more ambitious cousin to Zach’s small projects. Nate has decades of fiddling and he offers four practical tracks, prompts, demos — the whole kit. He’s blunt about limits. No-code isn’t a silver bullet. But he also says: now’s the time for non-coders to throw together prototypes that actually work. To me, that reads like permission. Like: go make a thing, even if it’s a bit rough.

And then there’s the quieter reflection by Adam Keys about the Things app. He uses it as a repository of notes and as a prompt for writing. He loves the tool and fears its evolution at the same time. That fear is familiar: you put your life into something and then worry a new version will break the ritual. Adam’s notes were not a how-to. They were a small worry and a small praise rolled together.

What ties Zach, Nate, and Adam is a love for tools that behave. Not flashy. Not corporate. Tools that do the job and let you get on with your life. It’s the appeal of a reliable kettle. It boils the water and doesn’t talk back.

LLMs, demoware, and the problem of pretty demos

The AI conversation, predictably, got louder. But instead of the usual breathless cheerleading, Charlie Meyer offered a tempered, slightly annoyed take: LLMs are the ultimate demoware.

Demoware is software that shines in demos and then collapses under real usage. LLMs, he says, shine. They can fake competence in a five-minute demo. They can answer prompts, write text, do weirdly human things. But the more you hand them real work — with edge cases, integration, scale — the more they start showing cracks. This is not an argument that LLMs are useless. It’s an argument that a demo isn’t the product. If you’ve ever watched an appliance demo where the cake comes out perfect every time, then gone home and had the oven smoke five minutes into your baking, you know the feeling.

That critique links nicely with Ben Follington, who wrote about interfaces as languages. Ben worries that swapping interfaces for LLMs might sacrifice fluency. A well-designed interface teaches you how to think with it, a bit like learning the grammar of a language. You get better with practice. If the interface is replaced by free-text LLM interaction, the shared grammar between user and machine can feel thinner. You might get a flexible conversation, but you lose the ability to build shared mental models and predictable habits.

So there’s this push-and-pull. LLMs are great for improvisation and demos. But they can also erode the design of predictable, learnable systems. It’s like replacing a clear street sign with someone who shouts directions in different accents each time. Helpful sometimes, maddening other times.

Developer experience: more than toys and speed

A practical strand of the week came from Marcel Hauri, who argued that developer experience (DX) is not just about better tools. He says a lot of teams focus on what’s measurable: faster builds, snappier IDEs, new laptops. Those are real things. But the bigger causes of developer misery are subtle: cognitive load, the way information flows, how decisions get made.

This is the backstage stuff. The parts of an orchestra you don’t see that make the music possible. Marcel is asking teams to widen their view. Documentation, clarity about ownership, predictable processes — those matter as much as the shiny toolchain.

There’s a human thread here. Adam’s fear of app changes, Zach’s joy at an elegant calendar merge, Marcel’s call for better flows — they all point to the same idea: software is mostly social. It’s about how people coordinate, remember, and pass things along. Tools help, but they don’t fix bad coordination.

Piracy, pricing, and turning a problem into a marketing trick

I didn’t expect to smile at a piracy post, but Herman's blog did something smart. He runs JustSketchMe, a 3D modeling tool. He noticed people searching for cracked versions. Most people would be annoyed. Herman decided to rank for those searches and offer a discount instead.

It worked. A small, pragmatic flourish. He turned a leak into a funnel. Not a deep moral treatise on piracy. Just a business move: make it easy for people to buy instead of stealing. It’s low theatre. It’s practical. It’s like putting a bowl of gum at the checkout so people don’t walk out chewing on a free sample.

This post is a reminder that indie dev work is messy. Pricing, marketing, piracy — they’re all part of the craft. Sometimes the best solution is slightly cheeky and slightly brilliant.

Tiny posts, small comforts: Cal Henderson’s notes

Two short notes from Cal Henderson stood out because of their tone. One was about trying Directory Opus Pro because Windows Explorer feels like it has declined. The other was a quiet praise for racket tutorials and their craft.

Both are the kind of tiny posts you tuck away. Cal’s thinking is not abstract. It’s: "Explorer used to be fine. Now I want something better." And: "These tutorials? They actually teach well." Little endorsements matter because they’re practical and lived. It’s like hearing a neighbor say, "This coffee shop still makes good espresso," and then trying it yourself.

Recurring patterns and the small contradictions

Reading these posts together, a few patterns stood out. I’ll list them in a messy little pile because that’s how my mind puts things together.

• Control versus convenience. Auto-installed apps are convenient for some. They’re an intrusion for others. People want features, but they also want to decide what lands on their machines.
• Demoware and real work. Shiny demos hide operational problems. LLMs are great at the first impression, not always the ongoing relationship.
• Interfaces as languages. When you teach people a design grammar, you build fluency. Replace that with something loose and you lose the shared grammar.
• Small tools do heavy lifting. Side projects, tiny utilities, and deliberate simplicity keep everyday life moving. They matter more than we often admit.
• DX is social. Fixing tools is not the whole job. Fixing how people talk, share, and decide matters just as much.
• Bootstrapped business moves matter. Herman’s piracy strategy is an example of real, scrappy commerce — not noble, not pretty, but effective.

Each item is a different way of saying the same thing: software is not just code. It’s politics, gestures, language, and habits. It’s also, very importantly, small rituals.

A few tangents — because I can’t help myself

There were a couple of delightful side notes that felt worth mentioning. Zach’s "Calendearing" made me think of cleaning out a junk drawer. You know the one with batteries, coupon clippings, and half a charger? It’s very satisfying when you pull everything out and it fits back neatly. That’s the joy Zach is working toward — small friction removed.

Ben’s "interfaces are languages" note made me think of learning a regional dialect. If you know the slang in a place, people nod at you differently. You get in quicker. Software that teaches you its slang makes you feel at home. But if someone replaces that with a translator who changes words every time, you lose the local rhythm.

Charlie’s demoware point is like watching a magician. Great trick on stage. But if you try the trick in your living room and it requires eight assistants, you feel cheated. Demos are theatre. They’re good at attracting attention. Real software is the kitchen where the meals actually get cooked.

And Marcel’s DX talk is like the plumbing in a house. Nobody thinks about it until it leaks. Then you spend a lot of money fixing things. Better to design the pipes properly. Less dramatic, but way more useful.

Where the disagreements sit

There were quiet disagreements. Not full-on clashes. More like different priorities.

• Some authors are forgiving of AI’s rough edges because the improvisational power is new and useful. Others are more skeptical, warning that demos and improvisation can mask deeper flaws.
• Some celebrate small side projects as the most meaningful work. Others worry about scale and long-term support — the usual tension between hobby-run tools and long-lived platforms.
• On the corporate side, people debate whether auto-installing apps is reasonable product evolution or a breach of trust.

None of this is resolved. It rarely is. But the arguments are practical: they’re about what people will tolerate in their daily workflows, and how software either fits into life or tries to own it.

Little recommendations — not full endorsements

If you’re skimming and want a quick map of who to read first, here’s a gentle nudge.

• Curious about the Windows noise? Start with Martin Brinkmann and then read Chris Hoffman. One tells you what’s changing; the other tells you whether it actually matters.
• Want to tidy up your life? Read Zach Holman. His calendar project is small, useful, and maybe something you’ll steal for yourself.
• Building without code? Nate lays out a practical path. He doesn’t promise magic, just momentum.
• Worried about demos? Read Charlie Meyer. He’ll make you squint at the shiny stuff and ask the hard questions.
• Love design and habits? Ben Follington will make you rethink the idea that interfaces are just pretty skins.
• Running a team? Marcel Hauri will prod you to look beyond tooling and focus on flow.
• Building a product and seeing pirates in the search results? Herman's blog has a small, cheeky playbook you might like.
• If you like small, real-world notes about tools and tutorials, skim Cal Henderson.

Each of these writers brings a different lens. Some are practical, some philosophical, some combative. That variety is actually useful. It’s like getting a recipe, a review, and a weather report all in one morning.

If you want to go deeper, the authors linked above are the best next stop. They don’t all hold hands and sing the same tune. They disagree, and that disagreement is where the interesting questions live. It’s worth following the thread that annoys you the most — that’s usually the one that will teach you something.

There’s a lot happening quietly.

Some weeks the blogs shout. This week they mostly muttered, and the mutters were practical. New apps popping up on your desktop. Little hacks that merge feeds. Platforms promising to make building easy. Warnings about demos that look better than the product. Reminders that developer experience is a human problem. A pirate trick that turned into a sale.

I’d say the strongest through-line is this: software still matters most where it meets people. Not the other way round. It’s about habits, trust, clarity, and the occasional bit of real craftsmanship. If you like stories about the small fixes that keep the lights on, these posts are your kind of thing. Read one, follow one link, and you’ll find a rabbit-hole that’s actually useful — rather than one of those shiny demo holes that lead nowhere.

If nothing else, you’ll come away with a feeling. A small, domestic comfort: the best software is the kind you barely notice until it saves your day. And when the software that shows up on your machine didn’t ask you first, well, that feeling changes fast.