ConTejas Code

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Wix (sponsor): https://tej.as/wix- SquiggleConf (partner): https://squiggleconf.com/- JS Heroes: https://jsheroes.io/- Alex on X: https://x.com/alexnmoldovan- Tejas on X: https://x.com/tejaskumar_Summary:In this discussion, we talk to Alex Moldovan, a software engineer at CodeSandbox and event planner who co-founded JS Heroes—a non-profit, community-driven JavaScript (Programming Language) conference in Romania. Together, we cover the intricacies of project management, event planning, and the challenges of organizing a conference that prioritizes open source values and community engagement.Key topics include the benefits of a single-track format for presentations and talks, strategies for diversity and inclusion in the call for papers (CFP) process, and balancing a full-time role in technology with being a conference speaker and organizer. The discussion provides valuable insights for developers interested in community building, functional programming, and the evolving landscape of the tech industry.Chapters00:00:00 Alex Moldovan00:03:54 Introduction00:09:42 Origin of JS Heroes00:18:17 Non-Profit Conference Model00:25:15 Single-Track Conference Benefits00:36:16 Transparency in Event Planning00:43:13 Challenges with Sponsorship00:53:27 Scaling and Quality Focus01:04:54 Diversity in CFP Process01:13:08 Cultural Challenges in Tech01:23:26 Balancing Roles01:32:26 Future Goals for JS Heroes Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Wix (sponsor): https://tej.as/wix- G2i: https://g2i.co- Developer Health OS: https://www.g2i.co/developer-health- Michelle on X: https://x.com/michellebakels- Tejas on X: https://x.com/tejaskumar_SummaryIn this episode, Michelle Bakels from G2i discusses the importance of developer health and wellbeing. She explains G2i's Developer Health Operating System, which focuses on burnout recovery, prevention, and optimizing performance. Michelle shares insights on work-life balance, the impact of remote work, and practical strategies for maintaining physical and mental health in the tech industry.Chapters00:00:00 Introduction00:06:13 Challenges developers face in the tech industry00:12:08 External and internal pressures on developers00:19:31 The importance of questioning and reevaluating work habits00:24:08 G2I's focus on developer health00:29:33 Overview of the Developer Health Operating System00:34:26 Burnout recovery strategies00:39:53 Workaholic tendencies and stress addiction00:46:38 Burnout prevention techniques00:51:58 Optimizing performance through sleep and brain health00:59:43 Remote work's impact on productivity and work-life balance01:09:12 Michelle's personal routine for maintaining health and productivity01:15:11 Measuring the effectiveness of health strategies01:20:18 G2I's four-day work week experiment01:24:50 The importance of transparency and vulnerability in leadership01:28:10 Conclusion and final thoughts Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Wix (sponsor): https://tej.as/wix- SquiggleConf (partner): https://2024.squiggleconf.com/- G2i: https://www.g2i.co/- Gabe on X: https://x.com/gabe_g2i- Tejas on X: https://x.com/tejaskumar_- Book: "Traction" by Gino Wickman https://www.amazon.de/-/en/Gino-Wickman/dp/1936661837- "Move Fast and Fix Things" book: https://www.amazon.de/-/en/Frances-Frei/dp/1647822874- Developer Health Operating System: https://www.devhealthos.com- fourdayworkweek.io: https://www.fourdayworkweek.io- Suno: https://suno.ai - Ro.am: https://ro.am- Loom: https://www.loom.com- Linear: https://linear.app- "Deep Work" book by Dr. Cal Newport: https://www.amazon.de/-/en/Cal-Newport/dp/1455586692- Dopamine Nation by Dr. Anna Lembke: https://www.amazon.de/-/en/Dr-Anna-Lembke/dp/152474672XSummaryG2i is a unique hiring community that originated from the open-source community. The company focuses on working with React, React Native, and GraphQL engineers and matching them with companies. G2i stands out for its autonomous and engineering-focused approach to solving problems. The company emphasizes clarity, prioritization, and moving fast while maintaining trust. The Entrepreneurial Operating System (EOS) framework has been implemented at G2I to provide structure and clarity in running the business. The key quality that sets great engineers apart is their ability to work autonomously, take ownership, and make effective decisions. In this conversation, Gabe and Tejas discuss the importance of developer health and its impact on revenue generation. They explore the concept of setting priorities and positioning oneself close to revenue as a founder. They also touch on the idea of creating a cohesive story around optimizing revenue and developer health. Gabe shares insights on implementing the Entrepreneurial Operating System (EOS) framework and the value of having a clear vision and core values. They also discuss the tools and technologies that have been crucial for successful remote work at G2I.Chapters00:00:00 Gabe Greenberg00:03:45 Introduction and G2I's unique approach00:07:16 Building a company without VC backing00:10:42 The importance of mentors and advisory boards00:16:08 Implementing the Entrepreneurial Operating System (EOS)00:22:04 Key qualities of great engineers00:27:44 The value of being early to new technologies00:34:02 G2I's initiatives in AI and machine learning00:41:30 Developer health and productivity00:48:06 Recognizing patterns in emerging tech ecosystems00:54:51 Identifying valuable skills in the AI era01:02:53 G2I's work with reinforcement learning01:08:38 Balancing revenue goals and developer wellbeing01:16:45 Advice for technical founders and CEOs01:23:03 Implementing goal-setting frameworks like EOS01:28:27 Tools and strategies for successful remote work Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Wix (sponsor): https://tej.as/wix- Josh Goldberg: https://x.com/joshuakgoldberg- Learning TypeScript: https://learning.oreilly.com/library/view/-/9781098110321/- SquiggleConf: https://2024.squiggleconf.com/ SummaryJoshua K Goldberg is a full-time independent open source maintainer in the TypeScript ecosystem. He shares his journey into open source and the importance of filling in the gaps in the ecosystem. He also discusses the best incremental migration path to TypeScript and highlights advanced features like shenanigans with type parameters and the 'satisfies' keyword. The conversation covers topics such as literals in TypeScript, writing a book, the process of writing and shipping a book, the reception of the book, the development of TypeScript ESLint, abstract syntax trees (ASTs), parsing, and static analysis. We also discuss the future of TypeScript, the performance of ESLint, and configuration tips to improve ESLint's performance. Takeaways1. Being a full-time independent open source maintainer is rewarding and allows for direct contributions to tools that benefit everyone.2. When migrating to TypeScript, it's best to start with one file at a time and gradually increase strictness.3. Type parameters in TypeScript can be complex, but they are useful for advanced scenarios.4. The 'satisfies' keyword in TypeScript allows for declaring data that adheres to a type while still inferring a more specific type.5. Parsing is the process of converting a string of code into an AST.6. ESLint provides a report function that allows lint rules to report issues to the user.7. TypeScript ESLint supports typed linting, which allows for more powerful linting rules.8. ESLint's performance can be affected by misconfiguration, the number of plugins, and the use of ESLint plugin prettier.9. Separating ESLint and Prettier as separate tools can improve performance.10. Being an open-source maintainer can be challenging, but having a fallback plan and a supportive community can make it sustainable.Chapters00:00 Josh Goldberg03:37 Introduction and Background06:22 The Journey into Open Source and Filling in the Gaps15:15 The Best Incremental Migration Path to TypeScript28:41 Introducing the 'Satisfies' Keyword in TypeScript30:31 The Process of Writing and Shipping a Book35:10 The Development of TypeScript ESLint37:26 Parsing and Static Analysis with Abstract Syntax Trees56:54 Improving ESLint Performance: Configuration Tips01:01:00 Understanding the Role of ASTs and Compilers in TypeScript and ESLint01:03:42 Configuring Type Linting in TypeScript01:06:22 The Intersection of AI with TypeScript and ESLint01:11:53 Creating a Standardized Open-Source Sponsorship Rating System Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (Sponsor): https://tej.as/codecrafters- Wix (Sponsor): https://tej.as/wix- OpenPipe: https://openpipe.ai- Kyle on X: https://x.com/corbtt- Tejas on X: https://x.com/tejaskumar_SummaryKyle Corbitt, founder and CEO of OpenPipe, shares the origin story of the company and his background in computer science and entrepreneurship. He discusses the evolution of machine learning and the breakthroughs that made OpenPipe possible. The conversation then dives into the process of fine-tuning models using OpenPipe, including the logging feature, data curation, and the selection of base models and hyperparameters.The episode also explores the developer experience and the decision to create an SDK that is a drop-in replacement for the OpenAI SDK. The conversation explores the concept of overfitting in machine learning models and how it differs for language models. The validation process for fine-tuned models is discussed, including inner loop tests and outer loop evaluations.Takeaways1. OpenPipe was founded to help people transition easily and smoothly into fine-tuning models using machine learning.2. The process of fine-tuning models involves logging user requests, curating data, selecting base models, and optimizing hyperparameters.3. OpenPipe provides an SDK that is a drop-in replacement for the OpenAI SDK, making it easy for developers to integrate OpenPipe into their existing workflows.4. The platform automates the heavy lifting of fine-tuning models, including the optimization of hyperparameters based on thousands of fine-tuned models and user-defined evaluations.5. OpenPipe offers a seamless developer experience, allowing users to quickly and efficiently fine-tune models and deploy them for production use.Chapters00:00 Kyle Corbitt03:28 The Origin Story of OpenPipe14:34 Fine-Tuning Models with OpenPipe33:46 Understanding Overfitting and Fine-Tuning39:47 The Role of Hyperparameters46:32 Validating Fine-Tuned Models56:46 Enabling Tool Calls in Language Models01:00:33 Unleashing the Full Potential of Language Models01:05:09 Introduction to OpenPipe01:10:14 Changing the Configuration Parameter01:20:17 The Future of OpenPipe01:25:31 The Need for a Founder's Handbook01:32:17 Advice for Technical Founders and CEOs Hosted on Acast. See acast.com/privacy for more information.

Links- Wix Studio (sponsor): https://tej.as/wix- Codecrafters (sponsor): https://tej.as/codecrafters- Shruti Balasa's Website: https://shrutibalasa.com/- Tailwind Weekly: https://tailwindweekly.com/- Shruti on X: https://x.com/shrutibalasa- Tejas on X: https://x.com/tejaskumar_SummaryShruti Balasa, a Tailwind CSS expert, shares her journey of discovering and specializing in Tailwind CSS. She explains how Tailwind CSS enhanced her CSS skills and made her more efficient in web development. She also discusses the pain points that Tailwind CSS solves, such as context switching, naming conventions, and cross-browser compatibility. Shruti emphasizes the importance of understanding CSS fundamentals before diving into Tailwind CSS. She also addresses common criticisms of Tailwind CSS, such as the length of class names and the use of the apply directive. The conversation also covers topics like layers, dynamic and static components, and the use of Tailwind CSS for email design. Shruti recommends using plugins like Prettier Tailwind CSS Sorting for code organization and subscribing to Tailwind Weekly for updates on new plugins and resources. She also discusses upcoming features in Tailwind CSS, such as CSS-first configuration and container queries.Takeaways1. Understanding CSS fundamentals is important before diving into Tailwind CSS2. Tailwind CSS solves pain points such as context switching and naming conventions3. The apply directive should be used sparingly and for specific cases4. The Tailwind config file allows customization and the creation of plugins5. Tailwind CSS version 4 introduces auto-discovery and shifts towards using CSS for configuration6. Tailwind CSS generates only the styles that are used in the source code with the Just-In-Time (JIT) compiler7. Tailwind CSS is a choice and not a requirement for improving accessibility or performance.8. Subscribing to Tailwind Weekly can provide updates on new plugins and resources.9. Upcoming features in Tailwind CSS include CSS-first configuration and container queries.Chapters06:19 Discovering and Specializing in Tailwind CSS09:33 Enhancing CSS Skills with Tailwind CSS13:19 Solving Pain Points with Tailwind CSS17:36 The Use of the Apply Directive in Tailwind CSS26:16 Upcoming Changes in Tailwind CSS Version 434:21 The Latest State of Tailwind CSS v4 Discussions37:33 Generating Only the Used Styles with the JIT Compiler40:56 Maintaining Consistency in Large-Scale Projects with Custom Classes53:47 Responsive Features in Tailwind CSS: Dark Mode and Reduced Motion01:01:31 Tailwind CSS: A Choice for Convenience01:04:28 Exploring Layers and Components in Tailwind CSS01:09:00 Tailwind CSS for Email Design and Development01:18:00 Useful Plugins for Tailwind CSS Productivity01:22:34 Exciting Upcoming Features in Tailwind CSS Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Nx: https://nx.dev/- Jeff on X: https://twitter.com/jeffbcross- Tejas on X: https://x.com/tejaskumar_SummaryJeff B. Cross, co-founder of NX, discusses the origins of NX and its evolution as a tool for monorepos. He explains the benefits of using NX, such as code mod running, large-scale migrations, and CI optimizations. Jeff also clarifies the definition of a monorepo and how NX supports both package-based and graph-based monorepos. He highlights the features of NX that help with development, integration, and deployment, including the interactive graph, tagging system, and caching. We also cover the ability of NX to deflake tests and shares his perspective on running a business, including the challenges of positioning and marketing, and his experience of starting NX. Takeaways1. NX is a powerful tool for monorepos that offers features such as code mod running, large-scale migrations, and CI optimizations.2. A monorepo can be defined as a single repository containing multiple distinct projects with well-defined relationships.3. NX supports both package-based and graph-based monorepos, with the latter being more suitable for application developers.4. NX also offers features for integration and deployment, such as building affected targets, replaying builds and tests, and distributing work across multiple machines.5. NX has the ability to deflake tests, which are tests that indeterministically fail or pass. NX detects and handles flaky tests by analyzing test results and determining if a test fails often or fails without changes in inputs or dependencies.6. Measuring the developer experience is challenging, but NX uses user feedback, internal testing, and collaboration with enterprise customers to improve the product.7. Positioning and marketing a product can be a difficult task, especially for a tool like NX that doesn't fit into a specific category.8. Finding a niche and being the best in the world at it is crucial for success as a consultant or business owner.9. Continuous adaptation and evolution are essential qualities for a CEO, as they need to be able to change and pivot as the company grows.10. Polygraph, an upcoming feature of Nx, will provide visibility and dependency management across multiple workspaces in an organization.Chapters00:00:00 Jeff Cross00:03:18 Introduction and Origins of NX00:06:25 Understanding Monorepos and NX00:11:04 Tools for Development and Code Consistency00:14:56 Integration and Deployment with NX00:36:09 Detecting and Handling Flaky Tests00:38:20 The Developer Experience with NX00:48:36 Understanding Lexers, Parsers, Compilers, and Rich Text Editors01:00:54 Challenges of Positioning and Marketing01:03:36 Starting and Running a Business01:10:47 The impact of Nx Cloud on CI performance01:18:49 Introducing Polygraph: Visibility and dependency management01:27:46 What's next for Nx01:31:47 Conclusion Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters - Jatin on X: https://x.com/JatinRamanathan- Tejas on X: https://x.com/tejaskumar_SummaryJatin Ramanathan, a software engineer at Google, discusses the Wiz framework and its use in Google products like search, photos, and payments. Wiz is a resumable web framework that focuses on loading minimal JavaScript and uses the concept of signals for reactive programming. Signals are reactive properties that reflect the state of an observable or reactive property at any given time. The Wiz framework also incorporates JS Action, a library that listens to events and delivers them to event handlers only when necessary, reducing the amount of JavaScript that needs to be loaded. The conversation also touches on the merger of Wiz and Angular and the potential for unified APIs in the future. The conversation explores the concept of responsible JavaScript and web performance. We dive into the use of signals and JS action in Wiz and Angular, and how they enable declarative behavior and interactivity on the client side. The discussion also touches on the challenges of using TSX in Angular and the potential for future improvements. The importance of measuring performance and understanding the user experience on different devices is emphasized, along with the use of feature flags and instrumentation to optimize the user funnel.Takeaways1. Wiz is a resumable web framework used in Google products like search, photos, and payments.2. The framework focuses on loading minimal JavaScript and uses signals for reactive programming.3. JSAction is a library that listens to events and delivers them to event handlers only when necessary, reducing the amount of JavaScript that needs to be loaded.4. Wiz and Angular are merging to exchange ideas and potentially unify APIs in the future. 5. Signals and JSAction in Wiz and Angular enable declarative behavior and interactivity on the client side.Chapters00:00 Jatin Ramanathan03:05 Welcome Jatin06:15 Overview of Wiz and its Use in Google Products13:00 Resumability and the Concept of Signals36:03 Merger of Wiz and Angular: Unifying APIs48:08 Signals and Interactivity50:26 Declarative Behavior with Signals and JS Action52:10 Performance of HTML and htmx59:10 Responsible JavaScript as a Diet01:09:26 Open Sourcing Wiz through Angular01:13:34 Challenges of TSX in Angular01:16:40 Declarative Behavior Composition in TSX01:22:15 Contributing to Wiz through Angular01:25:11 Checklist for Responsible JavaScript and Web Performance Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Polypane: https://polypane.app/- Kilian on X: https://x.com/kilianvalkhof- Tejas on X: https://x.com/tejaskumar_SummaryKilian Valkhof created Polypane, a web browser designed to enhance developer productivity. Built on Chromium with Electron, it offers features like local server sharing, live DOM view, and social media preview tools.Polypane's development faced challenges in element injection, security, and dependency management. Valkhof balances user feedback with innovation, maintaining a user-centric approach while introducing novel features.The business model includes a free trial and paid plans, addressing the challenge of monetizing in a market accustomed to free tools. Valkhof emphasizes clear communication of Polypane's value in the competitive DevTools space.Throughout Polypane's journey, Valkhof has stressed the importance of comprehensive documentation, willingness to take risks, and effective user engagement. These principles guide Polypane's evolution as it aims to distinguish itself in the web development tool market.Takeaways1. Explore specialized tools for improved productivity2. Consider cross-device testing for better user experience3. Gather concrete user feedback for meaningful improvements4. Utilize visual tools for better code understanding5. Try free trials to evaluate tool value6. Focus on value provided when pricing products7. Refine messaging to effectively communicate product benefits8. Develop active listening skills for user engagement9. Balance user requests with innovative features10. Invest time in comprehensive documentationChapters00:00 Kilian Valkhof Introduction03:49 Introduction and Background07:07 Polypane: A Web Browser for Developers10:37 The Engineering Behind Polypane14:11 Testing and Compatibility in Polypane19:37 Real-Time Collaboration and Testing with Polypane's Proxy Feature35:49 Challenges of Injecting Visual Elements42:57 The Importance of a Concrete Basis for User Feedback44:46 Insights for Developers: Live DOM View and Head Order Visualization57:36 Complexities of Creating Accurate Social Media Previews01:07:24 The Business Side of Polypane: Pricing and Value01:12:49 Getting Employers to Pay for Developer Tools01:14:59 The Value of Developer Tools and Fair Compensation01:21:01 Messaging and Positioning in the DevTools Space01:23:26 Iterating on Messaging and Positioning01:28:01 The Skill of Listening and Engaging with Users01:29:54 Balancing User Needs and Innovative Features01:33:09 Features That No One Asks For01:36:58 Navigating Pushback and Communicating Decisions Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Fair Source License: https://fair.io/- Sentry: https://sentry.io/- Sentry on X: https://x.com/getsentry- Chad on X: https://x.com/chadwhitacre_- Tejas on X: https://x.com/tejaskumar_SummaryChad Whitacre, Head of Open Source at Sentry, discusses his involvement in open source and the commitment of Sentry to open source. He shares his background in the Python community and his experience with open source sustainability. Chad explains the importance of community in open source and the origins of the free software movement. He also talks about Richard Stallman, the founder of the free software movement, and his impact on the open source community.Chad discusses his role at Sentry and the company's deep roots in open source. He highlights Sentry's efforts to give back to open source maintainers and their commitment to open source sustainability. The conversation explores the tension between the pressure to grow and make money in the startup world and the act of giving back to the open-source community.Together, we discuss how Sentry gives away half a million dollars to open-source projects. He explains that this act is part of their brand and values as a company. They believe in supporting open source, privacy, and security. Chad also talks about the challenges and ethical dilemmas of open source, including re-licensing and the tension between community and corporation. The conversation explores the concept of fair source licensing and the role of foundations in supporting open source projects. It discusses the need for a balance between user freedom and developer sustainability.Open source is fundamentally broken within the framework of market dynamics. It writes itself out of capitalism and lacks a sustainable funding model. The current approach to funding open source involves jumping through hoops and finding adjacent business models to subsidize the work. This is not a sustainable solution. The concept of fair source, where compensation is required for commercial use of open source software, offers a potential solution. Companies can join a funding cabal or pledge to contribute a percentage of revenue to support open source projects. The goal is to create a sustainable ecosystem where developers can be fairly compensated for their work.Chapters00:00:00 Chad Whitacre00:04:40 Introduction and Background00:12:02 The Importance of Open Source and Community00:17:12 Sentry's Commitment to Open Source00:20:47 Supporting Open Source with Thanks.dev00:28:49 The Tension Between Startup Growth and Giving Back to Open Source00:39:10 The Ethical Dilemmas of Open Source and Re-Licensing00:47:24 Balancing Community and Corporation in the Open-Source Ecosystem00:52:20 Fair Source Licensing00:54:06 Introducing Fair Source00:58:05 Transitioning from BST to BSL01:00:48 Balancing Developer Sustainability and User Freedom01:03:38 The Value of the In-Between01:07:19 Defining Open Source01:13:09 Negotiating Fair Compensation01:15:42 The Role of Foundations01:20:16 Foundations as Community Stewards01:27:51 Jumping Through Hoops: The Current Approach to Funding Open Source01:38:46 Fair Source: A Potential Solution for Sustainable Funding01:42:20 Joining the Funding Cabal: Supporting Open Source Projects01:44:30 Creating a Sustainable Ecosystem for Fair Compensation Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Sentry: https://sentry.io/- Sentry on X: https://x.com/getsentry- David on X: https://x.com/zeeg- Tejas on X: https://x.com/tejaskumar_SummaryDavid Cramer, the founder of Sentry, discusses the origins and growth of the company. Sentry started as an open-source project that Cramer built to solve his own problems as a software engineer. The initial version of Sentry captured and deduplicated errors, providing developers with valuable context for debugging. Cramer's experience at Disqus and Dropbox allowed him to refine and commercialize Sentry, turning it into a successful business. The key to Sentry's success was its versatility and ease of integration, supporting any SQL adapter that Django supported. Cramer emphasizes the importance of simplicity and pragmatism in building a product and the value of user feedback in shaping its development.We discuss the challenges of using open source technology and the early architecture of Sentry. He emphasizes the importance of simplicity and the power of SQL databases. He also talks about the need for a fast and accurate development environment and the value of being brand-driven rather than data-driven. Sentry is focused on capturing attention through creative marketing campaigns. They believe that marketing is about capturing someone's attention and making them curious. They use preposterous and visually compelling campaigns that have nothing to do with their product to capture attention. They emphasize the importance of building brand recognition and authenticity. They also discuss the challenges of marketing and positioning complex technical products. They believe that marketing and positioning are more important and more complex than the engineering side of things. They emphasize the need for founders to care deeply about what they are doing and to be willing to take risks.Chapters00:00:00 David Cramer00:03:19 Introduction and Background00:15:39 The Initial Problem and Early Development of Sentry00:26:38 Transitioning Sentry from Open-Source Project to Company00:33:22 Technical Decisions that Shaped Sentry's Versatility and Portability00:36:11 The Importance of Simplicity and User Feedback in Sentry's Development00:36:38 Challenges of Using Open Source Technology00:38:32 The Power of SQL Databases in Architecture00:41:47 The Importance of a Fast and Accurate Development Environment00:49:09 Being Brand-Driven vs. Data-Driven00:54:40 The Value of Customer Feedback Signal01:09:49 Capturing Attention through Creative Marketing01:11:26 Building Brand Recognition and Authenticity01:12:53 The Challenges of Marketing Technical Products01:13:56 The Importance of Caring and Taking Risks Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Santosh on X: https://x.com/SantoshYadavDev- Santosh' story: https://www.freecodecamp.org/news/my-journey-into-tech-from-slums-of-mumbai-to-my-own-apartment/- Tejas on X: https://x.com/tejaskumar_SummaryIn this episode, we deep dive into Angular and its related frameworks, along with the power of open source to change one's life—moving Santosh from the slums of Mumbai to Germany, where he now owns a home. If you're interested in Angular, web engineering, or open source, then this episode is for you.Takeaways1. Santosh Yadav started his career in software development with Windows development before transitioning to web development with Angular.2. Web development presented challenges such as cross-browser compatibility and deployment, which were not as prevalent in Windows development.3. Santosh emphasizes the importance of contributing to the open source community and shares his journey of contributing to the Angular community.4. Modern Angular has simplified the building blocks and introduced standalone components, making it easier to learn and use.5. Angular Universal and Angular SSR provide server-side rendering and file-based routing capabilities in Angular applications.6. Modern Angular has shifted from constructor-based injection to function parameter-based injection, which offers advantages such as easier use of services outside the constructor.7. Components in Angular should be minimal and focused on UI rendering, with logic and data dependencies handled by services.8. Constructive collaboration and empathy are essential in open source projects, and discussions and contributions should be made on GitHub rather than on social media platforms.9. Sharing personal stories and experiences in the open source community can inspire and motivate others. Education can be a powerful tool for overcoming challenging circumstances.10. Perseverance and hard work are key to achieving success.Chapters00:00 Santosh Yadav03:00 Introduction and Background11:03 Open Source Contributions32:30 Server-Side Rendering and File-Based Routing40:53 Modern Angular and Dependency Injection52:59 The Power of Nx as a Build Tool01:03:42 Constructive Collaboration in Open Source01:20:50 Living in the Slums and the Start of Santosh's Journey01:31:11 Burnout and the Need for Work-Life Balance01:44:51 Future Plans and Helping Others Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- SST: https://sst.dev- Jay on X: https://x.com/jayair- Tejas on X: https://x.com/tejaskumar_SummaryJay V, co-founder of the serverless framework SST, discusses the origins and purpose of SST. SST is an open-source framework for building applications on AWS and other cloud providers. It aims to make it easy to get started with building an application and scale as the application and team grow. SST differentiates itself by allowing developers to write infrastructure as code in TypeScript, providing abstractions that simplify the complexity of serverless applications.The conversation also touches on the importance of positioning and messaging in marketing, the value of educational content and courses, and the role of community in building a following. In this final part of the conversation, we discuss the importance of building a community and reaching critical mass in order to grow a product. We also talk about the future plans for SST, including adding support for more frameworks and runtimes.Takeaways1. SST is an open-source framework for building applications on AWS and other cloud providers2. SST allows developers to write infrastructure as code in TypeScript, providing abstractions that simplify the complexity of serverless applications3. Next.js is considered the Kubernetes front end because it provides a batteries-included framework with many out-of-the-box features for React SSR apps.4. Positioning and messaging should be tied to the product and focused on addressing the needs and interests of the target audience.5. Founders and CEOs face challenges such as resistance to new ideas and the need to adapt to change.Chapters00:00 Jay V03:07 Introduction to Jay and SST17:22 SST's Approach to Infrastructure as Code21:30 Shift from CDK to Pulumi and Terraform29:01 Jay's Role as a Technical Founder31:20 Managed Services vs Kubernetes38:39 Building AI Agents and Using GPT-4 with SST40:11 Why Next.js is the Kubernetes Front End42:41 Limitations of Serverless Architecture46:36 The Importance of Positioning and Messaging52:48 The Value of Educational Content and Courses58:06 Building a Community and Following01:04:29 Building a Community and Reaching Critical Mass01:05:45 Future Plans: Adding Support for More Frameworks and Runtimes01:06:40 Staying Updated in the Tech Industry01:10:55 Challenges Faced by Founders and CEOs01:12:12 Creating High-Performing Teams01:25:11 The Importance of Familiarity and Trust in Communication Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- TBD: https://www.tbd.website/- Rizèl on X: https://x.com/blackgirlbytes- Tejas on X: https://x.com/tejaskumar_SummaryRizèl Scarlett, a developer advocate at TBD, discusses her experiences with GitHub Copilot, open source, and Web5. She shares how she enjoys engaging with skeptics and helping them understand new technologies. Rizèl also explains TBD and its SDKs, TBdex and Web5, which aim to enable global money exchange and provide decentralized identity verification.Takeaways1. Rizel enjoys engaging with skeptics and helping them understand new technologies.2. TBD is a company that focuses on enabling global money exchange and decentralized identity verification.3. TBdex is an SDK that facilitates the exchange of money, while Web5 supports TBdex through identity verification.4. Web5 utilizes decentralized identifiers and verifiable credentials to create a seamless and secure web experience.5. Decentralized identifiers and verifiable credentials offer convenience and selective disclosure of personal information.6. Digital identifiers have the potential to replace single sign-on methods and provide a standardized authentication protocol across the web.7. Interoperability among companies is a challenge for the adoption of Web5.8. Web5 can be used to build various applications, such as chat applications. Web5 is built on open web standards and offers a secure way to handle decentralized identity and share files.9. Diversity, equity, and inclusion are crucial in the tech industry, and efforts should be made to create positive and inclusive experiences for underrepresented groups.Chapters00:00:00 Rizèl Scarlett00:03:50 Introduction and Background00:12:52 Skepticism of Open Source00:17:01 Introduction to TBD and TBdex00:26:21 Web5: Creating a Seamless Web Experience00:27:38 Decentralized Identifiers and Verifiable Credentials00:33:54 Exploring the Potential of Digital Identifiers00:36:11 Building Decentralized Digital Identities with the Web5 SDK00:41:27 The Benefits and Challenges of Web500:49:26 The Future of Authentication: Web5 and Digital Identifiers01:05:21 Exploring the Potential of Web5 and Decentralized Identity01:09:08 Leveraging AI Technologies in the Web5 Ecosystem01:13:21 The Importance of Diversity, Equity, and Inclusion in Tech Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Turso: https://turso.tech- The Save File Podcast: https://www.youtube.com/playlist?list=PLGUwjXxvasIczMiiZ5joRlTA-PFydJZbb- Glauber on X: https://x.com/glcst- Tejas on X: https://x.com/tejaskumar_SummaryGlauber Costa, CEO of Turso Database, shares his journey from coding for the Linux kernel to co-founding Turso. He started contributing to open source in university and developed a passion for low-level programming. He joined RedHat and later joined a database company, which eventually pivoted into ScyllaDB, a NoSQL database.Glauber discusses the challenges and successes of building ScyllaDB and the importance of competition in driving innovation. After leaving ScyllaDB, he joined Datadog before deciding to start Turso. The opportunity to start a company arose, and Glauber and his co-founder, Pekka, took the leap.Turso is a database that is based on SQLite and focuses on data replication. It offers a cost-effective and easy way to replicate data to multiple locations, with a single URL that routes requests to the closest replica. Turso is not limited to web use cases and can be used for various applications. It provides read-your-own-writes consistency, ensuring that when a value is written, it can be immediately read.The term 'edge database' is not accurate for Turso, as it is more focused on data replication rather than edge compute. The confusion around the term 'edge' arises from the conflation of network edge and edge compute. In this conversation, we discuss the challenges and misconceptions surrounding the concept of the edge in web development.Glauber also explains how messaging and positioning are crucial in the success of a startup, and how validation should be carefully considered. He also highlights the importance of moving fast and adapting to the needs of users. He emphasizes that replication is a core feature of Turso, allowing for high availability and performance, and the ability to replicate data closer to users for faster access.Takeaways1. Turso is a database based on SQLite that specializes in data replication.2. The term 'edge database' is not accurate for Turso, as it focuses more on data replication than edge compute.3. Messaging and positioning are crucial in the success of a startup.4. It is important to carefully consider validation and not rely solely on positive feedback.5. Moving fast and adapting to user needs is essential for success.Chapters00:00 Glauber Costa03:21 Introduction and Background12:39 Pivoting from Operating System to Database27:15 Transition from ScyllaDB to Turso31:32 Timing and Market Conditions in Starting a Company56:31 Turso: A Database for Data Replication01:02:52 The Horizontal Nature of Databases01:06:03 Turso's Impressive Write Performance01:09:37 Turso's Versatility Beyond Web Use Cases01:16:19 The Need for Speed: Moving Fast and Adapting to User Needs01:38:31 Conclusion Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- OpenSauced blog post: https://opensauced.pizza/blog/how-we-saved-thousands-of-dollars-deploying-low-cost-open-source-ai-technologies- John on X: https://x.com/johncodezzz- Tejas on X: https://x.com/tejaskumar_SummaryJohn McBride discusses his experience deploying open-source AI technologies at scale with Kubernetes. He shares insights on building AI-enabled applications and the challenges of managing large-scale data engineering.The conversation focuses on the use of Kubernetes as a platform for running compute and the decision to use TimeScaleDB for storing time-series data and vectors. McBride also highlights the importance of data-intensive applications and recommends the book 'Designing Data-Intensive Applications' for further reading.The conversation discusses the process of migrating from OpenAI to an open-source large language model (LLM) inference engine. The decision to switch to an open-source LLM was driven by the need for cost optimization and the desire to have more control over the infrastructure. VLLM was chosen as the inference engine due to its compatibility with the OpenAI API and its performance. The migration process involved deploying Kubernetes, setting up node groups with GPUs, running VLLM pods, and using a Kubernetes service for load balancing.The conversation emphasizes the importance of choosing the right level of abstraction and understanding the trade-offs involved.Takeaways1. Building AI-enabled applications requires good mass-scale data engineering.2. Kubernetes is an excellent platform for servicing large-scale applications.3. TimeScaleDB, built on top of Postgres, is a suitable choice for storing time-series data and vectors.4. The book 'Designing Data-Intensive Applications' is recommended for understanding data-intensive application development.5. Choosing the right level of abstraction is important, and it depends on factors such as expertise, time constraints, and specific requirements.6. The use of Kubernetes can be complex and expensive, and it may not be necessary for all startups.7. The decision to adopt Kubernetes should consider the scale and needs of the company, as well as the operational burden it may bring.Chapters00:00 John McBride03:05 Introduction and Background07:24 Summary of the Blog Post12:15 The Role of Kubernetes in AI-Enabled Applications16:10 The Use of TimeScaleDB for Storing Time-Series Data and Vectors35:37 Migrating to an Open-Source LLM Inference Engine47:35 Deploying Kubernetes and Setting Up Node Groups55:14 Choosing VLLM as the Inference Engine1:02:21 The Migration Process: Deploying Kubernetes and Setting Up Node Groups1:08:02 Choosing the Right Level of Abstraction1:24:12 Challenges in Evaluating Language Model Performance1:31:41 Considerations for Adopting Kubernetes in Startups Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- OpenSauced: https://opensauced.pizza- OpenSauced Tour: https://www.youtube.com/watch?v=JCNjj19iDa4- The Secret Sauce Podcast: https://podcast.opensauced.pizza/episodes- Brian on X: https://x.com/bdougieyo- Tejas on X: https://x.com/tejaskumar_SummaryIn this episode, Brian Douglas (BDougie), the founder of OpenSauced discusses the evolution of the Jamstack, BDougie's career switch from sales to coding, and the inspiration behind OpenSauced. OpenSauced is a tool that provides deeper insights into GitHub repositories, filling the gap left by GitHub's limited insights feature. BDougie explains how OpenSauced sources data from the GitHub event feed and circumvents rate limiting. He also shares the vision for OpenSauced, which includes building a standard for successful open source projects and providing valuable metrics for maintainers and companies.OpenSauced focuses on the top-down approach to building their business, targeting large enterprise customers and establishing product-market fit with them. They prioritize building relationships with these customers and providing value to them, rather than focusing on charging individual developers for their product. They believe that the future of open source lies in telling stories with data and providing insights to enterprises. OpenSauced aims to be a long-term, sustainable business that scales to both enterprise and the broader community.The conversation explores measuring the impact of open source projects, including the influx of stars and the growth of the active community. We discuss the importance of repo pages and new features like the lottery factor and contributor confidence. We also touch on the challenges of contributor engagement and the need for proper governance in open source projects. The conversation then shifts to the difficulties of positioning and messaging for technical founder-led companies and the importance of storytelling. The episode concludes with a discussion on the value of talking to users and customers regularly.Takeaways1. OpenSauced is a tool that provides deeper insights into GitHub repositories, filling the gap left by GitHub's limited insights feature.2. OpenSauced sources data from the GitHub event feed and circumvents rate limiting to provide comprehensive and up-to-date information.3. The vision for OpenSauced is to build a standard for successful open source projects and provide valuable metrics for maintainers and companies.4. The tool includes features like contributor confidence, lottery factor, and YOLO coding to assess the health and sustainability of open source projects.Chapters00:00 Brian Douglas03:05 Introduction and Background09:44 The Evolution of the Jamstack14:45 OpenSauced and GitHub's Relationship32:17 Identifying the Problem with Hacktoberfest35:28 Insights and Metrics for Open Source Projects37:09 The Value of Open Sauce for Businesses43:40 The Shift in DevRel and Go-to-Market Strategies47:57 Top-Down vs Bottom-Up Approach in DevRel54:20 Balancing Top-Down and Bottom-Up Strategies01:02:59 The Importance of Establishing Product-Market Fit01:05:42 The Challenges of Building an Open Source Business01:06:57 Measuring the Impact of Open Source01:07:28 The Role of Repo Pages01:08:09 Understanding Contributor Engagement and Confidence01:09:11 The Importance of Governance in Open Source01:11:14 Positioning and Messaging for Technical Founder-Led Companies01:36:11 The Value of Regular Communication with Users and Customers Hosted on Acast. See acast.com/privacy for more information.

Links- CodeCrafters (sponsor): https://tej.as/codecrafters- Solid Final Form post: https://erikras.com/blog/solid-final-form-poc- Erik on X: https://x.com/erikras- Erik on GitHub: https://github.com/erikras- Tejas on X: https://x.com/tejaskumar_SummaryIn this conversation, Erik Rasmussen discusses his experiences with open source and public speaking, as well as the development and differences between Redux Form and React Final Form. He also explores the value of form libraries and the challenges of coupling and modularity.Additionally, he shares his thoughts on Solid.js and its approach to granular rendering, as well as the potential integration of Solid.js and Final Form for building forms. In this conversation, Erik Rasmussen discusses his experience building forms with Solid and Redux Form.He shares the motivation behind creating Redux Form as a library and the decision to open source it. Erik also talks about the challenges and rewards of maintaining open source projects and the importance of saying no to feature requests.He explores the use of XState on the server side and the benefits of using state machines and state charts. Finally, Erik reflects on the current state of Redux and Solid.js and offers lessons learned from his open source journey.Takeaways1. Open source work can lead to opportunities for public speaking at conferences.2. Form libraries like Redux Form and React Final Form provide valuable solutions for managing form state and validation.3. Modularity is important in library design to allow users to choose and include only the necessary functionality.4. Solid.js offers a different approach to rendering and state management, which can result in more efficient updates.5. Integrating Solid.js and Final Form could provide a powerful solution for building forms with granular rendering and reactivity.6. Maintaining open source projects requires balancing feature requests and maintaining scope.6. Using XState on the server side allows for modeling complex flows and maintaining state.7. State machines and state charts provide a visual way to understand and manage application logic.8. The Redux ecosystem is still relevant and evolving, while Solid.js offers a novel approach to building UIs.Chapters00:00 Erik Rasmussen03:56 Introduction and Early Experiences08:14 Getting into Public Speaking13:00 Redux Form and React Final Form30:01 Coupling and Modularity in Libraries32:32 Solid.js and Granular Rendering37:57 Solid.js and Final Form Integration42:15 Challenges with Solid.js Forms44:33 Building Forms with Solid and Redux Form45:57 Creating Redux Form as a Library49:22 Maintaining Open Source Projects52:30 Considerations for Open Sourcing Projects57:34 Using XState on the Server Side01:00:34 Understanding State Machines and State Charts01:11:22 The State of Redux and Solid.js01:18:32 Lessons Learned from Maintaining Open Source Projects Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Xata: https://xata.io- Tupu: https://tupu.io- Monica on X: https://x.com/monicasarbu- Tejas on X: https://x.com/tejaskumar_SummaryMonica Sarbu, the founder and CEO of Xata, shares the story of founding Xata. She discusses the challenges of being a woman founder in a male-dominated industry and the importance of open source in her career. Monica also talks about the transition from being a founder to a director at Elastic and the role of titles and hierarchy in organizations. She highlights the significance of happiness and motivation in building successful teams.Monica talks about the journey of building Xata, a Postgres data platform, and how it was inspired by the need she discovered while building Tupu. Xata aims to provide the usability of Airtable on top of a traditional database, with the goal of empowering companies to build products with fewer resources. The platform offers features like full-text search, schema migrations with zero downtime, and a spreadsheet-like UI. Monica also discusses the challenges of running a company and the importance of diversity and culture.Takeaways1. Monica Sarbu shares her journey from building Packetbeat to founding Xata.2. She discusses the challenges of being a woman founder in a male-dominated industry.3. Monica highlights the importance of open source in her career.4. She talks about the transition from being a founder to a director at Elastic and the role of titles and hierarchy in organizations.5. Monica emphasizes the significance of happiness and motivation in building successful teams.6. Xata was built to address the need Monica discovered while building Tupu, and aims to provide the usability of Airtable on top of a traditional database.7. The platform offers features like full-text search, schema migrations with zero downtime, and a spreadsheet-like UI.8. Monica emphasizes the importance of diversity and culture in the company, and the need to support and empower female engineers.9. She believes that every company's journey is different, and it's important for founders to have a plan and prioritize what is important to them.Chapters00:00 Monica Sarbu05:08 Introduction and Background07:14 Building Packetbeat and the Power of Open Source13:46 Differentiating Packetbeat from Other Monitoring Tools19:25 Challenges and Benefits of Building in a Crowded Market34:51 The Importance of Happiness and Motivation in Building Teams48:27 The Relationship Between Tupu and Zeta50:15 The State of Tupu and the Challenges of Non-Profit Organizations56:04 The Journey of Zeta's Development58:26 Zeta's Full-Text Search and Postgres Compatibility01:01:23 Zero Downtime Migrations and Direct Postgres Interfacing01:04:33 Zeta's Roadmap and Self-Hosting Capabilities01:10:35 The Importance of Diversity and Culture at Zeta01:18:26 Zeta's Chat GPT Feature and Future Plans01:21:04 The Challenges and Priorities of Running a Company01:31:29 The Importance of Diversity and Empowering Women Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Rachel's book "The Tech Career Survival Guide": https://nearestnabors.substack.com/- Rachel on X: https://x.com/rachelnaborsSummaryRachel Nabors (they/them), a developer relations expert with an incredible track record discusses their career journey and the challenges of pricing and valuing their work in the developer relations industry. They emphasize the importance of knowing your worth and setting appropriate hourly rates based on your skills and the value you bring to the table. Rachel also highlights the need for building trusted relationships with your community and collaborating with companies to create products that align with your audience's needs.Takeaways1. Know your worth and set appropriate hourly rates based on your skills and the value you bring to the table.2. Build trusted relationships with your community and collaborate with companies to create products that align with your audience's needs.3. Acknowledge the transactional nature of the influencer industry but maintain your values and advocate for fair compensation.4. Balance the tension between working for a company and maintaining your integrity by establishing collaboration agreements that emphasize mutual benefit.5. DevRel should be involved in shaping the product and providing valuable feedback.6. The line between DevRel and marketing should be clarified to avoid undervaluing the engineering contributions of DevRel.7. The role of DevRel varies depending on the stage of the company, with more need for DevRel in early-stage or large companies.8. Documentation plays a crucial role in learning React, and progressive disclosure is an effective pattern for presenting information. User experience is crucial in documentation, and features like AI-generated pop-ups and special links can greatly enhance the user's understanding and navigation.9. People often discover documentation through search engines like Google, so it's important to optimize content for search and provide solutions to common errors and problems.10. In workplace dynamics, it's important to communicate with managers about issues like dominating conversations and lack of participation, either directly or through anonymous feedback channels.Chapters00:00:00 Rachel Nabors00:02:49 Introduction and Career Background00:04:49 Running a Developer Relations Consultancy and Influencer Agency00:07:07 Pricing and Determining Your Worth00:11:11 Negotiating and Advocating for Fair Compensation00:15:59 Value-Based Pricing and Collaborations00:25:12 Maintaining Integrity in the Influencer Industry00:30:11 Balancing Work and Trust with Companies00:33:20 Collaboration Challenges between DevRel and Product/Engineering Teams00:39:20 The Evolution of DevRel: From Evangelists to Influencers00:47:30 The Importance of DevRel in Shaping the Product00:59:42 The Role of Documentation in Learning React01:06:17 Enhancing User Experience in Documentation01:09:19 Optimizing Documentation for Search and Problem Solving01:11:57 Conveying Core Knowledge and Creating Accessible Content01:15:28 Collaboration between Documentation Teams and Developer Advocates01:22:16 Navigating Workplace Dynamics and Communication Hosted on Acast. See acast.com/privacy for more information.

Links- Sponsors and Partners- Codecrafters (sponsor): https://tej.as/codecrafters- THAT Conference: https://www.thatconference.com/- Stately: https://stately.ai- Guest Content- Flightcontrol: https://www.flightcontrol.dev- Blitz.js: https://blitzjs.com/- Brandon on X: https://x.com/flybayer- Book Recommendations and Resources- Full type-safety for Next.js routes: https://www.flightcontrol.dev/blog/fix-nextjs-routing-to-have-full-type-safety- Obviously Awesome: https://www.aprildunford.com/books- Psych framework: https://andrewchen.com/psychd-funnel-conversion/- Tejas on X: https://x.com/tejaskumar_SummaryBrandon Bayer, the creator of Blitz.js and co-founder of Flightcontrol discusses his journey in open source and the challenges of building full-stack frameworks in the JavaScript ecosystem. He explains the motivation behind creating Flightcontrol, a platform-as-a-service for deploying production applications to your own AWS account.Brandon also shares insights into the pricing model of Flightcontrol and the trade-offs between using a platform-as-a-service and self-hosting with a VPS. He discusses the technical challenges of migrating from PlanetScale to AWS Aurora and highlights the benefits of using Flightcontrol for long-running function invocations.Flightcontrol was backed by Y Combinator (YC)—an experience that was instrumental in helping Flightcontrol raise funding and providing valuable mentorship and networking opportunities.Takeaways1. Building full-stack frameworks in the JavaScript ecosystem is challenging due to the complexity and fast-changing nature of the ecosystem.2. Flightcontrol is a platform-as-a-service that allows developers to deploy production applications to their own AWS account, providing reliability, flexibility, and performance.3. Self-hosting with a VPS offers more control and lower costs, but it requires more management and may not be suitable for large-scale startups.4. Flightcontrol enables arbitrarily long-running function invocations, making it suitable for tasks like web scraping and data processing.5. Flightcontrol is focused on removing barriers to adoption and improving their marketing and positioning6. The Y Combinator experience helped Flightcontrol raise funding and provided valuable mentorship and networking opportunitiesChapters00:00 Brandon Bayer03:41 Introduction and Background17:05 The Pricing Model of Flightcontrol and the Trade-Offs of Platform-as-a-Service vs. Self-Hosting53:23 Removing Barriers to Adoption1:00:23 Marketing and Positioning as a Reliable Platform as a Service1:13:07 Accepting the Truth and Embracing It1:22:55 The Impact of Y Combinator Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (Sponsor): https://tej.as/codecrafters- Outreachy: https://outreachy.org- Recurse Center: https://recurse.com- Tejas on X: https://x.com/tejaskumar_SummaryAnjana discusses her journey into tech, including her background in computational linguistics and her experience in various roles within the tech industry. She highlights the importance of following one's passion and finding meaning in work. The conversation also touches on the need for the tech industry to prioritize human well-being and collaboration over profit and productivity. In this conversation, I and Anjana Vakil discuss the importance of shifting our mindset from a focus on productivity and economic success to one that prioritizes human flourishing and collective well-being. We explore the toxic nature of the competitive scarcity mindset prevalent in the tech industry and advocate for a more collaborative and community-oriented approach. We emphasize the need to recognize the value of every individual and the interconnectedness of all living beings. We also discuss the role of technology in addressing global challenges and the responsibility of tech professionals to use their skills for the betterment of society.Takeaways1. Tech careers can be pursued by individuals from diverse backgrounds and with non-linear trajectories.2. Programs like the Recurse Center and Outreachy provide opportunities for career changers and underrepresented groups to gain experience and contribute to the tech industry.3. The tech industry should prioritize human well-being and collaboration over profit and productivity.4. Success should be measured by the impact on individuals, communities, and the environment, rather than financial gain.5. Tech professionals have the power to shape the direction of the industry and should use their privilege to advocate for positive change.6. Shifting our mindset from productivity and economic success to human flourishing and collective well-being is crucial.7. The toxic productivity and competitive scarcity mindset prevalent in the tech industry need to be challenged.8. Recognizing the value of every individual and the interconnectedness of all living beings is essential.9. Tech professionals have a responsibility to use their skills and technology for the betterment of society and to address global challenges.Chapters00:00 Anjana Vakil03:39 Anjana's Non-Linear Tech Career15:21 The Intersection of Tech and Computational Linguistics27:00 Redefining Success in Tech32:10 Using Privilege to Advocate for Change48:55 Shifting Mindsets: From Productivity to Human Flourishing53:09 Tech's Role in Addressing Global Challenges55:33 Practical Protocols for Coping with the Current Context59:23 Community: Central to Software Development01:05:03 Scarcity Mindset vs. Abundance Mindset01:17:13 Cooperative Mindset: Surviving Scarcity Together01:24:34 Tech's Responsibility: Solving the World's Problems Together01:29:25 Recognizing the Value of Every Individual and the Interconnectedness of All Hosted on Acast. See acast.com/privacy for more information.

LinksCodecrafters (sponsor): https://tej.as/codecraftersTHAT Conference: https://www.thatconference.com/Clark on X: https://x.com/theclarksellTHAT Conference on X: https://x.com/thatconferenceTejas on X: https://x.com/tejaskumar_SummaryClark Sell discusses the origins and purpose of THAT Conference, a multi-day conference for software engineers and their families. He emphasizes the importance of human connection and the need for conferences to provide a space for engineers to learn, grow, and connect with others in the industry. Clark also addresses the challenges of balancing technical and soft skills in conference programming and the value of attending conferences for personal and professional development.This conversation explores the challenges and complexities of organizing a large conference, focusing on the specific example of That Conference. The chapters cover topics such as the difficulties of booking venues and the long-term contracts and financial commitments involved.TakeawaysFinding your why and being clear about your motivations is essential when starting a conference.Conferences should prioritize the human side of tech, offering a balance of technical and soft skills talks to help engineers become better individuals and professionals.Attending conferences can have a significant impact on mental health and well-being, especially for remote workers who may feel isolated in their careers.Companies should recognize the value of conferences and allocate budget for employees to attend, as it contributes to their personal and professional development.Organizing a large conference involves challenges such as booking venues and dealing with long-term contracts and financial commitments.Sponsors play a crucial role in supporting conferences and their involvement can be both sought after and initiated by the organizers.Building a tribe of organizers and engaging with other conference organizers can provide valuable support and insights.Chapters00:00 Clark Sell06:49 Starting That Conference15:40 The Purpose of That Conference28:53 The Importance of Human Connection33:18 The Value of Attending Conferences37:21 Agent Conf and the Importance of Tech39:13 Organic Panel Discussion and Open Spaces40:04 Exploring New Conference Formats41:02 The Importance of Open Spaces41:59 Blowing Up the Conference Format44:03 The Challenge of Selling White Spaces45:33 The Role of Hackathons46:27 Building a Custom Conference Platform48:07 Motivation Behind Building a Custom Platform50:07 Using Google Sheets as the Front End51:52 The Stack and Open Source Nature of the Platform55:19 Refactoring and Rebuilding the Platform59:05 The Challenges of Organizing a Conference01:01:31 Encouraging Speakers to Put Effort into Submissions01:05:40 The Financial Challenges of Organizing a Conference01:09:52 Considering Dropping Food from the Conference01:11:06 Exploring a Kickstarter-like Model for Ticket Sales01:12:11 Challenges of Booking Venues01:12:54 Long-Term Contracts and Financial Commitments01:14:35 The Ugly Side of Contracts01:17:03 The Entrapment of Venue Commitments01:18:00 Financial Struggles and Commitments01:18:56 The Role of Sponsors01:20:27 Sales and Sponsorship Relationships01:24:08 Starting a Conference: Find Your Why01:25:39 Building a Tribe of Organizers01:26:33 Engaging with Other Organizers01:28:19 The Importance of Balance and Sustainability01:32:44 Contributing and Getting Involved with the Conference Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (Sponsor): https://codecrafters.io- Liveblocks: https://liveblocks.io- Steven on X: https://x.com/stevenfabre- Tejas on X: https://x.com/tejaskumar_SummarySteven Fabre, the co-founder of Liveblocks, shares his journey from a design-focused background to starting his own company. He discusses the importance of combining design and engineering skills and the challenges of building a collaborative dev tool. Steven also talks about the decision to raise venture capital and the trade-offs between being an indie developer and seeking VC funding. He shares insights on starting a company during the pandemic and dealing with stress and anxiety as a founder. Finally, he touches on the benefits and challenges of remote work.Liveblocks is a platform that enables developers to add real-time collaboration features to their applications. It offers low-level APIs and pre-built React components for easy integration. The key to effective remote work, according to Liveblocks, is being truly remote-first and having time zone overlap. They also emphasize the importance of being intentional about culture and recognition in a remote team. Liveblocks recently announced a new product called Text Editor, which provides integration to make any text editor collaborative. They are also launching comments and notifications out of beta.Takeaways1. Combining design and engineering skills can lead to building polished and visually appealing products.2. Starting a company around a problem you personally face can provide unique insights and timing advantages.3. Dealing with stress and anxiety as a founder requires finding a balance, prioritizing sleep, and maintaining a healthy lifestyle.4. Being truly remote-first and having time zone overlap are key to effective remote work.5. Being intentional about culture and recognition is important in a remote team.Chapters* [00:00:00] Steven Fabre* [00:03:34] Introduction and Background* [00:05:55] The Journey from Design to Starting Liveblocks* [00:10:15] The Role of Design Engineers in Building Polished Products* [00:17:45] The Trade-Offs of Indie Development vs. Venture Capital* [00:30:13] Dealing with Stress and Anxiety as a Founder* [00:33:54] Unlocking the Benefits of Remote Work* [00:37:36] Creating a Remote-First Culture* [00:43:34] Introducing Liveblocks: Enabling Real-Time Collaboration* [00:54:23] Unveiling the Future of Collaboration with Liveblocks* [01:04:45] Building a Useful and Non-Overwhelming Notification System* [01:07:55] The Importance of Positioning and Marketing* [01:12:51] Showing Momentum and Providing Value* [01:22:52] The Challenges of Being a CEO Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Stately: https://stately.ai- XState on GitHub: https://github.com/statelyai/xstate- David on X: https://x.com/davidkpiano- Tejas on X: https://x.com/tejaskumar_SummaryIn this conversation, David Khourshid (CEO, Stately.ai) discusses XState, a state management library that uses state machines and the actor model to solve complex state management problems. He explains that state management is not a problem in itself, but it becomes complex when frameworks and libraries expect state updates in different ways.XState provides a simpler model for managing complex state by using state machines and transitions triggered by events. David also introduces the concept of state charts, which take state machines to the next level by allowing for hierarchy and orthogonality. XState provides tools for visualizing state machines and helps identify modeling issues early in the software development lifecycle.We continue to discuss the use of agents in observing environments and the potential for building practical applications using state machines. David shares his journey of founding Stately and productizing XState, highlighting the challenges and lessons he has learned as a first-time CEO. They also touch on the importance of making mistakes, transitioning to a paid model, and the future plans for Stately.Takeaways- State management becomes complex when frameworks and libraries expect state updates in different ways.- XState provides a simpler model for managing complex state by using state machines and transitions triggered by events.- State charts, a more advanced form of state machines, allow for hierarchy and orthogonality.- State machines are useful in AI programming and can be used to build agents that observe environments and take actions based on goals.- As a first-time CEO, it is important to make mistakes, learn from them, and be open to continuous learning and improvement.- Transitioning to a paid model can help focus on users who have real use cases and are willing to pay for advanced features.Chapters[00:00:00] David Khourshid[00:03:17] Introduction and Background[00:05:28] The Problem of State Management[00:09:16] XState: A Solution for Complex State Management[00:13:27] XState and Conflict-Free Replicated Data Types (CRDTs)[00:15:55] State Machines and State Charts[00:29:45] Orthogonality and Modeling Complex States[00:33:11] The Value of State Machines in Software Development[00:35:32] The Use Cases for State Machines[00:39:40] Balancing Time Investment and Fast-Paced Development[00:45:20] The Connection Between State Machines and AI[00:50:47] The Potential of AI in Stately.ai[01:01:35] Understanding the Actor Model[01:09:19] Building a To-Do App with XState[01:10:17] Introduction to X-State and Actor Interface[01:11:32] Snapshot and State in X-State[01:12:54] Agents and Observing Environments[01:14:16] State Machines in AI Programming[01:15:17] Building State Machines for Practical Applications[01:16:52] State Machines and AI Limitations[01:18:34] Founding Stately and Productizing X-State[01:21:20] Challenges and Lessons as a First-Time CEO[01:24:46] Importance of Making Mistakes and Learning[01:27:03] Transitioning to a Paid Model[01:30:32] Future Plans for Stately Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/Codecrafters- Replay Protocol Examples: https://github.com/replayio/Protocol-Examples- Mark on X: https://x.com/acemarke- Tejas on X: https://x.com/tejaskumar_SummaryMark Erikson, the maintainer of Redux and developer at Replay.io, discusses the process of modernizing the Firefox DevTools UI (a React app!) and the challenges of code migration. He shares insights on migrating to TypeScript and the value of staying up to date with the latest techniques. Mark also explains how Replay captures and transmits data for debugging purposes. Replay is a tool that captures and replays browser interactions for debugging purposes. It requires a browser because extensions do not have the same privileged access as a browser.During the recording phase, Replay captures network data. The captured data is stored in a binary archive. When a user opens the debugger, the recording is downloaded and cached in the backend. The debugger includes a video playback feature, which is actually a series of JPEG images rendered on a canvas. The element picker in the debugger is a bespoke canvas that interacts with the paused browser process.In this conversation, Mark Erikson discusses the capabilities of Replay, a debugging tool for web applications. He explains how Replay allows developers to console log in replays, run code in the browser, and work with source maps and minified code. Mark also discusses the use of Replay in Node.js and the ability to manipulate events in replays. He highlights the backend API of Replay and the potential for future features such as root cause analysis and React time travel.Takeaways1. Modernizing legacy codebases requires careful planning and a step-by-step approach.2. Migrating to TypeScript can improve code maintainability and reduce bugs.3. Replay.io captures and transmits browser events and interactions for debugging purposes.4. Extensions do not have the same privileged access as a browser, which is why Replay requires a browser.5. Replay can be used in Node.js environments, and developers can manipulate events in replays to simulate different outcomes.6. Future features of Replay include root cause analysis and React time travel, which will further enhance the debugging experience for developers.Chapters00:00:00 Mark Erikson00:02:40 Introduction and Background00:03:59 Replay.io and Time Travel Debugger00:08:48 Modernizing the Codebase00:11:44 The Challenges of Code Migration00:13:39 Finding Joy in Legacy Code00:16:11 Migrating to TypeScript00:19:16 The Process of Modernization00:30:19 The Pressure and Value of Modernization00:35:47 The Trade-offs of Using the Latest Techniques00:37:12 Capturing and Transmitting Data in Replay00:38:11 Replay: Capturing and Replaying Browser Interactions00:45:56 Why Replay Requires a Browser00:46:51 Capturing Network Data and Security Concerns00:48:54 Recording and Storing the Binary Archive00:56:21 Downloading and Caching the Recording00:58:46 Pre-Processing and Caching Basic Data01:03:30 The Video Playback and Memory Snapshots01:10:39 Inspecting Elements and the Bespoke Canvas01:14:26 Building the Replay Debugger01:16:49 Replay's Capabilities01:18:12 Console Logging in Replays01:19:50 Running Code in the Browser01:20:51 Source Maps and Minified Code01:22:44 Shipping Source Maps01:25:41 Replay in Node.js01:26:12 Using Replay in the Terminal01:33:50 Manipulating Events in Replay01:38:02 Replay's Backend API01:51:33 Future Features: Root Cause Analysis and React Time Travel01:54:41 Closing Remarks Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Zephyr Cloud: https://zephyr-cloud.io/- Module Federation: https://www.npmjs.com/package/@module-federation/node- Tejas on X: https://x.com/tejaskumar_SummaryIn this conversation, Zack Chapple, CEO of Zephyr Cloud, discusses the concepts of module federation, micro frontends, and the role of Zephyr Cloud in simplifying developer workflows. He explains the evolution of module federation, its relationship with Webpack and RSPack, and the impact of these technologies on build times and developer productivity. The conversation delves into the evolution of micro front-end architecture, starting with the use of iframes and progressing to module federation. It explores the challenges of iframes, the benefits of lazy loading, and the finer control offered by module federation. The discussion also covers the founding of Zephyr Cloud and its innovative approach to deploying micro front-ends to the edge. Zack Chapple discusses the innovative features of Zephyr Cloud, including its seamless integration with module federation, real-time deployment to the edge, and observability capabilities. He also shares insights on the challenges and decision-making process for technical founders and CEOs.Takeaways1. Module federation and micro frontends are key concepts in modern web development, allowing for the decomposition and distribution of front-end applications.2. Zephyr Cloud simplifies the complexity of module federation and micro frontends, providing a platform that accelerates developer workflows and enhances production reliability for micro frontends.3. Finer control and deployment to the edge with module federation and Zephyr Cloud Zephyr Cloud enables real-time deployment to the edge, making it easy for developers to integrate with module federation and streamline the development process.4. The platform offers robust observability features, allowing users to monitor and analyze the impact of remotes on performance and user experience.5. Zack Chapple emphasizes the importance of aligning company values with personal values as a founder, highlighting the need for individualized approaches to leadership and decision-making.Chapters00:00 Zack Chapple03:49 Introduction and Overview of Topics05:49 The Birth of Zephyr Cloud and its Mission11:06 Understanding Module Federation and Micro Frontends30:05 RSPack, ESBuild, and the Future of Module Federation36:12 Evolution of Micro Front-End Architecture40:25 Challenges and Benefits of Lazy Loading56:50 Innovative Edge Deployment with Zephyr Cloud01:06:05 Revolutionizing Deployment with Zephyr Cloud01:11:55 Seamless Deployment and Rollbacks01:31:09 Navigating the CEO Journey Hosted on Acast. See acast.com/privacy for more information.

