Michael Lenaghan

I’m not sure that The Composable Architecture’s compile-time benefits are worth the increased coupling. There’s some appeal to “sending a message” and not caring about who receives it. But maybe I’m just not thinking about it the right way…?

The Composable Architecture is quite interesting. An idea I’m exploring: it’s a bit like a more tightly coupled version of the actor model. Why “more tightly coupled”? Parents know about their children’s state and actions. The coupling yields better compile-time checking, better testing.

I spent some time the day before yesterday learning Logseq, and I spent some time yesterday thinking about how to adapt my note taking process to it. I have a plan. We’ll see how it goes.

Why look for Bear alternatives? The main problem is navigation between notes. There’s just too much friction — and the friction is getting in the way of habits I’d like to form. (You can link notes to each other; that’s not a problem. Jumping between entirely different notes — that’s a problem.)

I’ve been using Bear for notes. I started looking into alternatives (ia Writer, Ulysses) for… Reasons. And then I stumbled across Logseq…

I’m not convinced that this is the best way to use micro.blog. :-)

To succeed, a design has to anticipate the forces that will act on it. And possibly against it.

Design is about achieving goals. Goals always exist within some context. Identifying the correct context is part of the design process.

Design is about the use of judgement to achieve goals in the face of fundamental trade-offs.

Lots of thoughts, and little experience organizing them into full-length blog posts.

Consider this an experiment.

Does saying things, short things, out loud — does that help?

Does saying things, short things, out loud with minimal friction — does that help?

Let’s see.

Hello, world.