Skip to main content
Ryan Orban

Ryan Orban

Subject
13 entries

Collaboration

Bookmarks

  1. Aviator Runbooks: multiplayer AI coding via shared runbooks

    Aviator Runbooks makes AI coding multiplayer — reusable, shareable AI runbooks for teams that can automate PR reviews, standardize workflows, and integrate with existing AI tools. Specs become team-shared playbooks.

  2. Docs (suitenumerique): Open-Source Collaborative Editor

    Docs is an open-source collaborative text editor built with Django and React, designed as a Notion or Google Docs alternative for organizations that want self-hosted data ownership. MIT licensed, real-time with live cursors and offline editing, with optional AI writing assistance.

  3. tldraw: Infinite Canvas Drawing App

    tldraw is a tiny, open-source infinite canvas drawing app with a clean developer SDK — excellent for whiteboarding, diagrams, and embedding collaborative drawing into your own applications. Later gained prominence for its 'make it real' GPT-4V integration demo.

  4. Browsertech Index

    The Browsertech Index is a curated directory of companies and projects building browser-native collaboration technology — real-time sync, local-first software, CRDTs, and multiplayer features. A map of the technical ecosystem underlying tools like Figma, Linear, and Notion.

  5. Automerge: CRDTs for Collaborative Applications

    Automerge is a CRDT (Conflict-free Replicated Data Type) library for building collaborative applications that work offline and sync automatically without conflicts. The technical foundation of the local-first software movement.

  6. Remotion: Virtual Coworking for Distributed Teams

    Remotion was a virtual coworking platform for distributed teams — persistent video presence to replicate serendipitous office collisions. Later rebranded to Multi, pivoting toward remote pair programming and engineering collaboration.

  7. CRDTs: Conflict-free Replicated Data Types

    crdt.tech is the canonical reference hub for Conflict-free Replicated Data Types — the data structures that enable real-time collaborative editing without central coordination. The math guarantees eventual consistency even when network partitions split collaborators.

  8. How Do Data Science Workers Collaborate? Roles, Workflows, and Tools

    ACM survey of how data science workers actually collaborate in practice — finding distinct roles (data engineers, ML engineers, domain scientists, communicators) that rarely map to job titles, with coordination breakdowns at handoff points between roles. One of the few empirical studies of real data science team dynamics rather than idealized workflow diagrams.

  9. DAGsHub: GitHub for Data Science

    DAGsHub is a GitHub-like collaboration platform for data science — adding data versioning (DVC), experiment tracking, and model registry to the familiar git workflow. Addresses the pain point that standard git doesn't handle large data files or ML experiment metadata.

  10. Data is Ugly: Tales of Data Cleaning

    Ryan Orban's KDnuggets piece on data cleaning — arguing that teaching data scientists and engineers to understand each other's work is more important than any technical fix. The piece reframes data quality as an organizational problem, not just a technical one.

  11. Dat Project — Open Data Infrastructure

    Wired profile of Max Ogden and the Dat Project — a decentralized, versioned data sharing protocol designed to make scientific and public datasets as easy to share and update as code on GitHub. An ambitious vision for open data infrastructure that was ahead of its time.

  12. Floobits: Cross-Editor Real-Time Collaboration

    Floobits brought real-time multi-editor collaboration — like Google Docs for code — to Vim, Emacs, Sublime Text, and IntelliJ in 2013. A pre-cloud-IDE attempt to solve remote pair programming without forcing everyone onto the same editor.

  13. Git (and Github) for Data

    Open Knowledge Foundation's 2013 post on using Git and GitHub for data versioning — exploring whether the version control model that worked for code could work for datasets. An early articulation of what became the data-as-code movement.

All bookmarks