- Sandbox, Virtualisation, Vagrant, and other tools
- Efficient code reviews (including useful tools)
- Grunt & Rake. The Make-tool ecosystem
- Responsive images
- Remote debugging and emulation in Chrome DevTools
-
-
Save Crystalh/7677159 to your computer and use it in GitHub Desktop.
Ah yes! Event debouncing, definitely one I'd like to see covered.
In a similar vein a guy at the FT wrote a small lib 'FastDom' for batching up DOM read/writes, to prevent layout thrashing:
http://wilsonpage.co.uk/preventing-layout-thrashing/
- Better understanding of purpose and focus of unit testing and acceptance testing (I vote Kenny)
- Componentisation via NPM (Maslen mentioned a way to do this via Package.json) or if not that then Bower or Component
- Refactoring code (when and how - e.g. smells to look for)
- View/Templating languages (John/Kenny/Maslen had some opinions on this I believe: Mustache, twig etc)
Test metrics (how long our tests take to run, how to identify problems and how to improve our suite). Not volunteering; it's more of a request :)
I can talk at you all about tests no problem :)
I'm happy to talk about "Sandbox, Virtualisation, Vagrant, and other tools"
I would be keen to discover what everyone thinks about the metrics on the test suite(s), and I think that we should as a matter of course be considering ways to improve them in terms of utility in every way, so this ought to be agenda imho...
- Web Components
- Modern JavaScript Guidelines
- JS Supersets (like TypeScript etc.) for agnostic module writing (write with the Future, compile into legacy JS)
Show and tell:
Specials have dones this recently...
http://m.bbc.co.uk/news/entertainment-arts-24957282