Software: Weekly Summary (October 20-26, 2025)

This week’s little pile of software writing felt like a mixed toolbox left on the kitchen table. Some pieces were shiny and new. Some were a bit greasy and honest. I would describe them as a set of tiny, useful arguments about how people use software — and how software, in turn, nudges people to change. To me, it feels like voices arguing about agency, simplicity, and where we put our attention. Read the posts if you want the fuller flavors, but here I’ll walk through the crumbs and the main bites.

The tactile itch: wanting to be a maker

matthew_brunelle writes with a kind of soft, rueful clarity about moving from building with hands to building with code. The post isn’t a tutorial. It’s a confession and a nudge. The writer misses the smell of sawdust, the wobble of a first prototype, the feeling of a finished object. They note how their childhood projects — little do-it-yourself things — gave a kind of confidence that software sometimes doesn’t give. I’d say the core idea is this: digital agency and physical agency feel different, and losing one feels like misplacing a tool you didn’t realize was important.

There’s regret in there. Not of career choices, exactly, but of a narrower skillset. A neat phrase in the piece points to remixing ideas — not copying, but building on stuff that already exists. That stuck with me. It’s like learning to cook by changing a recipe instead of always following it. And then there’s a subtle hope: that it’s possible to regain some of that hands-on agency, even late in the game. The post points at books and podcasts that nudged the author. It’s the kind of thing you half want to tuck into a pocket and carry out to the garage.

If you’ve ever felt the odd disconnect between what your code does and what your hands can make, this one will hit a spot. It hints at ways back into making. It’s not a map, more a compass.

The art of taking breaks and reading smarter

There’s a thoughtful edition from creativerly that reads like someone who’s just had their calendar flipped over by an AWS outage and then decided to think about how we work. It starts small — a delay in a newsletter — and grows into a meditation on breaks, attention, and how apps help or hurt reading.

Philipp (the newsletter voice) drops a couple of tools: Meco, a newsletter reader, and Hindsight, an RSS reader that tries to make news less frantic. The pitch is simple. If the internet feels like a crowded market, these apps are like a quieter stall where you can actually look at the olives without being elbowed. I would describe this idea as gentle: tools that reduce the friction of catching up instead of forcing you to sprint.

There are other threads here too — notes on the public’s perception of AI, how social media hits teens hard, and yes, the inevitability of anger as a social force. That last bit is written with a kind of resigned curiosity. You can feel the author thinking, mulling over how people react to news, how they share outrage, and what that does to a day’s attention. To me, it feels like someone pointing at the steam leaving a kettle and saying, “Don’t get scalded.” Small and practical advice sits beside bigger reflections.

If you care about how to read less and understand more, or how to keep a calmer head in an angry feed, this edition has a few useful pointers and app names to try.

Obsidian: more like a toolbox than a machine

The piece from Juha-Matti Santala argues something pleasantly obvious: Obsidian is as complex as you want it to be. That sounds banal on paper, but the post makes the point with useful, plain talk. Start with a blank note. Write. Add features later. You don’t need to drink the plugin Kool-Aid.

This is the kind of argument that reminds me of the first time someone shows you a Swiss Army knife. It looks complicated until you learn that most days you only use the knife and the corkscrew. Juha-Matti suggests trying Obsidian without plugins or influencer guides. You’ll either fall in love or realize you want a very specific attachment. Either is fine.

The post also nudges back at internet pressure: people feel they must replicate elaborate setups shown by power users. The writing asks you to resist that pressure, to find your own flow. Simple note-taking is underappreciated, the post says, and I’d say that’s true. There’s also a hint about the joy of slow refinement. Use it, then shape it.

Copilot on the command line: the tinkerer’s AI

Now we get into the tooling for people who live in terminals. Bart Wullems continues his exploration of the GitHub Copilot CLI. He digs into switching models, adding MCP servers, and even executing inline shell commands. It reads like a practical hike through features: useful signposts for folks who want their AI to sit on the same bench as their other dev tools.

What’s interesting is how much the discussion lands on customization. Copilot is not just a black box; it’s a set of switches and wires you can rearrange. Add an MCP server and it’s like bolting a new headlamp onto a bike. Switch models and you change the kind of help you get. Execute inline shell commands and Copilot becomes less of a suggestive friend and more of an assistant who can actually do small tasks.