Links- CodeCrafters (sponsor): https://tej.as/codecrafters- Understanding RegEx Once and for All Post Series: https://www.codegram.com/blog/understanding-regex-once-and-for-all-part-one- RegEx 101: https://regex101.com/- (Golang to .d.ts) go2dts: https://github.com/fabien0102/go2dts- Svenja on LinkedIn: https://www.linkedin.com/in/svenjaschaefer/- Svenja on GitHub: https://github.com/slickepinne- Tejas on X: https://x.com/tejaskumar_SummaryIn this conversation, Svenja Schäfer, a development team lead at Thoughtbot, discusses her background, experience, and the importance of testing in software development. She shares her journey into tech, the value of testing, and the benefits of test-driven development. Svenja also talks about her work at Thoughtbot, a consulting agency that focuses on Ruby on Rails and JavaScript development. The conversation touches on the challenges of learning new technologies and the fast-paced nature of the industry. The importance of collaboration, taking breaks, and finding a balance between pairing and individual work is also highlighted.In this part of the conversation, Svenja and I discuss the importance of communication and belonging in remote teams. We also dive into the topic of regular expressions and how they can be used to accelerate robustness in testing. We also do a live coding exercise to demonstrate how regular expressions work. Svenja then shares her experience as a team lead and emphasizes the importance of maintaining a balance between coding and people management. She introduces a three-question communication framework to help manage time and prioritize tasks. The conversation concludes with a discussion on the significance of feedback and the importance of open and honest communication.Takeaways- Testing is essential in software development as it provides confidence, reduces errors, and helps developers understand the codebase.- Test-driven development (TDD) is a valuable approach that involves writing tests before implementing features, leading to more robust and maintainable code.- Collaboration and pairing can enhance productivity and code quality, but it's important to find a balance and allow for individual work and breaks.- Taking breaks and allowing time for the brain to reset can lead to fresh ideas and solutions.- Effective communication and a sense of belonging are crucial in remote teams.- Regular expressions can be a powerful tool for testing and accelerating robustness in software development.- Regular expressions can be used for email validation, form input validation, and searching in code editors.- Understanding the building blocks of regular expressions, such as the caret (^), dot (.), asterisk (*), and word boundaries, is essential for writing effective patterns.- Tools like regex101.com can be helpful for testing and experimenting with regular expressions. Regular expressions can be a powerful tool for searching and manipulating text.- It is important to be aware of the potential challenges and gotchas when using regular expressions.- As a team lead, it is important to maintain a balance between coding and people management.- Effective communication involves asking the right questions and providing feedback in a constructive manner.- Prioritizing tasks and managing time can be achieved through frameworks like the three-question communication framework.Chapters00:00 Svenja Schäfer03:39 Introduction and Background11:59 Challenges and Learning in the Fast-Paced Tech Industry19:42 Staying Up-to-Date with Evolving Technologies50:42 Understanding the Building Blocks of Regular Expressions58:48 Live Coding Exercise: Matching Words with Regular Expressions Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (Sponsor): https://tej.as/codecrafters- Codepen: https://codepen.io- TailwindCSS Play CDN: https://tailwindcss.com/docs/installation/play-cdn- Chris on X: https://x.com/chriscoyier- Tejas on X: https://x.com/tejaskumar_SummaryIn this episode, Chris Coyier (CEO of CodePen) discusses his background and the projects he is involved in, including CSS-Tricks and CodePen. He talks about the workload and challenges of running these projects, particularly the complexities of managing advertising and the business models. Chris also shares insights into the tech stack used at CodePen, including Next.js and GraphQL. He highlights the benefits of GraphQL and the code generation tool, which helps ensure data consistency and type safety. Finally, he discusses the future plans for CodePen, including the adoption of server components. In this part of the conversation, Chris Coyier and Tejas Kumar discuss the Apollo code gen and type checking, the features of CodePen 2.0, the balance between simplicity and complexity, NPM install in CodePen, NPM support in CodePen 2.0, and the differences between ESM and CommonJS. In this conversation, Chris Coyier, the co-founder of CodePen, discusses various topics related to CodePen's architecture, development stack, and future plans. He talks about the use of CommonJS and GraphQL, the transpilation process in CodePen, the serverless architecture and Lambda functions, onboarding and familiarity with CodePen's codebase, staying up-to-date with industry trends, CodePen's design system, using Tailwind CSS in CodePen, the data layer in CodePen, and the potential acquisition of CodePen.Takeaways1. Running projects like CodePen/CSS-Tricks involves a significant workload, including managing advertising and the business models.2. The tech stack at CodePen includes Next.js and GraphQL, which provide powerful tools for building and managing web applications.3. Code generation with tools like Apollo helps ensure data consistency and type safety in GraphQL queries.4. Onboarding and becoming familiar with CodePen's codebase is relatively straightforward.5. Tailwind CSS can be used in CodePen by linking to a CDN-hosted URL.Chapters00:00:00 Chris Coyier00:03:27 Introduction and Background00:06:49 Running CSS-Tricks and CodePen00:12:45 Workload and Challenges00:25:37 Moving to Next.js00:29:49 Server Components and Future Plans00:32:27 Code Generation with Apollo00:34:10 Apollo Code Gen and Type Checking00:38:45 CodePen 2.0 Features00:46:43 Simplicity vs Complexity00:48:08 NPM Install and CodePen00:54:50 NPM Support in CodePen 2.000:59:12 ESM vs CommonJS01:01:54 Common JS and GraphQL01:02:31 CodePen's Architecture and Transpilation01:04:58 Serverless Architecture and Lambda Functions01:08:14 Onboarding and Familiarity with CodePen's Codebase01:08:42 Staying Up-to-Date with Industry Trends01:12:46 CodePen's Design System01:20:48 Using Tailwind CSS in CodePen01:25:01 CodePen's Data Layer01:29:03 AI Features and CodePen 2.001:31:26 Potential Acquisition of CodePen Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Improving Wix Performance: https://www.smashingmagazine.com/2021/11/improving-performance-wix-websites-case-study/- Dan on X: https://x.com/danshappir- Tejas on X: https://x.com/tejaskumar_SummaryIn this episode, Dan Shappir discusses his journey in web performance, starting from gaming networks before the web. He explains the web vs. internet distinction, offline-first web apps, and remote access solutions. Dan's role at Next Insurance as a performance tech lead is highlighted. The talk covers improving browser performance, server-side rendering at Wix, modern CSS, CDNs, backend issues, and encapsulation impacts. Dan and Tejas discuss the BF cache's workings, browser compatibility, and telemetry impacts. Tips for staying updated in tech are shared, emphasizing passion and teaching. The episode concludes with support for Gaza and the Speculation Rules API.Takeaways1. Avoid overloading the browser with excessive JavaScript, CSS, and HTML.2. Keep things small and lean to improve performance.3. Implement server-side rendering, use modern CSS, and leverage caching with CDNs to enhance performance.4. To stay relevant in the tech industry, follow your passion, accept that you can't know everything, and focus on understanding core concepts rather than chasing every new technology.5. The BF cache (back-forward cache) allows browsers to store a memory snapshot of a web page when the user navigates away, enabling instant retrieval when the user returns.Chapters00:00 Introduction and Honoring the Situation01:17 Dan's Background and Early Career07:46 Dan's Journey into Web Performance15:09 Offline-First Web Application25:34 Joining Wix and Improving Performance34:09 Transition to Next Insurance45:46 The Beauty of Constraints59:13 Using CSS for Layout01:04:12 Backend Performance Issues01:20:30 BF Cache01:25:32 Performance Strategies01:31:25 Advice for Staying Relevant in Tech01:42:42 Speculation Rules API01:43:14 Resource Hints: Prefetch and Preload01:48:12 Script Tags and JSON Representation01:51:39 Closing Remarks and Homework Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- GeekyAnts: https://geekyants.com- Sanket on X: https://x.com/sanketsahu- Tejas on X: https://x.com/tejaskumar_SummarySanket Sahu, founder and CEO of GeekyAnts, built a successful IT consulting company focused on web and mobile app development. Starting as a freelancer, he scaled the company to over 400 people, emphasizing problem-solving and strong culture. GeekyAnts began contributing to open source with NativeBase, transforming from a web shop to a mobile and web shop. This boosted their reputation, leading to global requests and organizing the largest React Native meetup group.They developed GlueStack, a full-stack framework, and GlueStack UI, a component library prioritizing accessibility and performance. GeekyAnts explores AI for code generation and AI-driven workflows, building an engineering studio with a user-first and AI approach. They emphasize evolving every six months, customer focus, and quarterly OKRs. The future involves productized services, dev tools, and internal products.In this episode, you will learn how Sanket Sahu built GeekyAnts from freelancing to a 400+ team, contributed to open source with NativeBase, and leveraged AI for growth. Discover their emphasis on problem-solving, culture, evolving every six months, and future plans involving productized services and dev tools.Takeaways1. Problem-Solving Attitude: Building a successful IT consulting company requires a problem-solving mindset at every level.2. Open Source Contributions: Contributing to open source can build your brand and establish credibility, as seen with GeekyAnts' release of NativeBase.3. Balancing Processes and Speed: Processes are essential for scaling but should not impede speed and innovation.4. AI Integration: Exploring AI for code generation and AI-driven workflows can positively impact business by increasing efficiency and problem-solving capabilities.5. Continual Evolution: Regularly evolving and rebuilding your company, as GeekyAnts does every six months, is crucial for sustained growth and adaptation.Chapters00:00 Introduction and Background 05:46 Starting Geeky Ants and Scaling to 400+ People 10:15 Transition from Developer to Founder 13:44 The Importance of Problem-Solving and Culture 19:05 Adapting to Changing Environments and Roles 26:04 The Role of Open Source Contributions 32:01 GeekyAnts' Journey into Open Source and React Native 38:15 The Impact of Open Source on GeekyAnts' Reputation 41:16 GeekyAnts: From Web Shop to Mobile Plus Web Shop 48:03 Solving Fragmentation and Unifying React Native 52:27 Introducing GlueStack: A Framework for Full-Stack Applications 56:15 GlueStack UI: Prioritizing Accessibility and Performance 01:03:59 Focusing on Visual Accessibility and AI 01:05:45 Exploring AI in Code Generation and Workflows 01:08:08 The Impact of AI on Business 01:10:05 Building an Engineering Studio with a User-First and AI Approach 01:20:10 The Importance of Evolving and Rebuilding 01:26:57 Using Quarterly OKRs for Planning and Objectives 01:29:57 The Future of GeekyAnts: Productized Services, Dev Tools, and Internal Products Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Shruti on X: https://x.com/shrutikapoor08- Slack Kit design system: https://slack.engineering/the-gradual-design-system-how-we-built-slack-kit/- Tejas on X: https://x.com/tejaskumar_SummaryShruti Kapoor, a member of technical staff at Slack, discusses her role, the impact of Slack on users, and recent redesign efforts. She covers the patenting process, technical implementation of features like clips and huddles using Amazon S3 and Chime SDK, and front-end development practices at Slack.Shruti also shares insights into Slack's interview process and compares it to Tejas' experience at Spotify, discussing the use of 'for' loops in interviews and her approach to code review. She concludes with thoughts on choosing between startups and big tech companies and the importance of diversity and inclusion in the industry.Takeaways1. Slack ships code frequently, even on Fridays, and rolls back quickly if issues arise.2. The redesign aims to reduce cognitive overload and enhance user experience.3. User feedback is crucial and actively gathered from social media, Zendesk tickets, and user research.4. Slack's interview process includes breaks and at-home assignments, focusing on both technical skills and empathy.5. Diversity and inclusion are vital, with efforts to ensure equal representation in technical discussions and panels.Chapters00:00 Shruti Kapoor09:39 Working at Slack and Impact on Users18:35 Redesigning Slack and User Feedback33:00 Patenting and Inventing42:39 Clips and Huddles51:40 Design System and Front-end56:02 Testing and Iteration57:59 Career Journey and Joining Slack01:00:38 Slack's Interview Process01:01:38 At-Home Assignment01:02:35 Comparison with Spotify's Interview Process01:03:34 Technical Interview Experience at Spotify01:05:02 Preference for Functional Programming01:05:43 Using 'for' Loop Instead of 'reduce'01:06:39 Approach to Code Review01:08:35 Code Review as a Learning Experience01:09:58 Testing Code during Code Review01:11:10 Choosing Between Startups and Big Tech01:11:39 Advantages and Trade-offs of Big Tech01:16:57 Advantages and Trade-offs of Startups01:18:47 Changing Teams in a Big Company01:22:51 Navigating Conversations about Changing Teams01:25:40 Role of Diversity and Inclusion in the Job Hosted on Acast. See acast.com/privacy for more information.

