Hacker Newsnew | past | comments | ask | show | jobs | submit | jevakallio's commentslogin

Marker | Product Engineer + Full Stack Engineer | Onsite/Hybrid, London, UK | Full-time | https://marker.page/jobs | £100K - £170K + equity Marker is an AI-native Word Processor – a reimagining of Google Docs and Microsoft Word.

We are a small, early stage team of experienced engineers, designers and product people, building the next generation user interface for people who care about writing, enhanced by collaborative workflows and augmented by human-centred agentic AI editorial assistants.

We're hiring for:

- Full stack engineer (React/TypeScript/Prosemirror/Cloudflare): https://marker.page/jobs/product-engineer

We are looking for:

- Senior, high-agency people with relevant experience in the technologies outlined in the role

- Full-time, based in London, UK or nearby (co-working some days of the week from our offices)

Massive bonus points for:

- If you've built text editors before and enjoyed it enough to do it again :)

- Interest in local-first, sync engines, CRDTs, and all that fun nerdy stuff

- Personal interest in the act, craft, and quality of written expression

- Experience and specialisation in one of the following: Design Engineering, Hybrid desktop applications (e.g. Electron), Hybrid mobile applications (e.g. Expo)

Reach out through https://marker.page/jobs and tell us a bit about yourself!


Marker | Product Engineer + Full Stack Engineer | Onsite/Hybrid, London, UK | Full-time | https://writewithmarker.com/jobs | £100K - £170K + equity

Marker is an AI-native Word Processor – a reimagining of Google Docs and Microsoft Word.

We are a small, early stage team of experienced engineers, designers and product people, building the next generation user interface for people who care about writing, enhanced by collaborative workflows and augmented by human-centred agentic AI editorial assistants.

We're hiring for:

- Frontend-focused full stack engineer (React/Tailwind/TypeScript, ProseMirror+Tiptap, Y.js): https://writewithmarker.com/jobs/product-engineer

- Backend-focused AI engineer (TypeScript, Cloudflare Workers, Durable Objects, CRDTs, Workflows, Prompt/Context engineering, Agent orchestration): https://writewithmarker.com/jobs/ai-engineer

We are looking for:

- Senior, high-agency people with relevant experience in the technologies outlined in the role

- Full-time, based in London, UK or nearby (co-working some days of the week from our offices)

Massive bonus points for:

- If you've built text editors before and enjoyed it enough to do it again :)

- Interest in local-first, sync engines, CRDTs, and all that fun nerdy stuff

- Personal interest in the act, craft, and quality of written expression

Reach out through https://writewithmarker.com/jobs and tell us a bit about yourself!


Foam author here. Yes it can. GitHub support is purely optional. I've improved the Getting Started guide to reflect this.


Foam author here!

Fiddly, yes. This is very early stage project and in need of polish.

Lacking backlinks, however? We actually got those, thanks to the VS Code Markdown Notes extension:

https://foambubble.github.io/foam/backlinking


Foam author here! I am very open to all suggestions in this area. Foam is a new project I built solely to my own requirements, but I'm actively seeking feedback on how to make it more broadly applicable as per our principles: https://foambubble.github.io/foam/principles

FWIW, subdirectory linking support is not far away. Work is being tracked on GitHub at the issue below, and I already have a WIP PR in the works: https://github.com/foambubble/foam-vscode/issues/8

If you have any more suggestions and ideas on how to improve Foam, feel free to open issues on GitHub!


That would seal the deal for me. I have tens of thousands of documents, notes, pictures etc. spread across hundreds of subdirectories. Foam looks extremely promising.


I just want to mention that I find the name absolutely great. Very fitting.


So far I'm loving your project. Will be closely following it as I move my notes into foam bubbles


Amazing! Please let me know in GitHub issues or Twitter DMs how you get along. This is a very early alpha release, keen to hear feedback at all levels!


Curious, unable to determine: is there a typeahead feature when inside wikilinks?


Yes, one of the markdown extensions handles that. It also allows “go to definition” on wikilinks


Foam author here! I'm not personally familiar with VSCodium, but contributions in this area would be extremely welcome as long as they don't prevent any of our Roadmap features working on VS Code!

Check out the contribution guide here: https://foambubble.github.io/foam/contribution-guide


Foam author here! I also don't like dependency on Jekyll, and over time I want to build a bespoke static site generator for Foam (possibly based on Gatsby) that's able to create a richer browsing experience.

Thanks for the idea! I have quite a few on the Roadmap already, and would love to hear more in GitHub issues

https://foambubble.github.io/foam/roadmap


Hi! Foam author here. We generate markdown references to bridge [[wiki-link]]s to work with Markdown tools. For the time being this is optimised for a) the editing experience in VS Code and b) the GitHub pages publishing pipeline, so it's more convenient to generate markdown links without the `.md` suffix.

See bottom of the file here for example: https://raw.githubusercontent.com/foambubble/foam/master/rea...

This means that for the time being links are broken in the GitHub markdown preview.

I'll look into getting this fixed, but not sure what the best way forward is.


I think the problem is that you're including these links in the README. New visitors expect all the links there to work, but they are broken.

If the README only included basic information and a link to the github pages, it would be easier to follow.

P.S. since I'm already typing, have you considered supporting semantic links, in addition to the regular ones? It will make the relationships between the pages clearer at a glance, and allow for better automation in the future. It might also help in visualization, for example you could toggle only specific relationships, to get a simpler graph of the information you care about.


Yes.


That's actually a good idea. Right now we pay the salary to you, and you can then donate it to a charity. It would be way more tax efficient to just skip the middle step.

Will take this under consideration!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: