In a world of AI agents and real-time collaborative software like Figma and Notion, there's never been more reason to get live chat and commenting experiences into your application. The Cord SDK is an excellent choice for building from nothing to a 10/10 chat experience.
Our 5th event in the tech pub quiz series. This post documents the event and includes all the questions and answers. It was a wonderful evening of "Aha!" and "Oh... no...". Thanks to everyone who joined us!
Ah, the classic tale of "let's build a chat feature, it'll be easy," said every tech team ever. Spoiler: it's not. This post navigates the labyrinth that is the creation of a chat feature for SaaS applications, emphasizing that while chat may seem like a frivolous addition, it's actually the lifeblood of online collaboration.
TL;DR: For most teams, building with a chat SDK or chat NPM package is a much more efficient way to get to a great chat feature.
Engineering expert, Doug Li, talks about his experience working at OpenAI, and how it compares to his time at early-Facebook. Listen now to learn how he uses AI in his workflows, what his favorite developer tools are, the last thing he committed to the codebase, and how he predicts AI will evolve over the next decade.
In this post, we'll walk through the steps required to craft your own AI-powered chatbot. By the end of this post, you'll have all the core concepts required to understand how to turn your content into a knowledgeable and helpful chatbot.
Cord initially embraced the ShadowDOM for its WebComponents, aiming to prevent CSS interference between components and the host page. However, we quickly discovered its restrictive nature, which hindered customization and introduced a steep learning curve for developers. After experimenting with alternatives like CSS variables and CSS Parts, we've reverted to vanilla CSS classnames and open WebComponents, prioritizing developer experience and flexibility over strict encapsulation.
Listed below are the questions to our virtual Tech Pub Quiz #2 event. We'll continue hosting regular tech quizzes starting in January. For 2021 though, this is our final quiz. Big thanks to everyone who participated! Congratulations again to Josh, Alberto, and Tom for their strong team performance.
Whiteboard coding interviews are fantastic if you want to see a trustworthy, extemporaneous performance of technical problem solving and have a candidate who can show their skills this way. But what about when a great candidate can’t show their skills this way?
Real-time collaboration demands real-time infrastructure. Doing web-based, real-time interactions efficiently is a hard problem, but we've found a solution that reduces the number of open connections by a factor of 10 or more. TL;DR: We're multiplexing many tabs' network interactions via a single persist websocket.
We started Cord in 2020 in the middle of a pandemic. Our mission is building absolutely killer real-time and asynchronous collaboration features that work with any existing SaaS tools.
This idea sounds simple enough, but when you dig into what’s required to deliver this, you start to see a lot of unique constraints starting to emerge, which lead us to some very specific technical choices. This post breaks down our choices for the client side of our tech stack.
TL;DR: If you just want to know what tech stack we’re running here’s a quick run down. For more detail, see below. We’ve chosen TypeScript for both server and client; modern React with Hooks for the client UIs; GraphQL for the client-server interaction; Apollo on the client and server using WebSockets; React-JSS for managing styles; Webpack + Babel for transpilation.