Engineering - Jam.dev blog
Behind the scenes of how we built the first magic link for bug reports!
Jam engineers: Max, Aidan, and Rui get into the technical details of implementing the tldraw library.
Highlights from AI DevTools Night with Jam, Cloudflare & Sourcegraph.
Dig into all the technical details with us, and the challenges of doing a complete refactor of our browser extension + rolling it out to 150k users.
Jam, Flox, Microsoft for Startups & GitHub for Startups hosted 100+ technical founders in SF for AI demos. Here are the live demo recordings.
Meet Jam's new collection of open-source & ad-free data conversion tools.
In 10 years, I bet there will be 100x more engineers than now. Here's 5 big predictions on how AI will impact engineers.
GraphQL strategies to help you manage interactions between evolving systems more effectively.
Discover Zoo's breakthrough in CAD: time traveling debuggers and custom KCL. Talk by Adam Chalmers, engineer at Zoo.dev.
Read about our journey to improve local development ergonomics and how we arrived at Tilt.
This probably sounds a bit crazy. Or, you may have forgotten what a network stack is.
But before you dismiss the concept of a layered protocol stack inside of a browser extension as ravings by a madman, or a concept too convoluted to bother understanding, let me provide some context.
Sometimes replicating your full stack environment locally is pretty hard. Orchestrating lots of microservices in a development environment and sharing demos can be tricky.
Making incremental changes and shipping fast is ideal. This is our default workflow for the vast majority of development but for some cases where we want.
At Jam, we initially chose GraphQL for our product due to its flexibility and ability to build lightweight and fast front-ends. However, as we’ve scaled, we have encountered challenges with GraphQL related to maintainability, debugging and monitoring.
Even within our engineering team, the jury is out on whether.
We built Jam to help you file bugs. But we’re not perfect! Here’s a quick teardown on one of our own bugs—a bug that affected some users during their first Jam install.
We’re writing this because we’re imperfect, and we think it’s a great.
This is the first part of an upcoming series documenting our work in migrating databases from MongoDB to Postgres. We did this with zero incidents, having planned the changes over 6 weeks, and executed them in under an hour. We’d love to share our thoughts on how we approached.
If you have a SaaS product that you want to embed into other platforms like Notion, you might find yourself struggling with the limitations of existing embed options. The good news is, you can create your own custom embeds by creating an oEmbed API using Cloudflare Workers. In this post,
At Jam, our mission is to help teams ship high-quality software, faster. We do this by making it easier to communicate about and fix bugs. Our tool makes sure all the information engineers need to debug a bug, like network requests, console logs, screenshots, videos, and device, OS, and.
In the earlier days of Jam engineering, we did a few things that don’t scale. As one of those many things, we manually submitted this developer Chrome extension to the Chrome Web Store. This meant whenever we wanted to release newer versions of our extension, one of our engineers.
There are tons of tools out there to help developers be more productive and simplify workflows. But, not all are made equal. The devtools landscape is shifting from utilitarian products, to productivity tooling that not only works, but is easy to use and designed with craftsmanship. In short, the developer.