Avoiding Complexity for Clarity

1min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

Ignoring necessary warnings in coding tools like ESLint can lead to confusion and a lack of clarity in error management. Maintaining visibility on errors, specifically referencing the challenge of an excessively high error count, is crucial for effective debugging. A clear overview of issues aids in purposeful fixes, reinforcing the importance of a clean and focused development environment.

In this Potluck episode of Syntax, Scott and Wes answer your questions, from weighing the trade-offs between numerous small npm packages and a few larger ones to managing the challenges of work-from-home life. They also explore CSS modules, strategies for shrinking JavaScript bundles, and even where to find the best replacement ear cups for your headphones.

Show Notes

00:00 Welcome to Syntax!
00:38 Commentating basketball.
01:16 Brought to you by Sentry.io.
02:09 The video podcast doesn’t translate well to audio.
04:08 Many small npm packages vs a few large.
09:55 Developers dealing with WFH, ADHD, and kids.
15:59 CSS modules for scoping styles to components.
20:55 Scoped CSS in React?
23:21 Reducing JS bundle sizes.
- Bundle Phobia.
- Javascript Bundle Analysis [Beta].
29:44 Balancing learning, doing, and teaching.
33:04 Making maps local first.
36:20 How to pronounce ‘schema’.
- Wes Bos Tweet.
37:09 HTML tag.
40:11 Where to get replacement ear cups for headphones?
- wickedcussions.
- Scott’s Audeze Headphones.
42:21 ESLint and hiding errors.
48:48 Sick Picks & Shameless Plugs.