Avoiding Over-Engineering in Web Development

14min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

The chapter explores the dangers of over-engineering in web development, using examples from projects involving technologies like SvelteKit and Storyblock. Speakers emphasize the importance of finding a balance to maintain code quality and prevent complications in the future. Tips are shared on optimizing performance, managing mono repos, and creating efficient web view apps to avoid unnecessary complexities.

Scott and Wes tackle a variety of audience questions, from the nuances of over-engineering to the energy consumption of AI LLMs. They also discuss the pros and cons of monorepos, frameworks, and the ever-important question: Do you really need to learn all the developer tooling?

Show Notes

00:00 Welcome to Syntax!
00:41 Brought to you by Sentry.io.
01:07 Challenges around a resume playback function.
05:56 Why use Google Forms for Potluck questions?
07:57 What constitutes over-engineering and how to avoid it.
13:28 Webview vs native component based mobile apps.
18:06 Running and managing monorepos.
20:59 Energy consumption of AI LLMs vs static web content.
- A guide to LLM inference and performance.
- From Words to Watts: Benchmarking the Energy Costs of LLM Inference.
25:19 Why do we need frameworks?
- Frank M Taylor Blog Post.
33:05 Handling ad-blockers blocking Sentry and other tools.
- Syntax GitHub.
38:25 Creating sites without JavaScript.
42:49 Do I really have to learn all the various developer tooling?
- Wes Bos Tweet.
44:47 What are the best ways to network and meet other developers?
50:16 Sick Picks & Shameless Plugs.