ConTejas Code Tejas Kumar

Links

Codecrafters (Sponsor): https://tej.as/codecraftersStately: https://stately.aiClerk: https://clerk.comJeff on 𝕏: https://x.com/jescalan
Summary
In 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.
Takeaways
1. 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.
Chapters
04:40 Introduction and Background
07:52 Starting Out in Web Development
13:39 Transitioning to Management at HashiCorp
17:42 Working on Websites and Next.js
29:49 Promotions and Expanding Field of Vision
36:43 Navigating Promotions and Expectations
41:16 Dealing with Frustration and Finding New Opportunities
41:50 The Importance of Properly Leveling Employees
43:21 Strategies for Leveling Employees
47:09 Handling Ambiguity in Interviews
50:48 The Value of Conversation in Defining Projects
53:21 Determining Comfort Levels in Ambiguity
53:54 The Vision-Scope Leveling Question
58:23 Prioritizing Customer Needs and Tech Debt
01:01:02 Navigating the Chaos of Undefined Spaces
01:05:55 Listening to Customer Feedback at Clerk
01:12:07 Importance of Centralized Feedback System
01:12:56 Challenges in Mapping Feedback to Projects
01:15:47 Choosing Product Lane over Other Tools
01:20:17 Value of Partnerships and Investing in Software
01:23:51 The Third Pillar: Evaluating Tech Skills and Handling Ambiguity
01:29:55 Honoring Context and Being Your Full Self
01:31:43 Navigating Personal and Professional Relationships
01:39:02 Balancing Honesty and Building Genuine Relationships
01: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.com
Summary
In 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.
Chapters
05:23 Introduction and Background
08:36 The Vision for Netlify
11:24 Challenges and Resistance
14:15 Self-Belief and Conviction
17:08 The Git-Centric Workflow
33:24 Scaling to Functions and Custom CDN
38:03 Building a Software-Only CDN
39:27 Open Sourcing Netlify
41:28 Separation of Concerns
41:50 The Role of the CEO and Founder
44:58 Handling Traffic Spikes and DDoS Attacks
54:42 The Importance of a Free Tier
56:49 Bottom-Up Approach and Enterprise Selling
01:02:54 The Evolution of Revenue Generation
01:04:42 The Power of Developer Advocacy
01:06:29 Handling Large Enterprise Clients
01:07:50 Netlify's Enterprise Customers
01:08:37 Improvements to Netlify's Local Development Experience
01:09:37 Simplifying Adapters for Frameworks
01:10:36 Improving Caching for Dynamic Content
01:11:33 New Features for Frameworks on Netlify
01:14:27 Simplified Next.js Runtime on Netlify
01:16:55 Long-Running Functions and Jobs
01:21:44 AI Features and UI 2.0
01:25:31 Using AI to Improve Netlify's Product
01:27:23 Shortening the Time from Code to Production
01: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-testing
Takeaways
- 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.
Chapters
08:13 The Importance of Automated Testing
15:37 Artem's Role at Epic Web and Testing Workshops
27:02 Future Plans for Epic Web and Workshops
28:45 Understanding Mocking and Mocking Strategies
31:51 Introduction to Mocking and Modeling Scenarios
33:43 The Broad Use Case of Mocking
35:20 Finding the Right Balance in Mocking
36:40 The Golden Rule of Assertion
39:19 Creation and Iterative Process of Mock Service Worker (MSW)
45:10 Adding Support for Node.js in MSW
52:47 Mocking WebSockets with MSW
01:04:54 Open Source and Sustainability
01:05:43 Supporting MSW
01:07:16 Solving Issues with MSW
01:08:22 Concurrent Testing Support
01:10:38 Using Async Local Storage
01:13:30 Strategies for Open Source Maintainers
01:14:27 Balancing Work-Life and Open Source
01:18:50 Saying No to Contributions
01:26:03 Balancing Speed and Quality in Testing
01:29:00 Adding Automated Testing to Projects
01: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/@francescociulla
Join 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.
Chapters
01:06 Becoming a Docker Captain
14:08 Working at the European Space Agency
28:36 Exploring Rust and Content Creation
30:03 Learning in Private vs. Learning in Public
34:02 Teaching and Documenting the Learning Process
41:17 Accepting and Embracing Introversion
46:17 Putting Pressure on Yourself to Grow
53:51 Growth Mindset
01:03:22 It's Never Too Late
01:06:06 Understanding DevRel
01:11:30 Daily.dev and the Free Model
01:18:36 Measuring DevRel Success
01:26:00 Algorithm Tricks for Social Media
01: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.
Chapters
05:00 Introduction and Background
12:49 Implementing JavaScript in Browsers
20:01 The Challenges of Language Evolution
34:57 Balancing Stakeholder Perspectives in TC39
37:45 The Importance of Moving Slowly in Language Development
38:21 The Blessing and Curse of the Web
45:11 The Journey of Temporal and Intl
53:25 Participating in the TC39 Process
01:06:38 The Philosophical Question of Accessibility
01:09:59 The Need for a Broader Perspective
01:11:00 The Bias in Technology
01:15:10 The Divide Between English and Non-English Speakers
01:19:35 The Challenge of Implementing Different Calendars
01:24:28 The Role of AI in the Web
01:30:08 Contributing to the TC39 Committee
01: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-copilot
Takeaways
- 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.
Summary
Yoav 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.
Chapters
03:26 Introduction and Background
06:33 Yoav's Journey to Builder
11:26 Builder.io and the Ecosystem
32:45 Mitosis
33:58 Qwik: Core Principles and Unique Selling Points
36:16 Qwik Implementation and Debugging
39:39 Qwik 2.0 and Community-Driven Development
49:14 Builder.io and the Use of Qwik
58:20 The Importance of Understanding Servers in Web Development
1:01:29 The Journey of Learning Web Development
1:02:27 The Big Announcement
1:02:36 Qwik Becoming Open Source
1:03:35 Qwik and Core Web Vitals
1:04:59 Qwik UI and Ecosystem Projects
1:05:56 Moving to Qwik Dev and New Governance Model
1:06:55 Benefits of Open Source and Community Ownership
1:10:27 Improvements in Qwik 2.x
1:15:12 Qwik and Core Web Vitals
1:17:30 Out of Order Streaming in Qwik 2.x
1:24:44 Qwik Server Components
1:28:03 Apple and PWAs

Hosted on Acast. See acast.com/privacy for more information.