Hello from Edinburgh

Hi I’m Simon, an IT dinosaur in Edinburgh, Scotland and I’ve been trying out Logseq for about a week.

I didn’t really know what to expect from Logseq but wanted to see what it could do for me. I had moved away from Evernote and Notion in favour of Anytype because I’m reducing my cloud dependencies, preferring local-first solutions; but my daily workflow does feel clunky at times, so time to look for improvements.

I’m liking what I see so far. I don’t think Logseq will outright replace anything in my current toolkit, but I’m already thinking it’s going to my daily driver for new notes as it’s such a frictionless experience.

I really like being able to just jot something into my journal, maybe tag it, maybe not; and then go back later and do a bit of housekeeping. No having to decide on how to organise things up front and possibly lose my train of thought.

I seem to be solving problems that I didn’t know I had.

  • Rather than starting the day wondering where I left off yesterday, it’s all there in the journal rather than out of sight in a maze of project pages.
  • I’m no longer building up hundreds of open browser tabs with things I have on the go, leaving them there all week, and forgetting to go back to them. Just paste links under a few headings in my journal or under the relevant TODO items and close everything down, knowing I can come back to what I need later.
  • Same with browser bookmarks, rather than adding more and more by the day, not having any context around them, and never finding them again; just spend a few minutes pasting them in the journal with a few words and maybe link to a relevant project or task.
  • And I’m sleeping better because I feel less need to stay up and finish for fear of forgetting where I was; and once something is journalled properly it doesn’t play on my mind so much.

Having EVERYTHING as a bullet point did grate on me a bit. I do love bullets, my notes are usually full of them, but having them at every level was visually distracting. That said, I’ve managed to come up with a custom.css that I think is a nice fit for me, allowing a mix of headings and todo without bullets, and plenty of bullets for the details.

I like that everything is stored as markdown(ish) as it will give me the opportunity to write code to transform my notes into web pages, wiki site, repo documentation, etc; as parts of my graph become static and can be archived. I’m not sure what I’m going to think of Logseq-DB so maybe too soon to commit to this tool.

My next step is to dive into plugin development as I’ve already come up with a good sized wish-list that doesn’t seem to be satisfied by the existing selection in quite the ways that I would like.

4 Likes

A joy to read your intro!

I have the same impressions about Logseq as a multi-year user:)

Hey Simon! Welcome from a fellow newcomer to the community :waving_hand:

I’m Ioannis, developer from Greece — just introduced myself here too, so we’re basically neighbours in the timeline!

Your point about solving problems you didn’t know you had really resonates. That’s exactly the kind of tool Logseq turns out to be — you don’t fully appreciate it until you look back and realise how much mental overhead it’s quietly absorbed.

The journal-first approach caught me off guard too. I spent years building elaborate folder structures and project hierarchies, and somehow the answer was just… write it down today, sort it out later. It’s almost annoyingly simple once it clicks.

Plugin development sounds like a great next step — especially with 15+ years of dev experience behind you, I imagine your wish-list will turn into some genuinely useful contributions for the community. Would love to see what you come up with.

Looking forward to crossing paths here!