-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Productivity Up #17
Comments
👍 |
Lets go for this talk for RejectJS instead, if you're interested, as requested here: #42 (comment) |
@techwraith I'd love to do it (sent you an email). Fingers crossed :) |
@techwraith as expressed in the latest emails I'm gonna make it! :) Looking forward to meet the San Francisco crowd. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Productivity Up
Abstract
The major ingredient that makes working with JavaScript so much fun is the high level of productivity it enables due to its dynamic nature. Unfortunately many of us have gotten used to one way of doing things without questioning if we could be more productive if we optimized it.
This presentation is designed to get the attendees excited about re-evaluating their workflow and tools in order to push their productivity level to the absolute maximum.
The live demonstration which constitutes the bigger part of the presentation will show how to meet the following requirements in order to be productive:
The focus of the demonstration is not on certain tools, but on showing how to use and tweak them to become part of a highly productive workflow. I do however hope to make the attendees aware of benefits that can be gained by giving browserify, the node repl or replpad and editor plugins like syntastic or equivalents a go.
Speaker Bio
I have been working with nodejs and JavaScript for over 2 years mostly in my spare time and lately full time at Condé Nast.
The fast turnaround from idea to working module has proven addictive for me and led to lots of modules which ended up on github and/or npm. I also contribute to other awesome open source efforts like browserify to which I added source map support.
The text was updated successfully, but these errors were encountered: