Nice project for looking for pitchdeck references. Thanks for building and sharing it. I am curious about the tech behind it - are you doing OCR on images? The search is very responsive - it's definitely not elastic search, curious what index/search system are you using?
Glad it helps! There are 4 key steps that I took:
- Upscaling (using Upscayl[0])
- OCR (using tesseract[1])
- Indexing (using Algolia[2])
- Scaling the processing and running on AWS (Klotho[3] - our startup)
You are absolutely right that building a performant rich-text-editor for large document is indeed a very difficult problem. Mixing real-time collaboration put further challenges on api design and server processing. It's a whole different level of engineering challenges compare to building a performant CRUD web app...
I am wondering how your team does note taking in Linear - are you guys create one issue for each document? It doesn't support collaborative editing, right?
I should have been clearer. We essentially abandoned note taking and began storing all of our tasks in linear in a more granular way. We also all began participating in our issue management more, as it became sort of like the core of project management for us.
Looking at linear can give you a very clear picture of where the team is right now, what we’ve been doing, and even what we will be doing. Our issues are a place where we discuss implementation decisions, relate issues together in various ways to provide more clarity, link to external resources relevant to issues, and we organize them into projects and cycles as well.
The goal was to convert a process we already used into a more robust and useful process which might make note taking redundant. It has mostly worked.
Since we work in software and we’re a small team that’s intimately familiar with most of our code (or at least what the code does), tooling and practices like version control, idiomatic naming conventions, and supplemental commenting in code can helpfully serve as sufficient documentation for the team right now.
It’s a much different thing from real-time collaborative documents though and I do worry that as we grow, it won’t benefit less technical roles we’ll need to support the team. That’s where something like Notion becomes very compelling to me.
Policy is not my department, but technically speaking... I think a VPN service would probably be more effective running on AWS or Digital Ocean or whatnot.
A websocket connection between client and server is great for real-time apps, but for non real-time app, the unnecessary websocket connections create more work for devops -- specifically DNS and load balancer. Does/will Horizon support that clients only use the Collections API to get/set data without websocket (for real-time sync)?
Very interesting analysis!
There are about half positive and half native words about the new logo. But all words about classic logo are positive!
In any case, logo change doesn't matter much for big companies. People won't start or stop using your product because of logo change. I don't understand the rational behind the change.
It's a fascinating read! I released my app a while ago and found most users are Arab. I am eager to learn more about my customers and this article provides great insights.