The post is full of small instructions and tips. It’s the sort of weekend tinkering guide you’d read if you like the idea of an AI that lives next to your prompt, not above it. There’s also a hint that the ecosystem will keep expanding. If you like to customize, this is worth a look.

VirtualBox: the quiet maintenance that matters

Then there’s the maintenance note from Brian Fagioli about VirtualBox 7.2.4. It’s not sexy, and that’s the point. This is software doing the job of staying useful. The update adds initial support for Linux 6.18, fixes a VM Manager crash, improves NAT stability, and tidies up some Windows XP guest installation problems.

Updates like this are like getting new tires on an old car. Not flashy, but suddenly you don’t dread the rain. The post reads like a reminder that helpful software is often the software that keeps working rather than trying to dazzle. Oracle’s maintenance keeps VirtualBox relevant, especially for people who prefer something straightforward to overcomplicated commercial virtualization suites.

If you run older guests or care about kernel compatibility, this short note is worth a skim. It’s the kind of small news that quietly prevents a lot of headaches.

Life updates, writer rhythms, and slow progress

tom_mewett shares a personal patchwork: a life update, a new job, and some notes about writing cadence. He set a goal to write twelve pieces in 2025, and admits he’s behind. That admission is oddly comforting. It makes the whole project feel human again — like a garden where some beds are thriving and some are empty.

Tom’s email lists and links weave between psychotherapy, project management, AI, and software topics. The update feels like checking in with a friend who’s building a house, painting a room, and planting a tree in small batches. He hints at posts already written and some he wants to finish. Not a manifesto. Just the real-life accounting of time.

There’s a small lesson in that: steady, imperfect progress is still progress. The post doesn’t try to sell anything. It simply reports. If you like reading someone’s thinking-in-progress, it’s a good little stop.

Common threads: attention, agency, and customization

If you scan the week’s pieces you can see some repeating beats. They aren’t identical, but they hum together.

• Agency vs. abstraction. A couple of posts — the maker piece and the Obsidian note — talk about wanting more direct control. The maker piece wants the feel of a finished object. The Obsidian piece wants the freedom to keep things simple. Both are small rebellions against being told that complexity equals expertise.

• Tools that respect attention. creativerly and the Obsidian post both care about attention. One suggests tools that let you read without frenzy. The other suggests using fewer plugins and finding a simple workflow. There’s a shared itch: software should not constantly demand attention. It should serve the work.

• Maintenance matters. The VirtualBox update is a practical reminder: staying useful means fixing bugs and keeping compatibility. It’s less thrilling than a new feature release, but ask anyone who manages VMs and they’ll tell you it matters. I’d say we should talk more about keeping things running. A ship that sails reliably is better than one that has a parade at launch and then slowly sinks.

• Customization and extensibility. The Copilot CLI post and the Obsidian piece both celebrate slow, personal tuning of tools. Both push the idea that you don’t have to accept defaults, but also that you don’t need to overcomplicate things. It’s a push-pull: customize to fit your life, but don’t spin up a circus of plugins for the sake of appearing clever.

• Reading and mental health. Philipp’s newsletter gently insists that how we consume is as important as what we consume. That ties back to Tom’s life update, which quietly hints at the energy needed to write — and how easy it is to exhaust that energy if you let headlines and outrage run the day.

These themes aren’t decisive arguments. They’re small notes calling for a little more thought in how we build and use software.

Points of gentle disagreement and questions that stuck

Not everyone agrees, even quietly. There are small tensions worth noticing.

• Complexity is neutral or toxic? Juha-Matti says complexity is optional. Bart’s Copilot post invites complexity through customization. They both make good points, but they lead different places. One says start small and stay small if that serves you. The other says build a setup that fits the hard things you do. The tension is real: when is customization helpful, and when does it become a burden? No single answer — depends on what you do.

• Public perception of AI. creativerly notes the variance in public feelings about AI. Some people treat it like magic. Others treat it like a nuisance. The Copilot piece treats AI as a tool you bolt onto workflows. Those take different starting assumptions about what AI should be allowed to do. The question lingers: do we train people to use AI as a hand tool, or do we keep letting platforms dictate the shape of that hand tool?

