Skip to content

Instantly share code, notes, and snippets.

@Crystalh
Last active December 29, 2015 13:29
Show Gist options
  • Select an option

  • Save Crystalh/7677159 to your computer and use it in GitHub Desktop.

Select an option

Save Crystalh/7677159 to your computer and use it in GitHub Desktop.
Ideas & Topics for Web Dev monthly meeting

Topics

  • 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
@tmaslen

tmaslen commented Nov 29, 2013

Copy link
Copy Markdown

Show and tell:

Specials have dones this recently...

http://m.bbc.co.uk/news/entertainment-arts-24957282

@Crystalh

Copy link
Copy Markdown
Author

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/

@Integralist

Copy link
Copy Markdown
  • 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)

@coderkind

Copy link
Copy Markdown

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 :)

@kenoir

kenoir commented Nov 29, 2013

Copy link
Copy Markdown

I can talk at you all about tests no problem :)

@sthulb

sthulb commented Dec 2, 2013

Copy link
Copy Markdown

I'm happy to talk about "Sandbox, Virtualisation, Vagrant, and other tools"

@maleghast

Copy link
Copy Markdown

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...

@thom4parisot

Copy link
Copy Markdown
  • Web Components
  • Modern JavaScript Guidelines
  • JS Supersets (like TypeScript etc.) for agnostic module writing (write with the Future, compile into legacy JS)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment