August 2018 Summaries

The Checkly web app's performance was significantly improved after a half-day of optimization efforts, resulting in a Lighthouse score of 100 from an initial score of 34. The optimizations focused on reducing bundle size by selectively importing modules and libraries, and implementing code splitting to reduce the amount of JavaScript loaded at each route change. These changes were made possible with tools like Bundle Analyzer and Webpack's BundleAnalyzerPlugin, which helped identify areas for improvement. By targeting specific areas, optimizing, measuring results, and iterating, the team was able to achieve a substantial performance boost, resulting in faster times to first paint and better overall user experience.

The development of Puppeteer Recorder, a Chrome extension that records browser interactions and generates a Puppeteer script, involves several key components including the `manifest.json` file, background scripts, content scripts, popup UI, options page UI, and the Chrome global. The Chrome global provides access to storage, messaging, and state management, but using it can be tricky due to its quasi-embedded nature. State is persisted using the native chrome.storage API, with different components handling state in varying ways. Debugging requires multiple Dev Tools windows, while building involves transpiling ESx, compiling SASS/SCSS, and testing with Jest or Puppeteer. Distributing the extension to the web store involves packaging code into a zip file, creating a Chrome Web Store Developer account, and providing images and a video.

The author of the text, Checkly, removed the "beta" tag after launching a private beta period, which involved several challenges and learnings. The company initially integrated Stripe for payment processing, but faced difficulties with its API and pricing strategy. To acquire early customers, Checkly offered discounts in exchange for testimonials, while also monitoring user feedback to improve features. However, this led to the "one more feature" trap, where the author added new features despite the need for balance between price and value. The company had to navigate the buy vs. build dilemma, choosing to use existing services like Heroku and GitHub instead of building their own solutions. Additionally, Checkly experienced an acquihire distraction, but ultimately parted ways with a potential acquirer on good terms. After the beta period, the author's role shifted from 80% engineering to 80% marketing and sales, as they focused on acquiring more launching customers through organic and paid channels.