by Ben Orenstein
Ben Orenstein interviews great programmers about their craft.
Language
🇺🇲
Publishing Since
1/24/2024
Email Addresses
1 available
Phone Numbers
0 available
June 10, 2024
<p>Ben and Adam Wathan cover the development and reimagining of Tailwind CSS, focusing on the release of Tailwind 4.0. They delve into the motivation behind the rewrite, the challenges faced, and the approach to maintaining backward compatibility. The conversation covers topics related to software versioning, open-source maintenance, backward compatibility, the use of Rust in Tailwind, testing strategies, and the future of Tailwind as a business.</p><p><br></p><p><strong>Links</strong></p><p>Tuple.app (<a href="https://tuple.app/">https://tuple.app</a>) - The best app for pair programming</p><p>Tailwind CSS (<a href="https://tailwindcss.com">https://tailwindcss.com</a>) - The CSS framework Adam created</p><p><br></p><p><strong>Key Takeaways</strong></p><ul><li>Rewrites can lead to a cleaner, more maintainable codebase.</li><li>Accurate problem modeling can lead to the emergence of new features and benefits.</li><li>The approach to backward compatibility involves making it easy to upgrade to the new version rather than simply making the old version work.</li></ul><p><br><strong>Chapters<br></strong></p><ul><li>(00:00) - Introduction and Background</li> <li>(00:35) - Windows Version Launch and Guest Network</li> <li>(01:24) - Rewriting Tailwind: Philosophy and Execution</li> <li>(03:42) - Ben’s Static HTML Website Idea</li> <li>(09:06) - Re-imagining Tailwind with Tailwind 4</li> <li>(20:49) - Challenges and Solutions in Tailwind Development</li> <li>(32:45) - Rust Components in Tailwind 4</li> <li>(35:41) - Tailwind 4 Goals and Achievements</li> <li>(40:22) - Testing and Quality Assurance in Tailwind 4</li> <li>(46:38) - Tailwind 4 Release</li> <li>(49:54) - The Tailwind Origin Story</li> <li>(52:24) - Business Strategies and Open Source Impact </li> </ul>
May 27, 2024
<p>Ben and Matt discuss the role of a product engineer and Matt's journey as a content creator. Matt shares his experience working at a consulting agency and how it shaped his perspective on engineering. They also discuss the benefits of working in-person and the importance of the quality of coworkers. Matt reflects on his motivation for content creation and how it ties into his competitive nature. They touch on the changing landscape of content creation and the value of posting code snippets, and about Matt's experience getting hired at Arrows through Twitter and the value of demonstrating competence through content creation. They touch on the longevity of Ben's Ruby talk and the elements that make it stand out.</p><p><br></p><p><strong>Links</strong></p><p>Tuple.app (<a href="https://tuple.app/">https://tuple.app</a>) - The best app for pair programming</p><p>Arrows.to (<a href="https://arrows.to">https://arrows.to</a>) - An app for collaborative customer onboarding that Matt works on</p><p>Boring Rails (<a href="https://boringrails.com">https://boringrails.com</a>) - Where Matt shares boring tools and practices to keep you as happy and productive</p><p>YAGNI (<a href="https://yagni.fm">https://yagni.fm</a>) - The podcast where Matt and look at software practices and tools and ask: "do we need it?"</p><p><br></p><p><strong>Key Takeaways</strong></p><ul><li>A product engineer is someone who writes code, cares about design and user experience, and is responsible for the end-to-end delivery of a feature.</li><li>Working at a consulting agency can provide valuable experience by exposing developers to a variety of projects and domains.</li><li>Content creation can be a way to contribute back to the community and establish oneself as an expert.</li><li>Demonstrating competence through content creation can help in the hiring process.</li><li>Long-lasting talks focus on practical ideas and good object-oriented design principles.</li></ul><p><br></p><p><strong>Chapters</strong></p><p></p><ul><li>(00:00) - Introduction and Matt's Role as a Product Engineer</li> <li>(07:11) - The Benefits of Working at a Consulting Agency</li> <li>(09:34) - The Importance of Quality Coworkers</li> <li>(13:41) - The Motivation for Content Creation</li> <li>(18:54) - The Value of Posting Code Snippets</li> <li>(24:03) - Packaging Content as an Event</li> <li>(26:40) - Demonstrating Competence through Content Creation</li> <li>(32:05) - Long-Lasting Talks: Practical Ideas and Object-Oriented Design</li> <li>(38:39) - 'Nathan for You': Creative and Mischievous Problem-Solving</li> <li>(41:30) - Unconventional Advertising: Selling Ads on the Penny</li> <li>(44:29) - Thinking Outside the Box: Unconventional Solutions</li> </ul>
May 13, 2024
<p>In this conversation, Ben and Derrick discuss the challenges of growing a business and the decision to target specific market segments. They explore the trade-offs between serving a broad audience and focusing on a niche market. They also discuss the technical choices and architectural decisions in building a product, with Derrick sharing his positive experience with Elixir and the Phoenix framework.</p><p><br></p><p><strong>Links</strong></p><ul><li>Tuple.app (<a href="https://tuple.app/">https://tuple.app</a>) - The best app for pair programming</li><li>SavvyCal.com (<a href="https://savvycal.com">https://savvycal.com</a>) - The scheduling tool Derrick created</li><li>Phoenix (<a href="https://www.phoenixframework.org/">https://www.phoenixframework.org</a>) - the Elixir framework SavvyCal is built on</li><li>Rails (<a href="https://rubyonrails.org">https://rubyonrails.org</a>) - the Ruby framework Ben worked with</li></ul><p><br></p><p><strong>Key Takeaways</strong></p><ul><li>Elixir and the Phoenix framework offer a maintainable and explicit approach to building applications.</li><li>Functional programming paradigms can simplify code organization and improve maintainability. Object-oriented programming and functional programming have different approaches to code organization and maintainability.</li><li>The active record pattern in Rails can lead to large and complex models, while the repository pattern in Phoenix provides a more modular and explicit approach.</li><li>Open source contributions can be seen as a good faith contribution to the commons and can provide benefits such as status and marketing opportunities.</li><li>Developers can improve their design skills by studying resources like the book 'Refactoring UI' and being introspective about user interfaces in their daily lives.</li></ul><p><br></p><p><strong>Chapters</strong></p><p></p><ul><li>(00:00) - Introduction and Background</li> <li>(02:12) - Savvy Cal and Horizontal Products</li> <li>(05:56) - Choosing Between Niche and Broad Audience</li> <li>(15:59) - Phoenix vs. Rails</li> <li>(22:20) - Object Oriented vs. Functional Programming</li> <li>(36:02) - The Motivations Behind Open Source Contributions</li> <li>(43:20) - Improving Design Skills as a Technical Person</li> </ul>
Ian Landsman and Aaron Francis
Wes Bos & Scott Tolinski - Full Stack JavaScript Web Developers
Oxide Computer Company
37signals
Changelog Media
Software Engineering Daily
Changelog Media
Changelog Media
Michael Dyrynda and Greg Skerman
Taylor Otwell, Matt Stauffer
Jacob Bennett and Michael Dyrynda
Adam Elmore & Dax Raad
Joel Clermont and Aaron Saray
Andrew Lisowski, Justin Bennett
Jacob Bennett and Michael Dyrynda
Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.
All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.
We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.
While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at [email protected] for prompt review and appropriate action, which may include content removal or proper attribution.
By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.