Tasty
Wes and Scott answer listener questions on React components, freelancing, ethics, moist code, debugging fonts, and more during a fun potluck episode.
Tasty
Emailer asks Wes and Scott to explain the basics of building a website from scratch using HTML, CSS and JavaScript for beginners with no experience.
Tasty
Wes and Scott answer developer questions about WordPress vs advanced tech for clients, backend hosting, Drupal, CSS strategies, preparing for job interviews, home cooling fan setups, and podcast recommendations.
Tasty
Wes and Scott from Syntax podcast join Chris and Dave from ShopTalk podcast for a crossover episode. They discuss their podcast goals, current web development stacks they use and like such as Next.js and SvelteKit, how WordPress compares, and more.
Tasty
In today's potluck episode, Scott and Wes answer listener questions on topics like Svelte vs React, severing project ties, permissions-based APIs, Rescript, and more.
Tasty
React 18 is introducing automatic batching, suspense, strict mode, useTransition hook, SSR streaming, and more. There are great explainers on the React docs.
Tasty
Scott and Wes review listener submitted websites and portfolios, providing feedback on design, code, accessibility, and more. They also discuss Scott's upcoming move, funny kid stories, and share picks for lever wire connectors, podcasts, and web dev courses.
Tasty
Scott and Wes dive deep into the elements tab in dev tools, explaining all the tips, tricks and lesser-known features for inspecting HTML and CSS. They cover manipulating the DOM, debugging styles and layouts, previewing animations, compatibility checking, and customizing the dev tools.
Tasty
Scott and Wes answer listener questions covering web components, minimum coding setup, Python frameworks, Docker, code prediction, storing audio files, and more.
Tasty
Discussion on how container queries will allow styling based on available space by measuring elements instead of viewport. Other topics include cascade layers to control specificity order, scope for addressing naming conflicts, and Miriam's work with the CSS Working Group.