Links- CodeCrafters (sponsor): https://tej.as/codecrafters- Frame: https://brilliant.xyz/products/frame- Bobak on X: https://x.com/btavangarSummaryIn this episode, Bobak Tavangar, founder of Brilliant Labs, discusses the creation of the AR device Frame and the open-source assistant Noah. He shares his journey from working at Microsoft and Apple to founding his own AR company, emphasizing innovation, simplicity, and user transformation in AR. He highlights the limitations of relying on large companies and big budgets, and the unique focus of Frame on AI, user experience, security, and privacy. Frame aims to create open, hackable smart glasses, offering distinctive, lightweight designs and future style variations. The glasses integrate with smartphones, and the assistant Noah extends developer capabilities. Tavangar reflects on the lessons from Google Glass, the challenges of hardware creation, and the importance of design and purpose.Takeaways- Innovation in AR comes from taking unique paths.- Noah, an open-source assistant, enables a broader developer ecosystem.- Frame smart glasses focus on user experience, security, and privacy.- Combining openness with quality and curation is key.- Learn from Google Glass's successes and failures.Chapters00:00 - Introduction and Background 10:02 - The Genesis of Brilliant Labs and AR 14:52 - The Missing Ingredient in AR 28:18 - Noah: An Open-Source Assistant for Frame 31:20 - Differentiating Frame from Other AR Devices 35:09 - Creating Open and Hackable Smart Glasses 38:51 - The Third Path: Combining Openness with Quality and Curation 41:41 - Networking Human Experience 45:42 - The Dangers of Subsidizing Product Sales at a Loss 57:31 - The Future of Glasses: Smart and Indispensable 01:01:01 - Designing for Thinness, Weight, and Distinctive Style 01:04:49 - Local Models: Balancing Functionality and Hardware Constraints 01:08:03 - Lessons from Google Glass and the Importance of Purpose and Design 01:12:20 - Advice for Aspiring Hardware Founders 01:21:44 - Specifications of Frame: Battery Life and Charging 01:27:08 - The Only Rules That Matter: God and Physics Hosted on Acast. See acast.com/privacy for more information.

Links- CodeCrafters (Sponsor): https://tej.as/codecrafters- Daniel on X: https://x.com/danieljcafonso- Daniel's comic book talk: https://www.youtube.com/watch?v=TBxipPwGvHY&list=PL6EW34-Kvy8UfigafIhb5l4thKqOvMgIFSummaryDaniel Afonso shares his journey as a developer advocate, emphasizing his passion for educating developers through conference talks and comic books. He discusses using storytelling and entertainment to explain complex technical topics, including fine-grained reactivity with Marvel's Watchers as an analogy. He addresses overcoming imposter syndrome by learning and presenting topics he initially struggles with and offers tips for creating effective Call for Proposals (CFPs). This episode educates listeners on how tech conferences work and how to secure speaking spots, highlighting the importance of passion, authenticity, and personal experiences in talks, the role of storytelling, and the need for diversity and empathy in developer relations. We also discuss the significance of growth and change in professional environments.Takeaways- Embrace opportunities for growth and learning to overcome imposter syndrome.- Use storytelling and entertainment in presentations to make them engaging and memorable.- Passion and authenticity are key in delivering engaging talks.- Diversity in conference talks is important to bring different perspectives and ideas to the audience.- Empathy is crucial in developer relations and understanding the needs and struggles of others.Chapters00:00 Daniel Afonso03:18 Introduction06:22 Imposter Syndrome and Conference Speaking12:14 Using Comic Books to Teach Technical Topics25:17 Explaining Fine-Grained Reactivity with Watchers33:12 The Process of Eliminating Imposter Syndrome35:26 Creating Effective CFPs01:00:43 The Importance of Diversity in Conference Talks01:07:18 Passion and Authenticity in Speaking01:26:23 The Importance of Empathy in Developer Relations01:37:21 The Importance of Recognizing Personal Value Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (sponsor): https://tej.as/codecrafters- Guillermo on 𝕏: https://x.com/rauchg- Vercel: https://vercel.com- Latency Numbers Every Frontend Developer Should Know: https://vercel.com/blog/latency-numbers-every-web-developer-should-know- Latency Numbers Every Programmer Should Know: https://brenocon.com/dean_perf.htmlSummaryIn this discussion with Guillermo Rauch (creator of Socket.io, Next.js, and Vercel CEO), we cover open source, latency, software as physical systems, PPR, distributed systems, edge computing, Vercel’s data centers, AWS/Azure partnerships, reducing cold starts, and balancing quality with rapid shipping.Takeaways- Starting from a solid open-source background.- Understanding latency is crucial for optimizing user experience.- Viewing software as physical systems aids in performance and scalability.- Partial pre-rendering (PPR) improves performance by merging static pre-rendering with dynamic server-side rendering.- Globally distributed systems face challenges like data residency, cost, and compliance.- Edge computing is key to enhancing website performance and user experience.- Vercel uses edge computing for fast data transfer and performance.- Vercel’s infrastructure includes mega data centers and partnerships with AWS and Azure.- Reducing cold start times is a Vercel priority, with significant advancements.- Maintaining high quality and attention to detail is crucial, even with rapid shipping.Chapters00:00 Guillermo Rauch03:42 Introduction and Background11:55 Importance of Latency32:24 Challenges of Globally Distributed Systems43:11 Power of Edge Computing53:18 Edge as the Blessed Path Hosted on Acast. See acast.com/privacy for more information.

LinksCodecrafters (Sponsor): https://tej.as/codecraftersStately: https://stately.aiClerk: https://clerk.comJeff on 𝕏: https://x.com/jescalanSummaryIn this episode, Jeff Escalante (Director of Engineering at Clerk.com) discusses his shift from web development to management, emphasizing replacing oneself as an IC, expanding vision, and acting at the promotion level. He covers leveling employees, handling interview ambiguity, prioritizing customer needs, using Clerk’s feedback system, and choosing tools like ProductLane. The talk also highlights evaluating tech skills, being authentic at work, and balancing honesty with team safety.Takeaways1. Promotions and Management: Manage current duties before moving to management; promotions should reflect demonstrated behavior and vision, with clear guidelines and support from companies.2. Handling Ambiguity and Feedback: Address ambiguity in interviews with thoughtful analysis and solutions; prioritize customer feedback and tech debt using centralized systems.3. Choosing Software and Partnerships: Select software based on integration and vendor responsiveness; collaborate with smaller companies for mutual benefits.4. Tech Skills and Authenticity: Evaluate tech skills and adaptability in interviews; be authentic while adapting to work contexts.5. Relationships and Communication: Balance honesty and trust in relationships; respect communication preferences to build genuine connections. Jeff's handbook offers valuable insights for engineering teams.Chapters00:00 Jeff Escalante04:40 Introduction and Background07:52 Starting Out in Web Development13:39 Transitioning to Management at HashiCorp17:42 Working on Websites and Next.js29:49 Promotions and Expanding Field of Vision36:43 Navigating Promotions and Expectations41:16 Dealing with Frustration and Finding New Opportunities41:50 The Importance of Properly Leveling Employees43:21 Strategies for Leveling Employees47:09 Handling Ambiguity in Interviews50:48 The Value of Conversation in Defining Projects53:21 Determining Comfort Levels in Ambiguity53:54 The Vision-Scope Leveling Question58:23 Prioritizing Customer Needs and Tech Debt01:01:02 Navigating the Chaos of Undefined Spaces01:05:55 Listening to Customer Feedback at Clerk01:12:07 Importance of Centralized Feedback System01:12:56 Challenges in Mapping Feedback to Projects01:15:47 Choosing Product Lane over Other Tools01:20:17 Value of Partnerships and Investing in Software01:23:51 The Third Pillar: Evaluating Tech Skills and Handling Ambiguity01:29:55 Honoring Context and Being Your Full Self01:31:43 Navigating Personal and Professional Relationships01:39:02 Balancing Honesty and Building Genuine Relationships01:40:05 Closing Remarks and Handbook Release Hosted on Acast. See acast.com/privacy for more information.

Let's stay in touch? https://twitter.com/tejaskumar_Links- Codecrafters (Sponsor): https://tej.as/codecrafters- Stately.ai (Sponsor): https://stately.ai- Matt on X: https://x.com/biilmann- Netlify: https://netlify.comSummaryIn this podcast episode, Mathias Biilmann, co-founder and CEO of Netlify, discusses the evolution of Netlify and the invention of the term "Jamstack" in the serverless landscape. Throughout this conversation, Biilmann shares essential life lessons for CEOs and aspiring entrepreneurs, delving deep into the engineering challenges and successes of building Netlify.Takeaways- Engineering Innovation: Netlify's journey began with a strong focus on engineering excellence, introducing innovative solutions like deploy previews and immutable deploys. This podcast highlights how Netlify revolutionized the web UI layer, now moving towards exciting uses of AI and open source technologies.- Jamstack and Serverless Architecture: Biilmann discusses the significance of the Jamstack approach and serverless functions in scaling Netlify's architecture. The platform's ability to handle high traffic and resist DDoS attacks is emphasized, showcasing the robustness of its engineering.- CEO Insights and Life Lessons: As CEO, Biilmann reflects on the strategic decisions made during Netlify's growth, from handling large enterprise clients like Unilever to implementing a Netlify-specific CDN. His insights provide valuable life lessons for listeners interested in technology leadership.- AI and Artificial Intelligence: The integration of AI into Netlify's platform is a focal point, with AI features enhancing user experience and operational efficiency. The podcast discusses AI-powered features like deploy diagnostics and AI responses in tools like Slack, which align with the latest trends in artificial intelligence and VR.- Open Source and Community Engagement: Open sourcing parts of Netlify's platform has contributed significantly to its community engagement. This podcast episode explores how open source principles are integral to Netlify's development and how they resonate with broader engineering practices.- The Role of a Founder CEO: Reflecting on the podcast, Matt shares life lessons on the evolving role of a CEO in the tech industry. From coding to strategic decision-making, the responsibilities vary but always aim to add significant value to the business.Chapters00:00 Matt Biilmann05:23 Introduction and Background08:36 The Vision for Netlify11:24 Challenges and Resistance14:15 Self-Belief and Conviction17:08 The Git-Centric Workflow33:24 Scaling to Functions and Custom CDN38:03 Building a Software-Only CDN39:27 Open Sourcing Netlify41:28 Separation of Concerns41:50 The Role of the CEO and Founder44:58 Handling Traffic Spikes and DDoS Attacks54:42 The Importance of a Free Tier56:49 Bottom-Up Approach and Enterprise Selling01:02:54 The Evolution of Revenue Generation01:04:42 The Power of Developer Advocacy01:06:29 Handling Large Enterprise Clients01:07:50 Netlify's Enterprise Customers01:08:37 Improvements to Netlify's Local Development Experience01:09:37 Simplifying Adapters for Frameworks01:10:36 Improving Caching for Dynamic Content01:11:33 New Features for Frameworks on Netlify01:14:27 Simplified Next.js Runtime on Netlify01:16:55 Long-Running Functions and Jobs01:21:44 AI Features and UI 2.001:25:31 Using AI to Improve Netlify's Product01:27:23 Shortening the Time from Code to Production01:32:37 The Role of a Founder CEO Hosted on Acast. See acast.com/privacy for more information.

