There Is No Front End
summary
The core claim is that “front end” is a fuzzy label and roles should be specified by skills and frame of mind not by a token title. Examples equate web UI work with React, React Native and even CLI or API design; practical pain points include configuring webpack and handling browser storage—author recounts implementing a localStorage migration. Hiring should list the actual responsibilities (UI design, data modeling, integration, performance, security) and the concrete tools expected.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 3:00Software is exciting
- 4:00Who is a frontend developer
- 5:00David Humes exercise
- 7:00Ionic
- 8:00Swing
- 10:00Accessibility
- 11:00Commandline vs API
- 12:00Frontend vs API
- 13:00Not being tech agnostic
- 14:00Words mean things
- 15:00Setting up a database
- 16:00Backend and frontend
- 17:00Frontend skills
- 18:00Backend skills
- 19:00Frame of mind
- 20:00Conclusion
related talks
46mFunctional Frontend. Practical survival guide for backend engineers.
40mThe Frontend Is a Full Stack
34mWe need to talk about the front web
58mFront-End Application Architecture
01h 10mThe Future of Frontend Panel
42mWhy Is Frontend So Hard?
29mUX is frontend only! Why do I, super ninja backend developer, need to care about it?
49mSOLID Frontend Architecture. Do we need it? Yes!