When simple is more complicate.

As I was thinking about how to manage publishing obsidian notes to my digital garden, I was saying I wanted a “simpler” solution. That was partially true. Really, I wanted a simpler solution for me, the user, even if it meant a more complicated backend. The danger is that complicated workflows are easier to break.

This is true of other areas of life too. We try to make things “simpler” for ourselves but under the surface there is a sea of (hopefully) hidden complexity.

The danger, is those dependencies will fail and our system comes crashing down or grinds to a halt like a shipping cannel clogged by a boat. Simple solutions may end up needing more maintenance than the “complicated” option.

So perhaps a simple drag and drop isn’t the worst thing in the world after all.