Frontend

In an era where everyone and their mother can generate and deploy the same generic-looking React / Tailwind / shadcn/ui slop to Vercel at the press of a button, your moat as a frontend developer remains the following:

• mastering the underlying web standards
• understanding tradeoffs and hard limits of existing frameworks/libraries/abstractions
• knowing how to cut bloat and replace building blocks with leaner, more flexible, or more maintainable alternatives
• leveraging lesser-explored platform features to create delightful, net-new experiences on the web

In an era where everyone and their mother can generate and deploy the same generic-looking React / Tailwind / shadcn/ui slop to Vercel at the press of a button, your moat as a frontend developer remains the following:

• mastering the underlying web standards
• understanding tradeoffs and hard limits of existing frameworks/libraries/abstractions
• knowing how to cut bloat and replace building blocks with leaner, more flexible, or more maintainable alternatives
• leveraging lesser-explored platform features to create delightful, net-new experiences on the web

https://youtu.be/TBIjgBVFjVI

> leveraging lesser-explored platform features to create delightful, net-new experiences on the web

This. I recently implemented carousel using scroll snap replacing JS library that got suggested by Claude. This required non-trivial understanding of how DOM and event loop works but I got it working in 30 LOCs and it works smoothly on mobile, too (no need for JS exec during each repaint.)

There are other similar features built-in into modern browsers that not many people know about because they don't know how to read MDN or caniuse.com

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo