The Business Of Front-End Development
summary
History shows front-end work shifts from browser-bug wrangling to tooling, but the recommendation stays concrete: know HTML CSS JavaScript, prefer progressive enhancement as default, test that output equals hand-written HTML/CSS, and measure impact on mobile performance. Try new specs now — CSS Grid behind a flag in Chrome — and use helpers that don’t force markup changes — Perch admin works without JavaScript — avoid baking big third-party dependencies into core experiences.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:41Perch
- 5:51Front-end developer circa 2005? Browser bugs expert.
- 7:08Browser vendors are implementing standard things in a standard way.
- 7:42Innovation happens through the standards process.
- 18:39By leaning on frameworks, are we masking the issues?
- 23:49Standardising on tools should not be at the expense of learning HTML, CSS and JavaScript.
- 28:09Considerations when choosing tools and processes.
- 45:21Avoid turning shortcuts and third party code into dependencies.
