Devrelshow Episode 13 - Baruch Sadogursky From Gradle ![rw-book-cover](https://i.ytimg.com/vi/IjtQZFP2QTA/maxresdefault.jpg?v=65ef5d96) [[3. Resources/Readwise/Full Document Contents/Articles/Devrelshow Episode 13 - Baruch Sadogursky From Gradle|Full Document Contents]] ## Document Notes --- tags: #DevRel #DeveloperRelations #Automation #OpenSource - DevRel - DeveloperRelations - OpenSource Author: Baruch Sadogursky Source: YouTube/DevRel Show Reference: [YouTube Transcript](https://www.youtube.com/watch?v=IjtQZFP2QTA) date created: 2024-09-15 14:30 --- # Title: Interview with Baruch Sadogursky: Developer Relations, Gradle, and Open Source Automation ## Table of Contents: - [[#📝 Summary:]] - [[#📖 Main Content:]] - [[#🗒️ Notes:]] - [[#📖 References:]] - [[#🗣️ Paraphrase:]] - [[#📰 Newsletter:]] - [[#✅ Action Items:]] - [[#🧪 Hypotheses:]] - [[#📊 Methodology:]] - [[#❓ Questions:]] - [[#🔮 Future Research:]] - [[#💡 Implications:]] - [[#🧠 Learning Styles Assessment:]] - [[#📊 Accessibility Assessment:]] - [[#🌍 DEIB Assessment:]] - [[#✅ Logical Validity]] - [[#🔍 SEO Evaluation]] - [[#🎯 Conclusion]] ## 📝 Summary: In this insightful interview, Baruch Sadogursky, Principal Developer Advocate at Gradle, discusses his career in DevRel, his experiences working with startups, and the challenges of developer relations. He highlights how open-source tools like Gradle and its premium product Gradle Dev Velocity optimize developer productivity, especially through automation, predictive test selection, and build caching. ## 📖 Main Content: Baruch Sadogursky's journey in developer relations has spanned over a decade. He has seen the evolution of the field, from small companies like JFrog to large-scale enterprises. His focus has been on improving the developer experience and streamlining workflows through automation tools. One of the key topics of the interview is Gradle Dev Velocity, a premium product by Gradle designed to enhance developer productivity by optimizing builds, running predictive test selections, and caching builds effectively. Baruch also emphasizes the importance of recognition within the developer relations industry, noting that supporting various departments such as sales, marketing, and HR is critical for DevRel success. ### 🗒️ Notes: - **DevRel**: A multi-faceted role that touches on product, marketing, HR, and even sales. Baruch emphasizes the importance of collaboration across departments. - **Gradle Dev Velocity**: A premium product that offers developers predictive test selection and build caching to significantly reduce build times and improve developer productivity. - **Predictive Test Selection**: Using machine learning, this feature identifies which tests are most likely to fail based on code changes and skips tests that will likely pass, saving time. - **DevRel Burnout**: Baruch discusses burnout in DevRel, particularly during the COVID-19 pandemic when in-person conferences were replaced with virtual events, removing the real-time feedback that motivates many in the field. - **Recognizing Contributions**: Baruch mentions the need for recognizing contributions beyond traditional metrics, such as developer advocacy's role in sales and marketing impact. ## 📖 References: - Sadogursky, B. (2024). Developer Relations and Gradle Automation. DevRel Show. Retrieved from [YouTube](https://www.youtube.com/watch?v=IjtQZFP2QTA). - Gradle Dev Velocity: [Gradle Website](https://gradle.com/products/gradle-enterprise/) ## 🗣️ Paraphrase: 1. “Developer relations is not just about advocacy or speaking at conferences, it's about building meaningful connections across all departments in an organization. Whether it's sales, HR, or marketing, DevRel can contribute to a company's success in more ways than just product feedback." 2. “Predictive test selection uses machine learning to predict which tests will fail based on changes to the codebase. This helps developers save valuable time by skipping tests that are predicted to pass.” ## 📰 Newsletter: 🚀 **Developer Relations and Automation at Gradle** In this exciting DevRel Show episode, Baruch Sadogursky, Principal Developer Advocate at Gradle, shares his experiences in developer relations and how Gradle’s Dev Velocity product is transforming the way developers work. Gradle Dev Velocity uses predictive test selection and build caching to optimize build times, saving developers time and improving productivity. Baruch also touches on the importance of balancing developer advocacy with contributions to sales, marketing, and HR. Watch the full interview [here](https://www.youtube.com/watch?v=IjtQZFP2QTA). 🌍 ## ✅ Action Items: - Investigate how predictive test selection can optimize workflow for WordPress plugin development. - Explore the potential for implementing DevRel practices across various departments at GoDaddy, including HR and sales. - Consider the impact of open-source automation tools like Gradle in reducing build times and increasing overall developer productivity. ## 🧪 Hypotheses: - Predictive test selection can reduce build time by at least 50% for large WordPress projects. - Collaboration between DevRel and HR can increase developer retention and improve internal community engagement. ### 📊 Methodology: - Conduct a case study with a team using predictive test selection in a large open-source WordPress project. - Use qualitative interviews with HR and DevRel teams to assess the impact of collaboration on developer engagement. ### ❓ Questions: - How can DevRel teams further support sales departments without becoming salespeople? - What are the long-term impacts of using machine learning for predictive testing in continuous integration workflows? ### 🔮 Future Research: - Investigate the role of machine learning in further automating the developer experience, especially within open-source ecosystems. - Explore the psychological aspects of developer burnout and ways to support mental health in DevRel roles, especially during virtual events. ### 💡 Implications: - The future of DevRel is closely tied to automation tools like Gradle Dev Velocity, which will save developers time and improve their overall productivity. - As machine learning continues to develop, predictive tools will likely become a standard part of the continuous integration workflow. ### 🧠 Learning Styles Assessment: 1. **Visual Learners (Spatial)**: - **Present**: The Gradle interface and dashboards provide visual aids for understanding build processes. - **Improve**: Include infographics or videos explaining how predictive test selection works. 2. **Aural Learners (Auditory-Musical)**: - **Present**: The interview provides auditory content. - **Improve**: Offer an audio version of Gradle documentation for developers on the go. 3. **Verbal Learners (Linguistic)**: - **Present**: Detailed explanation of Gradle Dev Velocity and test selection processes. - **Improve**: Include more case studies and blog posts. 4. **Physical Learners (Kinesthetic)**: - **Improve**: Incorporate hands-on exercises for setting up Gradle Dev Velocity in real-world projects. 5. **Logical Learners (Mathematical)**: - **Present**: The discussion around machine learning in test selection appeals to logical learners. - **Improve**: Provide additional data points and analytics. 6. **Social Learners (Interpersonal)**: - **Improve**: Encourage collaboration through forums or discussion groups around Gradle implementation. 7. **Solitary Learners (Intrapersonal)**: - **Improve**: Include reflection prompts to encourage developers to assess their own productivity gains. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Gradle documentation and Dev Velocity interfaces should be compatible with screen readers. - **Keyboard Navigation**: Ensure Gradle's website and tools are navigable via keyboard for users with mobility impairments. - **Contrast and Readability**: Ensure that dashboards have high contrast for readability. - **Text Resizing**: Ensure content can be resized without breaking layout. ### 🌍 DEIB Assessment: - **Cultural Relevance**: The content is broadly applicable but could include more examples from diverse de > [!note]+ Document Notes > tags: [DevRel, DeveloperRelations, Automation, OpenSource] > - DevRel > - DeveloperRelations > - OpenSource > Author: Baruch Sadogursky > Source: YouTube/DevRel Show > Reference: [YouTube Transcript](https://www.youtube.com/watch?v=IjtQZFP2QTA) > date created: 2024-09-15 14:30 > > # Title: Interview with Baruch Sadogursky: Developer Relations, Gradle, and Open Source Automation > <!-- deep-read:sections start --> ## Table of Contents: 1. [📝 Summary](#-summary) 2. [📖 Main Content](#-main-content) 3. [🗒️ Notes](#-notes) 4. [📖 References](#-references) 5. [🗣️ Paraphrase](#-paraphrase) 6. [📰 Newsletter](#-newsletter) 7. [✅ Action Items](#-action-items) 8. [🧪 Hypotheses](#-hypotheses) 9. [📊 Methodology](#-methodology) 10. [❓ Questions](#-questions) 11. [🔮 Future Research](#-future-research) 12. [💡 Implications](#-implications) 13. [🧠 Learning Styles Assessment](#-learning-styles-assessment) 14. [📊 Accessibility Assessment](#-accessibility-assessment) 15. [🌍 DEIB Assessment](#-deib-assessment) 16. [✅ Logical Validity](#-logical-validity) 17. [🔍 SEO Evaluation](#-seo-evaluation) 18. [🎯 Conclusion](#-conclusion) ## 📝 Summary: In this insightful interview, Baruch Sadogursky, Principal Developer Advocate at Gradle, discusses his career in DevRel, his experiences working with startups, and the challenges of developer relations. He highlights how open-source tools like Gradle and its premium product Gradle Dev Velocity optimize developer productivity, especially through automation, predictive test selection, and build caching. ## 📖 Main Content: Baruch Sadogursky's journey in developer relations has spanned over a decade. He has seen the evolution of the field, from small companies like JFrog to large-scale enterprises. His focus has been on improving the developer experience and streamlining workflows through automation tools. One of the key topics of the interview is Gradle Dev Velocity, a premium product by Gradle designed to enhance developer productivity by optimizing builds, running predictive test selections, and caching builds effectively. Baruch also emphasizes the importance of recognition within the developer relations industry, noting that supporting various departments such as sales, marketing, and HR is critical for DevRel success. ### 🗒️ Notes: - **DevRel**: A multi-faceted role that touches on product, marketing, HR, and even sales. Baruch emphasizes the importance of collaboration across departments. - **Gradle Dev Velocity**: A premium product that offers developers predictive test selection and build caching to significantly reduce build times and improve developer productivity. - **Predictive Test Selection**: Using machine learning, this feature identifies which tests are most likely to fail based on code changes and skips tests that will likely pass, saving time. - **DevRel Burnout**: Baruch discusses burnout in DevRel, particularly during the COVID-19 pandemic when in-person conferences were replaced with virtual events, removing the real-time feedback that motivates many in the field. - **Recognizing Contributions**: Baruch mentions the need for recognizing contributions beyond traditional metrics, such as developer advocacy's role in sales and marketing impact. ## 📖 References: - Sadogursky, B. (2024). Developer Relations and Gradle Automation. DevRel Show. Retrieved from [YouTube](https://www.youtube.com/watch?v=IjtQZFP2QTA). - Gradle Dev Velocity: [Gradle Website](https://gradle.com/products/gradle-enterprise/) ## 🗣️ Paraphrase: 1. “Developer relations is not just about advocacy or speaking at conferences, it's about building meaningful connections across all departments in an organization. Whether it's sales, HR, or marketing, DevRel can contribute to a company's success in more ways than just product feedback." 2. “Predictive test selection uses machine learning to predict which tests will fail based on changes to the codebase. This helps developers save valuable time by skipping tests that are predicted to pass.” ## 📰 Newsletter: 🚀 **Developer Relations and Automation at Gradle** In this exciting DevRel Show episode, Baruch Sadogursky, Principal Developer Advocate at Gradle, shares his experiences in developer relations and how Gradle’s Dev Velocity product is transforming the way developers work. Gradle Dev Velocity uses predictive test selection and build caching to optimize build times, saving developers time and improving productivity. Baruch also touches on the importance of balancing developer advocacy with contributions to sales, marketing, and HR. Watch the full interview [here](https://www.youtube.com/watch?v=IjtQZFP2QTA). 🌍 ## ✅ Action Items: - Investigate how predictive test selection can optimize workflow for WordPress plugin development. - Explore the potential for implementing DevRel practices across various departments at GoDaddy, including HR and sales. - Consider the impact of open-source automation tools like Gradle in reducing build times and increasing overall developer productivity. ## 🧪 Hypotheses: - Predictive test selection can reduce build time by at least 50% for large WordPress projects. - Collaboration between DevRel and HR can increase developer retention and improve internal community engagement. ### 📊 Methodology: - Conduct a case study with a team using predictive test selection in a large open-source WordPress project. - Use qualitative interviews with HR and DevRel teams to assess the impact of collaboration on developer engagement. ### ❓ Questions: - How can DevRel teams further support sales departments without becoming salespeople? - What are the long-term impacts of using machine learning for predictive testing in continuous integration workflows? ### 🔮 Future Research: - Investigate the role of machine learning in further automating the developer experience, especially within open-source ecosystems. - Explore the psychological aspects of developer burnout and ways to support mental health in DevRel roles, especially during virtual events. ### 💡 Implications: - The future of DevRel is closely tied to automation tools like Gradle Dev Velocity, which will save developers time and improve their overall productivity. - As machine learning continues to develop, predictive tools will likely become a standard part of the continuous integration workflow. ### 🧠 Learning Styles Assessment: 1. **Visual Learners (Spatial)**: - **Present**: The Gradle interface and dashboards provide visual aids for understanding build processes. - **Improve**: Include infographics or videos explaining how predictive test selection works. 2. **Aural Learners (Auditory-Musical)**: - **Present**: The interview provides auditory content. - **Improve**: Offer an audio version of Gradle documentation for developers on the go. 3. **Verbal Learners (Linguistic)**: - **Present**: Detailed explanation of Gradle Dev Velocity and test selection processes. - **Improve**: Include more case studies and blog posts. 4. **Physical Learners (Kinesthetic)**: - **Improve**: Incorporate hands-on exercises for setting up Gradle Dev Velocity in real-world projects. 5. **Logical Learners (Mathematical)**: - **Present**: The discussion around machine learning in test selection appeals to logical learners. - **Improve**: Provide additional data points and analytics. 6. **Social Learners (Interpersonal)**: - **Improve**: Encourage collaboration through forums or discussion groups around Gradle implementation. 7. **Solitary Learners (Intrapersonal)**: - **Improve**: Include reflection prompts to encourage developers to assess their own productivity gains. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Gradle documentation and Dev Velocity interfaces should be compatible with screen readers. - **Keyboard Navigation**: Ensure Gradle's website and tools are navigable via keyboard for users with mobility impairments. - **Contrast and Readability**: Ensure that dashboards have high contrast for readability. - **Text Resizing**: Ensure content can be resized without breaking layout. ### 🌍 DEIB Assessment: - **Cultural Relevance**: The content is broadly applicable but could include more examples from diverse development teams globally. - **Inclusive Language**: The interview uses inclusive language, avoiding jargon and complex terms. - **Neurodiversity Support**: Gradle should consider offering tutorials and content that cater to neurodiverse individuals. - **Representation**: More diversity in interviewees would improve the scope of the discussion. - **Psychological Safety**: Provide resources for mental health in developer relations, especially regarding burnout. ### ✅ Logical Validity: - **Sound Reasoning**: The interview builds on practical examples and real-world applications. - **Potential Fallacies**: None observed. The discussion is logically coherent with no ad hominem attacks or irrelevant tangents. ### 🔍 SEO Evaluation: - **Keywords**: "Developer relations," "Gradle Dev Velocity," and "predictive test selection" are well integrated. - **Meta Description**: The interview’s meta description is concise and keyword-rich. - **Title Tag**: The title includes relevant keywords for search engine optimization. - **Headers**: Headers are appropriately used, with keywords present. - **Content Length**: The content is appropriately long for a technical interview. - **Internal and External Links**: Gradle’s product page is well linked, but more internal linking to related resources would enhance SEO. ## 🎯 Conclusion: Baruch Sadogursky offers a rich perspective on the evolving role of DevRel, the power of automation in development, and the future of developer productivity tools like Gradle Dev Velocity. His insights emphasize the value of collaboration across departments and the importance of balancing the technical and interpersonal aspects of developer advocacy. Short Summary for [devrelshow episode 13 - Baruch Sadogursky from Gradle](https://www.youtube.com/watch?v=IjtQZFP2QTA) by [Merlin](https://merlin.foyer.work/) Title: Baruch Sadogursky from Gradle - Episode 13 of devrelshow with Fredéric Harper [00:00](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=0) Technical issues caused delay in show recording [02:40](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=160) Excited to have Baruch Sadogursky on the show [07:06](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=426) Baruch Sadogursky's experience doing a roadshow in Canada for cloud native meetups [09:35](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=575) Baruch advises startups and advocates for developer productivity at Gradle. [15:07](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=907) Real-time feedback is essential for avoiding burnout during online conferences. [17:40](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=1060) Discussion on burnout prevention and feedback at in-person conferences. [21:25](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=1285) Developer advocacy is part of a wider umbrella called developer relations. [23:33](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=1413) Building a developer relations team and strategy [27:57](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=1677) Principal Developer Advocate role explained [30:06](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=1806) Importance of measuring developer relations [35:01](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=2101) Speaking at Shopify, a small example of the principal. [37:04](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=2224) Developer relations is at the center of everything [41:18](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=2478) Gradle history and beginnings [43:18](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=2598) Gradle has expanded capabilities beyond JVM to support various languages like Scala and provides advanced features like build caching [48:12](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=2892) Two solutions for highlighting and reusing important book content. [50:16](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=3016) Gradle offers build scans for comprehensive build insights [55:10](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=3310) Gradle provides detailed feedback on test failures [57:49](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=3469) Comparing and analyzing multiple builds for insights [1:02:58](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=3778) The framework shows high accuracy in predictive text selection. [1:05:26](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=3926) Using predictive test selection to save local build times [1:09:44](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=4184) Baruch and Fred discuss their friendship and connection on social media. --------------------------------- Detailed Summary for [devrelshow episode 13 - Baruch Sadogursky from Gradle](https://www.youtube.com/watch?v=IjtQZFP2QTA) by [Merlin](https://merlin.foyer.work/) Title: Baruch Sadogursky from Gradle - Episode 13 of devrelshow with Fredéric Harper [00:00](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=0) Technical issues caused delay in show recording - Moved Streamyard account causing missed countdown music - Multiple postponements due to host being sick [02:40](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=160) Excited to have Baruch Sadogursky on the show - Baruch and the host have been following each other on Twitter for a few years but have never met in person. - They discuss the fun of sharing and potentially mispronouncing names at Starbucks. [07:06](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=426) Baruch Sadogursky's experience doing a roadshow in Canada for cloud native meetups - Baruch recalls the cold winter experience in Canada during the roadshow, appreciating the opportunity to see and feel snow after living in a warm climate since the age of 12. - Baruch shares his experience engaging with others on Twitter and his involvement in developer relations for over 12 years, including his work with JFrog and their successful IPO in 2020. [09:35](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=575) Baruch advises startups and advocates for developer productivity at Gradle. - Baruch advises startups on how to approach developers and make their products more developer-friendly. - Baruch joined Gradle to advocate for better developer productivity and to bring back feedback from developers. [15:07](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=907) Real-time feedback is essential for avoiding burnout during online conferences. - Offline conferences provide live feedback and interaction, which helps in boosting motivation and avoiding burnout. - The lack of real-time feedback during online conferences can lead to increased stress and potential for burnout. [17:40](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=1060) Discussion on burnout prevention and feedback at in-person conferences. - Exploring the book 'The Secret of Unlocking Distress Cycle' - Importance of in-person conferences for feedback and personal connection. [21:25](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=1285) Developer advocacy is part of a wider umbrella called developer relations. - Developer advocacy includes a variety of people, such as introverts and those who prefer not to travel. - Working as an external advisor for startups involves providing guidance and support for developer relations. [23:33](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=1413) Building a developer relations team and strategy - Hiring and mentoring process, developer advocate vs. community manager - Product discussions, events coordination, and remote work challenges [27:57](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=1677) Principal Developer Advocate role explained - Principal Developer Advocate is a level of individual contributors, reflecting experience and expectation of self-guidance and impact. - Requires significant experience, self-guidance, and impactful contributions to the community. [30:06](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=1806) Importance of measuring developer relations - Developers need recognition from other teams to impact the company positively. - Developer relations contribute to inbound leads and company growth through audience engagement. [35:01](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=2101) Speaking at Shopify, a small example of the principal. - The talk at Shopify was similar to previous content. - Emphasized the importance of helping other departments within the job. [37:04](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=2224) Developer relations is at the center of everything - Developer Advocacy involves more than just sales; it's about building community and adding value. - Providing a bridge between different departments like marketing, product, and sales. [41:18](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=2478) Gradle history and beginnings - Gradle started 12 years ago as a Java build Tool with superior capabilities compared to existing tools. - Gradle offers open source free tools for creating production-ready communities cluster with GitHub integration. [43:18](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=2598) Gradle has expanded capabilities beyond JVM to support various languages like Scala and provides advanced features like build caching - Gradle also offers a commercial product called Gradle Dev Velocity, which serves as a project comprehension and improvement tool for complex builds - Recent incidents highlight the importance of understanding build tools, like Gradle, to prevent sophisticated hacking attempts through manipulated PRs and back doors [48:12](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=2892) Two solutions for highlighting and reusing important book content. - Bookmarks and whisper sync as solutions to highlight and refer back to important content. - Benefits of using Kindle and Audible together for highlighting and reusing book content. [50:16](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=3016) Gradle offers build scans for comprehensive build insights - Gradle sponsors the development of open-source projects like Apache and Spring through Gradle Enterprise - Users can gain visibility into their builds through free build scans, providing insights into goals, phases, tests, and more [55:10](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=3310) Gradle provides detailed feedback on test failures - Feedback includes links to the specific line of code that caused the failure - Links can also be shared with relevant people to ensure a common understanding of the project [57:49](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=3469) Comparing and analyzing multiple builds for insights - I can now visualize differences between builds, including dependencies, CI build numbers, and infrastructure. - Predictive test selection is a key feature that aids in improving build efficiency. [1:02:58](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=3778) The framework shows high accuracy in predictive text selection. - The framework achieved a 98% accuracy in predictive text selection, with only 5 incorrect predictions out of 381 tests. - When turned on for usage, it can save significant time, with 30 days of savings over the last 28 days of usage. [1:05:26](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=3926) Using predictive test selection to save local build times - Predictive test selection allows running all tests in CI regardless of what the model predicts - Gradle's Velocity, a paid product, brings significant savings in local build times [1:09:44](https://www.youtube.com/watch?v=IjtQZFP2QTA&t=4184) Baruch and Fred discuss their friendship and connection on social media. - Baruch and Fred may seem unfriendly on Twitter, but they enjoy picking on each other. - They look forward to meeting in person at a future event or conference. <!-- deep-read:sections end --> ## Highlights - um at some point I didn't spoke there for a couple of years for different reasons never happened within my schedules so I was just happy to be back this year uh with that said uh depending where you live uh it's not the best time usually to come to Montreal and Canada because it's usually like really really cold and like I know a lot of international speakers that came to conf were like yeah we love the conference but yeah don't think we're g to come back next year because like it's it's usually really cold but this year was kind of like look warm temperature ([View Highlight](https://read.readwise.io/read/01j7vj9yd077t1fcaxk77w2d99))