UX is frontend only! Why do I, super ninja backend developer, need to care about it?
summary
Backend work directly shapes APIs, database schemas and query performance for the product that stores and serves the world's largest malware database built over 16 years; heavy static-analysis output forces tradeoffs between sending enough data and keeping pages fast. Concrete prescriptions include validate on front end back end and database, use clear endpoint names and use HTTP verbs (GET PUT PATCH POST DELETE) properly, add constraints to prevent bad input, test outputs as contracts, and involve QA and designers from day one.
AI-written summary · about
chapters (8)
- 0:00Introduction and speakers
- 1:30UX beyond the frontend
- 4:41User needs shape APIs
- 7:10Developer experience matters
- 11:31Constraints prevent errors
- 14:30Feedback and communication
- 17:00Design process for developers
- 20:14Q&A session starts
related talks
47mBack to front - Backend technologies for the frontend developer
49mSOLID Frontend Architecture. Do we need it? Yes!
21mThere Is No Front End
32mLet's put U in UX!
49mUX Engineer, engineers connecting design and front end
48mSecure Development on the Frontend
19mCritical Security Mistakes in Frontend Applications
46mFunctional Frontend. Practical survival guide for backend engineers.