• The enrichment of life vs. the efficiency of work. The maker’s longing is soulful. The Obsidian and Copilot posts are functional. They don’t contradict, but they put different values up front. Is software supposed to free up space for making, or to make the making itself more efficient? Both are sensible goals, but they can pull in different directions.

Those disagreements aren’t heated. They’re more like different notes in the same song. They make the reading more interesting.

Little practical tips worth trying

If you read just to take something home, here are a handful of things to try, each tied to a post.

• Want a calmer reading life? Try a different reader. Meco and Hindsight got name-dropped. Give one a week and see if your brain feels lighter.

• Using Obsidian? Start without plugins. I’d say keep one vault, write plain notes, and only add features when you miss them. It’s surprising how much you can do with a base setup.

• Work in a terminal? Peek at Copilot CLI options. If you like small automations, look into MCP servers and running inline shell commands. It changes how much the tool can do for you.

• Run VMs? Update the host or upgrade to VirtualBox 7.2.4 if you need Linux 6.18 support or the specific fixes mentioned. It’s one of those housekeeping things that saves time later.

• Feel stuck in a routine? Read a life update or two. Seeing someone else juggling job changes and writing goals is oddly motivating.

These are small. But then, so are a lot of good changes.

A few tangents and where they connect back

There’s a little cultural flavor in the pieces that comes through if you look for it. The maker piece whispers at that DIY, garage-hobby culture. The Obsidian and Copilot posts live in that developer, tinkerer groove. The newsletter edition is part tech-culture, part slow-living. The VirtualBox note is old-school sysadmin comfort. The life update is classic blogger personal updates.

If you squint, it’s like a Sunday market in a small town. The stalls sell different things — baked bread, a used tool, fresh flowers. You wander, buy one thing, and return home with the sense that life is made of many small, useful pieces. It’s not a big trade show. It’s personal.

That small-town feeling matters. It reminds you that not every software story is about disruption and funding rounds. Many of them are about staying useful, being gentler on attention, or making room for other skills.

Who might like these posts

• People who want to stop feeling overwhelmed by tools. The Obsidian piece and the newsletter both help with that.

• Terminal people who like customizing their environment. Bart’s Copilot piece is very much for you.

• Folks who miss doing things with their hands. Matthew Brunelle’s reflection scratches that exact itch.

• Admins and hyper-practical types. Brian Fagioli’s VirtualBox update is a small but important note for them.

• Readers who enjoy seeing a writer’s process. Tom Mewett’s update is a nice, real-life check-in.

If you’re any of those folks, these short reads are worth the time.

Little curiosities that kept me thinking

• The maker’s urge seems contagious. I kept thinking about whether software folks could start micro-projects that mix code and craft. Maybe a tiny lamp with firmware, or a little weather box that tweets. Not grand, not commercial. Just tactile.

• The idea of readers that reduce friction is appealing. A reader that helps you not panic about the news is more than convenience. It’s a tiny act of self-care. That made me curious about Hindsight’s design choices.

• Copilot running shell commands. That one kept looping in my head. It’s the difference between an assistant that scribbles suggestions and one that actually takes small, careful actions. That matters more than it sounds.

If you like poking around ideas, follow the links and see where they lead. Each post is a gateway to a slightly different set of practices.

Quick notes on style and voice in these posts

Most authors used plain language and short explanations. None tried to dress their ideas in jargon-heavy suits. That made the reading easier and a bit more human. A few of the posts were small and quietly practical. A few were reflective. It’s a good mix — the kind of week where you can hop from philosophy to a CLI tweak without feeling whiplash.

There’s a mild trend toward humility. Writers admit limits, small regrets, and the need to experiment. That’s welcome. It’s like watching someone at the bench, trying a new technique and shrugging if it doesn’t work. That tone makes the pieces feel trustworthy.

If you want to go deeper, each author’s page has the longer posts and links. The posts here work well as hooks.

If a single line of all these pieces had to be pinned on the refrigerator door, it might read: keep things useful, keep things simple when you can, and do the small maintenance that keeps the big stuff running. Or something like that. It’s a bit of a jumble, but the idea is useful. Read the original pieces if any of these sparks you — they’re short, and each one will give you a different kind of next step.