3 ms·
Agreed, and here's a real example from a tiny startup: Clickup's web app is too damn slow and bloated with features and UI, so we created emacs modes to access
by versteegen 8mo ago
Agreed, and here's a real example from a tiny startup: Clickup's web app is too damn slow and bloated with features and UI, so we created emacs modes to access and edit Clickup workspaces (lists, kanban boards, docs, etc) via the API. Just some limited parts we care about. I was initially skeptical that it would work well or at all, but wow, it really has significantly improved the usefulness of Clickup by removing barriers.
- m_ke 8mo agoyou should try some markdown files in git
- ethbr1 8mo agoI think you completely missed the point of this thread: rolling ones own data model is a non-negligible cost.
- m_ke 8mo agoyou missed the boat on natural language being the new interface best orgs will own their data and have full history in version control so that it's easier for LLMs and humans to work with, not walled garden traps
- versteegen 8mo agoSure, depending on the particular product, having control and direct local access to the data would be desirable or deal breaker. But for this Clickup integration that's not so important to us (we can duplicate where necessary), while still using Clickup lets us use all the other features we can get via the web app. (The emacs mode includes an MCP server)
- ethbr1 8mo agoNatural language and LLMs as a core corporate data repository is insane.