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.

Links

Tuple.app (https://tuple.app) - The best app for pair programming

Tailwind CSS (https://tailwindcss.com) - The CSS framework Adam created

Key Takeaways

• Rewrites can lead to a cleaner, more maintainable codebase.
• Accurate problem modeling can lead to the emergence of new features and benefits.
• The approach to backward compatibility involves making it easy to upgrade to the new version rather than simply making the old version work.

Chapters

• (00:00) - Introduction and Background

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.

Links

Tuple.app (https://tuple.app) - The best app for pair programming

Arrows.to (https://arrows.to) - An app for collaborative customer onboarding that Matt works on

Boring Rails (https://boringrails.com) - Where Matt shares boring tools and practices to keep you as happy and productive

YAGNI (https://yagni.fm) - The podcast where Matt and look at software practices and tools and ask: "do we need it?"

Key Takeaways

• 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.
• Working at a consulting agency can provide valuable experience by exposing developers to a variety of projects and domains.
• Content creation can be a way to contribute back to the community and establish oneself as an expert.
• Demonstrating competence through content creation can help in the hiring process.
• Long-lasting talks focus on practical ideas and good object-oriented design principles.

Chapters

• (00:00) - Introduction and Matt's Role as a Product Engineer

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.

Links

• Tuple.app (https://tuple.app) - The best app for pair programming
• SavvyCal.com (https://savvycal.com) - The scheduling tool Derrick created
• Phoenix (https://www.phoenixframework.org) - the Elixir framework SavvyCal is built on
• Rails (https://rubyonrails.org) - the Ruby framework Ben worked with

Key Takeaways

• Elixir and the Phoenix framework offer a maintainable and explicit approach to building applications.
• Functional programming paradigms can simplify code organization and improve maintainability. Object-oriented programming and functional programming have different approaches to code organization and maintainability.
• 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.
• Open source contributions can be seen as a good faith contribution to the commons and can provide benefits such as status and marketing opportunities.
• Developers can improve their design skills by studying resources like the book 'Refactoring UI' and being introspective about user interfaces in their daily lives.

Chapters

• (00:00) - Introduction and Background

In this episode, Ben chats with Thorsten Ball. This conversation fits neatly into two halves - in the first, Ben and Thorsten go deep on how to differentiate yourself, work in public, and make it easy for people to hire you. In the second part of the conversation, they talk more specifically about Zed, why it matters, and how it’s being built. 

Links

Tuple.app (https://tuple.app) - The best app for pair programming

Thorsten’s website (https://thorstenball.com) - Where you can find his books, blog, and other podcast appearances

Zed (https://zed.dev) - The editor Thorsten is working on

Key Takeaways

• Cultivating a diverse skill set can lead to unique opportunities and make you a valuable asset in a company.
• Evidence of competence, such as published work or open-source contributions, can significantly impact your chances of getting hired.
• Soft skills, such as communication and problem-solving, are essential for success in engineering roles.
• Taking initiative and adding value beyond your job description can make you stand out and contribute to the growth of a company.
• Interviews should be seen as a chance to demonstrate your skills and fit within a company's culture, rather than just answering questions. Visual cues and real-time interaction are important in conversations to gauge resonance and maintain engagement.
• Different business models exist in the tech industry, and investment can provide the time and resources needed for product development.
• Building high-quality products in open source requires a focus on performance, quality, and attention to detail.
• The landscape of text editors and funding is complex, with various models and approaches.
• Working on a quality product with a talented team can be fulfilling and contribute to personal growth.
• Noticing and writing about interesting ideas can enhance creativity and lead to new insights.

Chapters

• (00:00) - Introduction and Background

Ben interviews Andreas Kling, creator of SerenityOS and the Ladybird browser. They talk about the concept of lifestyle software and how it relates to the development of SerenityOS, Andreas’ vision of creating a Zen garden for developers, and the benefits of using a mono repo and a unified language in the development process. They also touch on the use of AI and language models for writing code, the art of using Copilot effectively, and the future of LLMs in pair programming.

Enjoy!

Links

Tuple.app - The best app for pair programming

Andreas’ YouTube Channel - The home for Serenity, Ladybird, and other updates from Andreas

SerenityOS - The operating system Andreas built

Ladybird - The browser Andreas built

Key Takeaways

• Serenity OS is an example of lifestyle software, where the focus is on the happiness of the developers and the joy of programming.
• The use of a mono repo and a unified language in Serenity OS allows for efficient development and easy cross-cutting changes.
• Onboarding new contributors by encouraging them to explore and find their own areas of interest leads to a diverse range of contributions.
• Raw coding videos and pair programming can be powerful tools for knowledge sharing and learning.
• Having a long-term vision and setting ambitious goals can help overcome the challenges of monumental projects.
• Continuous learning and improvement are essential for staying on top of new tools and technologies in the programming industry.
• Balancing programming and management responsibilities can be challenging, but leveraging the skills and expertise of a team can lead to greater productivity and growth. Building confidence in programming is crucial for productivity and success.
• Starting small and building miniature models can help understand complex concepts.
• Throwing away code and rebuilding with improved architecture can lead to better outcomes.
• Using AI and language models can significantly speed up coding tasks.

Chapters

• (00:00) - Introduction

In this conversation, Fable and Ben dig deep on building a technical career that balances programming and company leadership. Fable shares their experience working at Stripe and the different roles they have held, including being a technical advisor to the CTO. They also discuss Fable's career move from being a hands-on programmer to role where less hands-on coding is required, Fable's take on "code crimes", and how to find enjoyment and fulfillment in solving complex problems.

Links

Tuple.app - The best app for pair programming
Stripe - The company Fable works at
Ruby Kaigi - An annual conference dedicated to the Ruby programming language.
Sidekiq - A simple, efficient background processing library for Ruby
Sorbet - A fast, powerful type checker designed for Ruby.
YubiKey - A hardware device designed for high-security two-factor authentication.

Key Takeaways

• Making connections and friendships at conferences can be valuable in the programming community.
• Debugging and problem-solving skills are crucial for software engineers.
• Being willing to learn and work with different programming languages can enhance your skills.
• Prototyping and spiking can be effective ways to test and develop new ideas.

Chapters

• (00:00) - Introduction and Conference Interaction

In this episode, Ben interviews Josh Pigford, founder of Maybe.co, about the company’s journey from VC-backed startup -> closed startup -> open source project -> funded open source project. They discuss JavaScript and Rails trade-offs, the challenges of building a personal finance software, and the operational difficulties of building a business based on open source software.

Links

Tuple.app - The best app for pair programming
Maybe.co - The fintech startup Josh founded
NodeJS - The starting framework for Maybe.co
Ruby on Rails - The new framework for Maybe.co

Key Takeaways

• Choosing the right tech stack is crucial for the success of a project.
• Running out of runway can force difficult decisions and pivots.
• Making a codebase public can generate interest and community engagement.
• Replacing third-party dependencies can be challenging but necessary.
• Rebuilding a software project requires careful planning and decision-making. Building a personal finance app involves challenges such as managing pull requests and issues in open source development.
• Transitioning to Rails can provide a more stable and efficient framework for building a complex application.
• The decision to rewrite the app from scratch allows for better decision-making and faster progress.
• Targeting Mint users with a budgeting tool presents an opportunity to capitalize on a fragmented market.
• Detangled, a project that simplifies legal documents, has the potential for commercial success. Moonshot ideas can be exciting and worth pursuing, even if the specific angle is unclear.
• ChatGPT has the potential to generate usable results, either through heavily massaged prompts or prewritten blocks.
• Tools like detangle can augment conversations with lawyers, providing insights and helping users know what questions to ask.
• There are commercial opportunities in selling services like detangle to companies that don't have full-time counsel.
• Finding the right balance between passion and traction is important when deciding which projects to pursue.

Chapters

• (00:00) - Introduction

In this conversation, Ben interviews Caleb Porzio, the creator of AlpineJS and Laravel Livewire. The discussion ranges from discussions about life in general to specific testing practices and which notebook Caleb uses.

Links
Tuple.app - The best app for pair programming
AlpineJS
Laravel Livewire
Caleb's VSCode Course

Takeaways

• Apply core truths to life outside of programming.
• Find ways to make difficult tasks easier.
• Change your environment to support your goals.
• Value tests as much as, if not more than, the code itself.
• Keep methods and functions short for better code quality.
• Embrace your strengths and delegate tasks that don't bring you joy.
• Focus on the meaty tasks that excite you.
• Consider rewrites carefully and prioritize other solutions first.
• Pull down unfamiliar code and interact with it to understand it better.
• Start the day with tasks that align with your goals and priorities.

Chapters

• (00:00) - Introduction and Background

In this conversation, Ben interviews Taylor Otwell, the creator of Laravel. They discuss everything from the age-old argument of tabs vs. spaces to the origins of Laravel and how Taylor has turned it into a thriving, sustainable business.

Links:
Laravel, the framework Taylor created
Tuple, used by the Laravel team to collaborates

Takeaways

• Coding preferences and philosophies can vary among developers and programming ecosystems.
• Maintaining backwards compatibility is important for frameworks with a large user base.
• Clean code can be subjective and depends on the specific needs and goals of a project.
• Testing is crucial for shipping software with confidence. When starting a new project, consider writing documentation first to iron out any potential issues and ensure a user-centric perspective.
• Focus on high-level testing, such as feature-level or controller-level tests, to gain confidence in the functionality of your code.
• Challenge assumptions and ask questions to improve the quality of your code and avoid unnecessary complexity.
• Believe in the potential of your project and raise your ambitions to achieve greater success.
• Building a business around open source can be a sustainable model if you create commercial products that complement and support the open source project.

Chapters

• (00:00) - Tabs or Spaces?