ConTejas Code Tejas Kumar

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.

Follow me on 𝕏: https://twitter.com/tejaskumar_
Links
- Sentry: https://sentry.io
- Lazar on 𝕏: https://twitter.com/NikolovLazar
In 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.
Chapters
00:00 - Intro
01:07 - Sponsor
01:51 - Greetings
02:53 - Defining Sentry's Suite of Features
04:43 - How does Sentry instrument a wide variety of software?
09:32 - Sentry compared to TypeScript
12:31 - Sentry and Privacy
16:57 - De-obfuscating Code with Source Maps
19:46 - Replay.io vs. Session Replay and Sentry
21:20 - Sentry Spotlight and Dev-Time Monitoring
25:07 - Propagating a Trace inside a Database Transaction
27:38 - Sentry Differentiators
35:58 - Sentry Report of Most Common Pitfalls in Apps, like Spotify Wrapped but with Sentry
39:42 - Children and error/stack proximity with Sentry reporting
42:22 - The Apdex as a Performance Metric
44:56 - Performance and Core Web Vitals
49:20 - Cumulative Layout Shift (CLS)
54:43 - Where does CLS happen in the rendering process and mitigation steps
58: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 Glyphs
01:05:57 - Replacing fonts when loaded to prevent CLS, FOIT, and FOUT
01:08:51 - How Sentry helps with Core Web Vitals
01:11:49 - Sentry Internals: Architecture, Data Stores, Rust
01:17:21 - Scale Problems that Sentry went through
01:19:12 - Does Sentry use Sentry? Sentry on Sentry
01:21:13 - When to Avoid Sentry
01:22:11 - Sentry Salient (Repeating) Best Practices
01: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.ai
Takeaways
- 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
- 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.app
Chapters
00:00 - Intro
02:59 - Welcome
04:20 - Getting Inspired about SolidJS
06:59 - React Fatigue: Doubts and Questions about React
10:09 - Signals as Native JavaScript (TC39 Proposal)
12:38 - SolidStart and Ecosystem
21:01 - SolidJS Docs and How Atila Got Involved
24:45 - React is Hard to Contribute To/SolidJS is Easier; Why?
35:23 - Understanding SolidJS for newcomers
40:33 - Signals in React
46:38 - Do the minimal perf gains even matter?
52:56 - SolidJS Pros and Cons
56:45 - SolidStart Developments
01:04:27 - SolidJS Community and Ryan
01:07:39 - Migrating to SolidJS from another library
01:12:28 - Codemods and Kent C. Dodds
01:14:15 - CrabNebula
01:15:57 - Tauri, Rust, and Desktop Apps with JavaScript
01:21:13 - Rust: Benefits and Tradeoffs
01:32:37 - CrabNebula offerings: DevTools for Tauri
01:41:00 - CrabNebula offerings: Cloud
01:42:17 - CrabNebula offerings: Security Audits
01:44:46 - Getting involved with CrabNebula
01:45:57 - Main Takeaway from Atila
01:47:01 - Conclusion

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