June 2024 Summaries

AI is expected to significantly impact engineers, with predictions that it will make engineering 100 times more accessible and enjoyable. AI will automate mundane tasks such as dependency management, environment setup, and build systems, allowing engineers to focus on high-impact tasks like writing code and creating. This shift will also lead to an increase in demand for engineers, as the cost of adding new features drops dramatically and companies need to rapidly develop and iterate on their software. Furthermore, AI is expected to make every engineer a tech lead, managing teams of AI agents and focusing on strategic thinking, design, and communication. Ultimately, this future holds incredible possibilities for innovation and creativity, making it an amazing time to be an engineer.

This week at Jam, the team is live from Config2024, one of the world's best product design conferences, where they had free tickets courtesy of their investor Figma. They're discussing community learnings and sharing unfiltered conversations about building their startup, with no fluff or pretenses. The episode covers topics such as admiring the scale of the conference, meeting people from admired companies, learning about Figma's new slides product and a demo of Dot, an AI assistant, touring Config swag, reactions to Figma Slides, and meeting famous product educators, among other highlights.

Jam + LogRocket has launched with the addition of even more debug data auto-included in Jam, making it easier for developers to fix issues by providing a single link that includes all necessary technical context and application data. The integration brings together the full view of a bug, including replaying the issue, sending developers a link with context, and LogRocket sessions providing usage information. No set-up is required, and users don't need to write any code to get started, making it a convenient solution for software teams to save time and frustration in debugging and fixing issues.

This week at Jam, we're deep into building the next iteration of Jam AI, a project that involves incorporating Artificial Intelligence (AI) to improve the startup's operations. The latest demo shared by engineer Rui has sparked interest in bringing him on the podcast to discuss their approach and challenges in building this AI system. On the episode, they delve into how to limit the input space for building reliable AI, explore tools and experiments for AI reliability and infrastructure, and compare with other approaches such as Facebook's bug fixing methods. The conversation is an unfiltered discussion about real decisions, moments, and challenges faced by Jam engineers in building their startup, providing a unique insight into the engineering process at Jam.

We're sharing Jam's board deck template, a tool that communicates the health and progress of a startup to its board members, providing a clear snapshot of where the company stands, highlighting key metrics, and outlining future goals. The template has been instrumental in growing Jam's startup and is structured into 35 slides, each section designed to provide maximum clarity and insight. The deck includes an executive summary, usage update, revenue update, growth update, product update, financials, team update, housekeeping, and final thoughts and discussion sections. To create a comprehensive board meeting deck, founders should start with user feedback, break down metrics clearly, use visual storytelling, provide financial transparency, and leave room for discussion. Using this structure has helped Jam's startup keep its board meetings focused, informative, and engaging.

Building Jam | Ep. 8 The Board Meeting` The founders of Jam, Dani and Irtefa, are preparing for a board meeting by analyzing data to gain insight into the startup's performance. In this episode, they discuss their approach to the board meeting, what gets voted on, and how it influences their decision-making process. They also share their experiences and challenges in building the company, offering valuable lessons for founders of other startups. The conversation is unfiltered and real, providing a unique perspective into the inner workings of Jam's leadership team.

The story of the world's first software bug is not about a moth found in a logbook at Harvard, but rather about Grace Hopper and her team discovering an actual computer bug while working on the Mark II Aiken Relay Calculator. In 1947, they found a problem with the machine that required manual tracing through miles of wiring to pinpoint the issue. The team documented every detail in a comprehensive logbook, ensuring they could reference and learn from each issue. This meticulous approach was effective but time-consuming and annoying. Hopper did not discover the first "computer bug," which actually occurred earlier in history, with Ada Lovelace writing the world's first computer program in 1843 that contained a typo, or "bug." The future of debugging is still evolving, with auto-included dev tools and automatic steps to reproduce in every bug report.

The podcast episode "Building Jam | Ep. 7 Everything Feels Important" discusses the challenges and decisions made by the team at Jam while building their startup, with a focus on new tactics, channels, and live onboardings to create a seamless experience for users. The conversation touches on various topics such as onboarding new enterprise customers, creating engaging content, and prioritization strategies, offering insights into the team's approach to problem-solving and growth.

The latest development tool, Jam, has been updated with the integration of Fullstory, allowing developers to debug and fix issues in one tab. The update brings together various tools and workflows into a single platform, enabling faster debugging and providing a more comprehensive view of bugs. This is part of the mission to simplify the debugging process for developers by connecting all necessary tools and apps in one place. The integration requires no setup or code changes, making it easy for developers to access Fullstory's session data within Jam. With this update, developers can report bugs with Jam and instantly see Fullstory's customer behavior and analytics insights. The goal is to provide the one tab that developers need to open to debug and fix issues, streamlining the debugging process.