✳flâneur — a map of the web's best reading
The Elements of UI Engineering — Overreacted
overreacted.io · 2,006 words · saved by 3 readers
What makes UI engineering difficult?
The Elements of UI Engineering December 30, 2018 Pay what you like In my previous post , I talked about admitting our knowledge gaps. You might conclude that I suggest settling for mediocrity. I don’t! This is a broad field. I strongly believe that you can “begin anywhere” and don’t need to learn technologies in any particular order. But I also place great value in gaining expertise. Personally I’ve mostly been interested in creating user interfaces. I’ve been mulling over what it is that I do know about and consider valuable. Sure, I’m familiar with a few technologies (e.g. JavaScript and Rea
Explore this link on the map →saved by
related reading
- Building data-centric apps with a reactive relational databaseriffle.systems
- Say precisely what you mean.index.how
- Web Interface Guidelinesvercel.com
- ui.landui.land
- UI = f(statesⁿ) - daverupert.comdaverupert.com
- How to fix a bad user interfacescotthurff.com
- Cheng Lou on X: "My dear front-end developers (and anyone who’s interested in the future of interfaces): I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at https://t.co/BKnwCDIp75" / Xx.com
- Web Interface Guidelinesrauno.me
- Refactoring UIrefactoringui.com
- Mediumuxdesign.cc
- How we redesigned the Linear UI (part Ⅱ) - Linearlinear.app
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com