JS In The Enterprise - Lessons Learnt
summary
Recommends concrete practices: modularize UI as configurable widgets that communicate by events, package shared code as npm/node modules and host them internally with artifactory, use AOP libs like meld or aspect‑js for nonfunctional concerns, and enforce quality with eslint, Plato or Sonar plus JSdoc and live docs. Emphasizes high unit and functional test coverage, dependency injection (ES6 modules/requirejs/systemjs), a JS tech radar (adopt/trial/assess/hold), and plan for blocked npm access, old IE polyfills, and frontend data certification.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:37Prepare for modularization
- 4:21Non Functional Requirements
- 5:21Non Invasive NFR'S
- 6:27Metrics and documentation
- 7:47Start at the beginning
- 13:16Browser ecosystem
- 14:32Locked Down Environment
- 15:04Prepare for open source
- 15:26Compliance And Security
- 15:57Setup certification and approval process
related talks
52m10 Awesome Tips for Enterprise JavaScript
01h 01mDesign Principles for Better FrontEnd Code
31mThe Winding Road Towards JS Interoperability
25mLessons for frontend development at scale
01h 13mArchitecting complex JavaScript setups for large scale enterprise projects
20mJavaScript 2 Enterprise Edition
27mDesigning Even Larger (JavaScript) Applications
20mKeynote: JavaScript: Enterprise Adoption and Usage