Don't forget to share and subscribe. Follow along on 𝕏 at https://x.com/tejaskumar_Links- Codecrafters (sponsor): https://tej.as/codecrafters- THAT Conference (partner): https://www.thatconference.com- Artem on 𝕏: https://x.com/kettanaito- Epic Web: https://epicweb.dev- The Golden Rule of Assertions: https://www.epicweb.dev/the-golden-rule-of-assertions- The True Purpose of Testing: https://www.epicweb.dev/the-true-purpose-of-testingTakeaways- Automated testing is crucial for writing better and more reliable software.- Testing helps developers describe the intention behind the code and ensure that the implementation meets that intention.- Starting with a minimal functional prototype and then writing tests to verify its behavior is a practical approach to testing.- Mocking is a technique that helps establish testing boundaries and allows developers to focus on specific behaviors in their tests. Mocking allows you to model different scenarios and create the desired context for tests.- The testing setup phase is crucial and often underappreciated.- The golden rule of assertion states that a test should only fail if the intention behind the system is not met.- Mock Service Worker (MSW) is an API mocking library that uses the Service Worker API to intercept requests and supports both browser and Node.js environments. Open source sustainability is challenging, but financial support from companies can make it more sustainable.- MSW has gained financial support through programs and partnerships, allowing for further development and support for users.- Concurrent testing support in MSW allows for better performance and avoids shared state issues.- Async local storage is a powerful tool in Node.js that helps solve concurrency issues in testing.- Setting limitations and principles for open source projects helps maintain focus and manage the scope.- Saying no to contributions is important to maintain the project's vision and scope.- Adding tests to projects, even small ones, can provide value and ensure reliability.- The future of testing lies in making it more accessible and having a testing strategy in place.- Balancing speed and quality in testing requires finding a minimal viable test suite that provides value.- Automated testing is crucial for ensuring software works reliably in different circumstances.- The future of testing involves making it more accessible and promoting its importance in software development.Chapters00:00 Artem Zakharchenko08:13 The Importance of Automated Testing15:37 Artem's Role at Epic Web and Testing Workshops27:02 Future Plans for Epic Web and Workshops28:45 Understanding Mocking and Mocking Strategies31:51 Introduction to Mocking and Modeling Scenarios33:43 The Broad Use Case of Mocking35:20 Finding the Right Balance in Mocking36:40 The Golden Rule of Assertion39:19 Creation and Iterative Process of Mock Service Worker (MSW)45:10 Adding Support for Node.js in MSW52:47 Mocking WebSockets with MSW01:04:54 Open Source and Sustainability01:05:43 Supporting MSW01:07:16 Solving Issues with MSW01:08:22 Concurrent Testing Support01:10:38 Using Async Local Storage01:13:30 Strategies for Open Source Maintainers01:14:27 Balancing Work-Life and Open Source01:18:50 Saying No to Contributions01:26:03 Balancing Speed and Quality in Testing01:29:00 Adding Automated Testing to Projects01:33:49 The Future of Testing Hosted on Acast. See acast.com/privacy for more information.

Links:- https://tej.as/codecrafters (sponsor)- https://daily.dev- https://x.com/FrancescoCiull4- https://youtube.com/@francescociullaJoin the conversation on 𝕏 at https://x.com/tejaskumar_In this episode, Francesco Ciulla, a developer and advocate at Daily.dev, shares his journey from working at the European Space Agency to becoming a Docker captain and content creator. He discusses the role of Docker in the tech industry and the process of becoming a Docker captain. Francesco also addresses accusations and criticism he has faced as a content creator and emphasizes the importance of supporting each other on social media. He shares his experience working at the European Space Agency and the use of Docker in managing complex systems. Finally, Francesco talks about his focus on Rust and the benefits of starting a YouTube channel. Francesco Ciulla discusses his journey of learning in private and learning in public, emphasizing the value of documenting the learning process. He shares his motivation for creating content and the benefits of being an early adopter in a less crowded space.Francesco also talks about accepting and embracing introversion, and how it has influenced his teaching and content creation. He highlights the importance of putting pressure on oneself to grow and achieve goals, while maintaining a growth mindset and being brutally honest about one's abilities and aspirations. He emphasizes that it's never too late to pursue your passions and make a change in your career. Francesco also explains the role of a developer advocate and the importance of building trust and connections with developers. He discusses the unique model of daily.dev, a platform for developers, and how it relies on funding and community engagement. Francesco shares insights on measuring the effectiveness of dev rel work and provides tips for leveraging social media algorithms to increase visibility and engagement.Takeaways- It's never too late to pursue your passions and make a change in your career.- Developer advocates play a crucial role in building trust and connections between companies and developers.- The daily.dev platform relies on funding and community engagement to provide free content and services to developers.- Measuring the effectiveness of dev rel work can be challenging, but metrics such as social media growth and user engagement can be used as indicators.- Understanding the algorithms and audience of each social media platform is essential for maximizing visibility and engagement.Chapters00:00 Francesco Ciulla01:06 Becoming a Docker Captain14:08 Working at the European Space Agency28:36 Exploring Rust and Content Creation30:03 Learning in Private vs. Learning in Public34:02 Teaching and Documenting the Learning Process41:17 Accepting and Embracing Introversion46:17 Putting Pressure on Yourself to Grow53:51 Growth Mindset01:03:22 It's Never Too Late01:06:06 Understanding DevRel01:11:30 Daily.dev and the Free Model01:18:36 Measuring DevRel Success01:26:00 Algorithm Tricks for Social Media01:33:04 Closing Remarks Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (Sponsor): https://tej.as/codecrafters- Ujjwal on X: https://x.com/ryzokuken- Tejas on X: https://x.com/tejaskumar_Takeaways- TC39 is responsible for maintaining the JavaScript language specification and ensuring the evolution of the language.- Implementing JavaScript in browsers is a collaborative effort between companies like Google, Mozilla, and Apple, with Igalia playing a significant role.- Language evolution requires balancing the needs and perspectives of various stakeholders, including browser vendors, platform owners, and developers.- API design considerations include security, privacy, and the ability to isolate potential risks.- Moving slowly in language development is crucial to ensure stability and safety. The web is both a blessing and a curse, serving as a reliable and trustworthy platform for communication while also presenting challenges like disinformation.- Web technologies have become the de facto way of building interfaces, surpassing other methods and becoming a crucial part of the tech stack.- Internationalization in JavaScript is facilitated by the Intl suite, which provides building blocks for localizing content into different languages, currencies, and cultures.- Participating in the TC39 process involves engaging in discussions and providing feedback on proposals through GitHub repositories.- Respectful and inclusive discussions are essential in the TC39 process, fostering collaboration and ensuring the growth and improvement of the JavaScript language.- Internationalization plays a crucial role in making the web more accessible and inclusive, allowing people from different cultures and geographies to engage with online content. Technology needs to be more inclusive and adaptive to accommodate the needs of all users.- The bias in technology benefits those who are already privileged, and it is important to address this bias to create a more equitable tech ecosystem.- The web should be accessible to all, regardless of language or cultural background.Chapters00:00 Ujjwal Sharma05:00 Introduction and Background12:49 Implementing JavaScript in Browsers20:01 The Challenges of Language Evolution34:57 Balancing Stakeholder Perspectives in TC3937:45 The Importance of Moving Slowly in Language Development38:21 The Blessing and Curse of the Web45:11 The Journey of Temporal and Intl53:25 Participating in the TC39 Process01:06:38 The Philosophical Question of Accessibility01:09:59 The Need for a Broader Perspective01:11:00 The Bias in Technology01:15:10 The Divide Between English and Non-English Speakers01:19:35 The Challenge of Implementing Different Calendars01:24:28 The Role of AI in the Web01:30:08 Contributing to the TC39 Committee01:38:55 Dreaming Big for the Future Hosted on Acast. See acast.com/privacy for more information.

Links- Codecrafters (Sponsor): https://tej.as/codecrafters- Follow me on X: https://twitter.com/tejaskumar_- Follow Yoav on X: https://twitter.com/HamatoYogi- Qwik’s next leap - moving forward together: https://builder.io/blog/qwik-next-leap- Towards Qwik 2.0: Lighter, Faster, Better: https://builder.io/blog/qwik-2-coming-soon- Qwik Microfrontends TikTok clone: https://github.com/gioboa/qwik-tiktok-microfrontends- Qwik-angular: https://github.com/QwikDev/qwik-angular- Qwik-vue: https://github.com/mizchi/qwik-vue- Visual copilot v1: https://builder.io/blog/visual-copilotTakeaways- Builder.io is a visual headless CMS that allows developers to build websites and sections of websites using a visual editor.- The Builder.io ecosystem includes tools like Party Town and Mitosis, which help with managing third-party scripts and transforming code for different frameworks.- Developers can register their own components from their code base in Builder.io and easily connect them to the visual editor.- Builder.io can be used in collaboration with other CMS platforms and APIs, allowing for flexibility and integration with existing systems. Qwik is becoming an open-source project, detached from Builder.io, to encourage community involvement and contributions.- Qwik is well-positioned to address Core Web Vitals and improve Interaction to Next Paint (INP) scores.- Qwik UI and other ecosystem projects enhance the Qwik framework and provide additional functionality.- Qwik 2.x will introduce improvements such as out-of-order streaming and a better micro-front-end story.- The concept of Qwik Server Components is being explored, but it may not align with the server-first approach of Qwik.- Apple's support for PWAs remains a topic of discussion and debate.SummaryYoav Ganbar, a developer relations engineer at Builder.io, joins the podcast to discuss the visual headless CMS and its ecosystem. Yoav shares his background and how he ended up at Builder.io. He explains that Builder.io is a visual no-code tool that helps build websites and sections of websites, and it is framework-agnostic. Yoav also introduces the other tools in the Builder.io ecosystem, including Party Town and Mitosis. In this part of the conversation, Yoav Ganbar discusses the Visual Copilot V1 and the ecosystem, the use of Mitosis and Sveltosis in Builder.io, the core principles and unique selling points of Qwik, the implementation and debugging of Qwik, the upcoming Qwik 2.0 and community-driven development, the importance of understanding servers in web development, the journey of learning web development, and a big announcement made by Yoav Ganbar. In this conversation, Yoav Ganbar discusses the announcement that Qwik is becoming an open-source project, detached from Builder.io.Chapters00:00 Yoav Ganbar03:26 Introduction and Background06:33 Yoav's Journey to Builder11:26 Builder.io and the Ecosystem32:45 Mitosis33:58 Qwik: Core Principles and Unique Selling Points36:16 Qwik Implementation and Debugging39:39 Qwik 2.0 and Community-Driven Development49:14 Builder.io and the Use of Qwik58:20 The Importance of Understanding Servers in Web Development1:01:29 The Journey of Learning Web Development1:02:27 The Big Announcement1:02:36 Qwik Becoming Open Source1:03:35 Qwik and Core Web Vitals1:04:59 Qwik UI and Ecosystem Projects1:05:56 Moving to Qwik Dev and New Governance Model1:06:55 Benefits of Open Source and Community Ownership1:10:27 Improvements in Qwik 2.x1:15:12 Qwik and Core Web Vitals1:17:30 Out of Order Streaming in Qwik 2.x1:24:44 Qwik Server Components1:28:03 Apple and PWAs Hosted on Acast. See acast.com/privacy for more information.

Follow me on 𝕏: https://twitter.com/tejaskumar_Links- Sentry: https://sentry.io- Lazar on 𝕏: https://twitter.com/NikolovLazarIn this in-depth podcast episode, we delve into the world of Sentry, a powerful tool designed to enhance software performance and reliability. From the initial introduction to Sentry's comprehensive suite of features, we explore how Sentry instruments a broad array of software, ensuring peak performance and minimal errors. The discussion includes a comparative analysis with TypeScript, highlighting Sentry's unique approach to software instrumentation and its focus on privacy and security.We further investigate Sentry's capabilities in de-obfuscating code with source maps, offering insights into the nuanced differences between Replay.io, session replay technologies, and Sentry's innovative solutions. The spotlight shines on Sentry's dev-time monitoring, trace propagation within database transactions, and its distinct differentiators that set it apart from competitors. Notably, the episode covers Sentry's report on the most common pitfalls in apps, akin to a Spotify Wrapped but for software errors, providing a deep dive into error and stack proximity reporting with Sentry.Performance metrics, such as the Apdex score and Core Web Vitals, including Cumulative Layout Shift (CLS), are thoroughly examined, alongside strategies for mitigating CLS and addressing font-related issues like Flash of Unstyled Text (FOUT) and Flash of Invisible Text (FOIT). The episode proposes innovative solutions, such as tree shaking for font glyphs and dynamic font replacement to prevent layout shifts and text visibility problems.Listeners will gain insights into Sentry's internals, including its architecture, use of Rust, and data storage strategies. The episode also discusses the scale challenges Sentry has overcome and how Sentry employs its own tools for self-monitoring. The conversation concludes with guidance on when to avoid Sentry and reiterates best practices for utilizing Sentry to its full potential, ensuring listeners are equipped with the knowledge to tackle common software performance issues effectively.Chapters00:00 - Intro01:07 - Sponsor01:51 - Greetings02:53 - Defining Sentry's Suite of Features04:43 - How does Sentry instrument a wide variety of software?09:32 - Sentry compared to TypeScript12:31 - Sentry and Privacy16:57 - De-obfuscating Code with Source Maps19:46 - Replay.io vs. Session Replay and Sentry21:20 - Sentry Spotlight and Dev-Time Monitoring25:07 - Propagating a Trace inside a Database Transaction27:38 - Sentry Differentiators35:58 - Sentry Report of Most Common Pitfalls in Apps, like Spotify Wrapped but with Sentry39:42 - Children and error/stack proximity with Sentry reporting42:22 - The Apdex as a Performance Metric44:56 - Performance and Core Web Vitals49:20 - Cumulative Layout Shift (CLS)54:43 - Where does CLS happen in the rendering process and mitigation steps58:19 - Fonts as a source of CLS, FOUT (Flash of Unstyled Text), and FOIT (Flash of Invisible Text)01:05:11 - Free Open Source Project Idea: Tree Shaking for Font Glyphs01:05:57 - Replacing fonts when loaded to prevent CLS, FOIT, and FOUT01:08:51 - How Sentry helps with Core Web Vitals01:11:49 - Sentry Internals: Architecture, Data Stores, Rust01:17:21 - Scale Problems that Sentry went through01:19:12 - Does Sentry use Sentry? Sentry on Sentry01:21:13 - When to Avoid Sentry01:22:11 - Sentry Salient (Repeating) Best Practices01:26:10 - Conclusion Hosted on Acast. See acast.com/privacy for more information.

Follow me on 𝕏 for more: https://twitter.com/tejaskumar_Links- Kyle on 𝕏: https://twitter.com/getifyx- Vella.ai: https://vella.ai- Codecrafters (sponsor): https://tej.as/codecrafters- Stately (sponsor): https://stately.aiTakeaways- The You Don't Know JS books have been successful, with over 300,000 copies sold across all editions.- Kyle Simpson decided to move away from the traditional publishing model due to constraints and a desire for more creative freedom.- Giving away the books for free on GitHub has not negatively impacted sales, and many readers have chosen to support Kyle by purchasing the books.- Accessibility and making knowledge available to a wide audience are central to Kyle's approach.- There are multiple pathways to publishing, including traditional publishing, self-publishing, and platforms like Leanpub. Publishing with O'Reilly provides a prestigious reputation and distribution, while self-publishing offers more control and potentially higher royalties.- Get a Pub is Kyle's publishing assistance service for self-published authors, while Lean Pub is a platform for incremental publishing and distribution.- Education should be seen as an ongoing journey, and college degrees may become less relevant over time as the industry evolves.- Gatekeeping in the tech industry can be a barrier for those without formal education, but continuous learning and self-education can bridge the gap.- Rejection can be a catalyst for personal growth and the pursuit of knowledge, leading to impactful contributions and a deeper understanding of a subject.- Prioritizing knowledge and learning in the workplace is essential for personal and professional growth, and it's important to find a company that values continuous learning.- Learning should be seen as a continuous process, with a focus on understanding and deepening knowledge rather than just acquiring new skills.- Vella.ai is a venture that aims to prioritize user ownership of data and privacy, offering a local-first approach to AI and smart assistants.In this episode, Kyle Simpson discusses his experience as the author of the You Don't Know JS books and his decision to move away from the traditional publishing model. He shares the status and future plans of the second edition of the books and the impact of giving away the content for free on GitHub. Kyle emphasizes the importance of accessibility and making knowledge available to as many people as possible.Chapters- 00:00 Kyle Simpson- 04:59 Introduction and Background- 05:59 You Don't Know JS Books- 09:19 Status and Future Plans of the Second Edition- 10:13 Published Books in the Second Edition- 11:40 Books That May Not Be Written- 13:44 Authoring Experience and Constraints- 18:20 Giving Away the Book for Free on GitHub- 29:26 Accessibility and Publishing Dreams- 31:01 Pathways to Publishing- 39:44 Publishing with O'Reilly and Self-Publishing- 41:02 Get a Pub and Lean Pub- 47:46 Education, Gatekeeping, and Learning- 50:35 The Role of College and Continuous Learning- 58:43 Kyle's Rejection from Twitter and the You Don't Know JS Series- 01:11:45 Prioritizing Knowledge and Learning in the Workplace- 01:12:15 Becoming Less Employable and Unexpected Challenges- 01:13:57 The Misunderstanding of Tejas' Contract- 01:15:12 The Value of Specialization and Experience- 01:17:54 Learning as a Living Standard- 01:22:14 The Shift in Valuing Experience in Engineering- 01:25:16 The Dog Wagging the Tail in Tech- 01:28:00 Kyle's Venture: Vela.ai- 01:35:45 The Mission of Vela.ai Hosted on Acast. See acast.com/privacy for more information.

Follow us on 𝕏: https://twitter.com/tejaskumar_Dive into the cutting-edge of web development with our latest episode, focusing on SolidJS, React fatigue, and innovative JavaScript technologies. We kick off with an inspirational look at SolidJS, exploring why developers are shifting towards this reactive framework amidst growing React skepticism. Delve into the TC39 proposal for native JavaScript Signals and the burgeoning SolidStart ecosystem, underlining its appeal through ease of contribution compared to React.We unpack SolidJS documentation and Atila's journey into the project, highlighting the framework's accessibility for newcomers and contrasting it with React's complexity. The discussion extends to implementing Signals in React, evaluating the tangible benefits of performance optimizations, and detailing SolidJS's advantages and potential drawbacks.Stay tuned for insights into SolidStart's latest developments, the vibrant SolidJS community, and practical advice for migrating from other libraries. Special segments include a spotlight on codemods, the groundbreaking CrabNebula project, and leveraging Tauri with Rust for desktop applications. We explore Rust's benefits, the unique offerings of CrabNebula in DevTools, cloud solutions, and security audits, culminating with ways to engage with CrabNebula's initiatives.Wrapping up, Atila shares key takeaways on navigating the evolving web development landscape. Whether you're contending with React fatigue, curious about SolidJS, or interested in desktop app development with Tauri and Rust, this episode offers invaluable insights into modern web technologies and their practical applications.Links:- Atila on 𝕏: https://twitter.com/atilafassina- Atila on YouTube:  @AtilaDotIO  - SolidJS: https://solidjs.com- CrabNebula: https://crabnebula.dev- Tauri DevTools: https://devtools.crabnebula.dev- Tauri: https://tauri.appChapters00:00 - Intro02:59 - Welcome04:20 - Getting Inspired about SolidJS06:59 - React Fatigue: Doubts and Questions about React10:09 - Signals as Native JavaScript (TC39 Proposal)12:38 - SolidStart and Ecosystem21:01 - SolidJS Docs and How Atila Got Involved24:45 - React is Hard to Contribute To/SolidJS is Easier; Why?35:23 - Understanding SolidJS for newcomers40:33 - Signals in React46:38 - Do the minimal perf gains even matter?52:56 - SolidJS Pros and Cons56:45 - SolidStart Developments01:04:27 - SolidJS Community and Ryan01:07:39 - Migrating to SolidJS from another library01:12:28 - Codemods and Kent C. Dodds01:14:15 - CrabNebula01:15:57 - Tauri, Rust, and Desktop Apps with JavaScript01:21:13 - Rust: Benefits and Tradeoffs01:32:37 - CrabNebula offerings: DevTools for Tauri01:41:00 - CrabNebula offerings: Cloud01:42:17 - CrabNebula offerings: Security Audits01:44:46 - Getting involved with CrabNebula01:45:57 - Main Takeaway from Atila01:47:01 - Conclusion Hosted on Acast. See acast.com/privacy for more information.

Follow me on 𝕏: https://x.com/tejaskumar_Dive into the fascinating world of computing with our podcast episode titled "How do computers actually work? From electrons to hardware to the web." We unravel the mystery starting from the fundamental building blocks of technology—electrons, and how they power datacenters, to the intricacies of hardware and firmware. Journey through the critical layers of computing, including the OS kernel, CPU operations, memory management, and storage solutions. Security gets its due with an exploration of TPM, setting the stage for a deep dive into software architecture. We break down frontend technologies and backend infrastructure, covering everything from HTML and CSS to cloud computing and network protocols. The episode culminates with a discussion on CI/CD pipelines and the decision-making process in tech development. It's a comprehensive guide for anyone curious about the inner workings of computers and the internet.Chapters00:00 - Intro01:17 - Sponsor02:47 - Everything is a Stack, with Layers on Layers04:55 - The Lowest Layer: Subatomic Particles09:21 - Types of Current: AC and DC (Alternating and Direct Current)12:36 - How Datacenters use Electricity15:45 - The Next Layer: Hardware19:07 - The Next Layer: Firmware21:46 - The Next Layer: The OS Kernel24:21 - Diving Deeper: Motherboard27:59 - The OS Kernel29:43 - CPU, Threading, Multithreading, Hyperthreading, Clock Speed36:53 - Memory/RAM, Volatile Memory, Virtual Memory39:43 - Storage, Hard Drives, Solid State Drives41:33 - TPM (Trusted Platform Module)42:59 - The Next Layer: Software43:46 - Software Architecture47:08 - Frontend Deep Dive: HTML, HTMX, CSS, TailwindCSS, JavaScript, Accessibility, and Network59:53 - What happens when data fetching: TCP/IP stack, HTTP and SSL encryption, how data flows over the network and internet01:12:05 - Receiving a Network Request on the Backend, DNS, Firewalls, Load Balancing, SSL Termination, Reverse Proxies01:20:38 - Backend Architecture: Caches, Queues, Distributed Systems, Control Plane vs. Data Plane01:25:44 - Cloud Computing: Virtual Private Clouds (VPCs), Subnets, NATs01:28:30 - Adjusting Expectations for Frontend and Backend01:29:34 - CI/CD Pipelines, Webhooks, git-based deploys01:30:21 - Build it or buy it?01:31:18 - Conclusion Hosted on Acast. See acast.com/privacy for more information.

Follow us on 𝕏: https://twitter.com/tejaskumar_Links- Sentry: https://sentry.io- Epic Web: https://epicweb.dev- Kent's Website: https://kentcdodds.com- Remix: https://remix.runJoin us in this enlightening episode as we welcome Kent C. Dodds, a renowned figure in the web development community and a dear friend, known for his impactful contributions and innovative teaching methods. Dive deep into Kent's journey, from his initial steps in the tech world to becoming a pivotal voice in modern web development. Explore the evolution of the web, understanding the critical milestones and breaking changes that have shaped its current state. Discover the art of building modern web experiences that surpass user expectations, emphasizing the importance of web performance, and adopting an empathy-driven approach to software development.Kent shares his insights on why Remix stands out as a premier framework, addressing common challenges like the complexity of Next.js and the intricacies of nested routes. Gain valuable knowledge on making strategic decisions between client and server rendering in Remix, and the practical steps for migrating from Vite/SPA to React Server Components (RSCs) with Remix, highlighting the revolutionary potential of RSCs in enhancing web development.The conversation takes a personal turn as Kent discusses his experiences creating the wildly successful Epic React course, revealing his approach to course ideation, preparation, and the secret to staying organized amidst a busy schedule. Listen to inspiring stories from Kent's career at PayPal, his influence on his team, and the personal philosophies that contribute to his enduring happiness and success.Lastly, tackle the daunting task of dealing with legacy code with minimal coverage, offering strategies and insights to navigate and improve upon existing codebases efficiently.This episode is a treasure trove for developers, educators, and tech enthusiasts alike, filled with practical advice, inspiring stories, and a deep dive into the technologies and methodologies driving forward-thinking web development.Chapters00:00 - Intro01:35 - Sponsor02:58 - Greetings03:49 - Kent's Background and Experience05:53 - How did the Web get to where it is today?12:56 - Breaking Changes on the Web20:30 - Building Modern Web Experiences to Meet User Expectations24:07 - Web performance, spinners and loading state: building for users over developers33:03 - Empathy Driven Development; Software as an act of Service38:37 - Why is Remix the best?50:04 - "Next.js was too complex" explained56:00 - Nested Routes in Detail01:07:23 - Lever: Choosing between Client or Server rendering in Remix01:10:30 - Incrementally Migrating from Vite/SPA to React Server Components (RSCs) with Remix01:14:12 - React Server Components (RSCs) in Remix01:25:19 - Server Components and Composability; Kent's new talk on RSCs01:30:50 - Matt Pocock: how was Epic React an overnight success?01:34:29 - Hayat Rachi: How do you go through course ideation and prep?01:36:08 - Artem Zakharchenko: how are you so organized?01:39:13 - David Sancho: PayPal career, team influence, and why Kent seems happy all the time01:42:05 - Oluwatobiloba: how do you deal with a legacy code with minimal coverage?01:44:39 - Conclusion Hosted on Acast. See acast.com/privacy for more information.

Follow us on 𝕏: https://twitter.com/tejaskumar_In today's episode, we dive deep into the world of artificial intelligence, starting with a basic understanding of AI and the pivotal role of AI Engineers. We explore the pressing question: "Is AI going to take my job?" and differentiate between answer engines and search engines, highlighting their impacts on how we find information.Transitioning into web development, our discussion shifts towards CSS, covering advanced topics like view transitions, container queries, the :has selector, dynamic viewport units, and the debate on the necessity of JavaScript (JS) when CSS can offer powerful solutions.Further, we delve into the latest JavaScript updates, including the introduction of `Object.groupBy`, immutable array methods, and exciting new tools and frameworks like vlt (new npm), Bun, Tauri 2.0, and a discussion on modern JavaScript frameworks including Signals, Qwik, and React Forget, focusing on bundle size optimization.We also cover significant HTML developments, such as OpenUI, the new `selectmenu` and `popover` elements, the `dialog` element, and HTMX, offering insights into how these advancements are shaping the future of web development.Wrapping up, we conclude with reflections on the topics covered and their implications for developers and the broader tech community. Join us for an informative journey through the latest in AI and web development.LinksOramaSearch: https://oramasearch.comKarpathy's post: https://twitter.com/karpathy/status/1674873002314563584Rise of the AI Engineer: https://www.latent.space/p/ai-engineerPerplexity (Answer Engine): https://perplexity.aiKeel: https://keel.soKeelGPT: https://chat.openai.com/g/g-0xwNB1Azt-keelgptvlt: https://vlt.shBun: https://bun.shTauri: https://tauri.appOpenUI: https://open-ui.org/HTMX: https://htmx.org/Chapters00:00 - Intro01:53 - Sponsor02:43 - AI05:27 - AI Engineering: What is an AI Engineer?12:26 - Is AI going to take my job?22:53 - Answer Engines vs. Search Engines28:26 - CSS: View Transitions35:45 - CSS: Container Queries48:53 - CSS: :has selector50:41 - CSS: Dynamic Viewport Units54:22 - CSS: Why not just use JS?56:27 - JavaScript: Object.groupBy58:47 - JavaScript: Immutable Array Methods01:04:31 - JavaScript: vlt (new npm)01:08:09 - JavaScript: Bun01:10:47 - JavaScript: Tauri 2.001:15:26 - JavaScript: Frameworks, Signals, Qwik, Bundle Size, React Forget01:31:00 - HTML: OpenUI, selectmenu, popover01:34:20 - HTML: dialog element01:37:05 - HTML: HTMX01:45:31 - Conclusion Hosted on Acast. See acast.com/privacy for more information.

Follow us on 𝕏: https://x.com/tejaskumar_This episode is an introduction to the Contagious Code podcast, outlining the motivation behind the show, what listeners and viewers can expect, and how they can get involved. Episodes will air weekly for a season, where there are about 8 episodes total. Then, we will regroup and record another season that will air after a short break. Ideally, we keep episodes rolling, but we'll need to evaluate this in light of temporal and financial budgets.Chapters:00:00 Intro00:40 Motivation01:37 Podcast Format02:30 Motivation Part 203:57 How to Get Involved05:14 Sponsorships06:07 Conclusion Hosted on Acast. See acast.com/privacy for more information.