Javascript Toolkit
•Download as PPTX, PDF•
1 like•570 views
Javascript Toolkit for a web developer.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (15)
Similar to Javascript Toolkit
Similar to Javascript Toolkit (20)
Recently uploaded
Recently uploaded (20)
Javascript Toolkit
- 1. T a n i a G o n z a l e s THE JAVASCRIPT TOOLKIT
- 2. ABOUT ME Tania Gonzales Villa Consultant/Developer @ ThoughtWorks @taniadgv 2
- 3. 3 An attempt to organise the recent explosion of Javascript based technologies and frameworks into a coherent toolkit to be used by a web application developer.
- 4. 4 What is the reason of the recent explosion of Javascript libraries and frameworks?
- 5. MANIFESTO FOR AGILE SOFTWARE DEVELOPMENT 5 Individuals and interactions over processes and tools Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan.
- 6. AGILE PURPOSE FOR DELIVERY 6 Deliver Fast Deliver Often Deliver Value
- 7. TECHNICAL SUPPORT FOR AGILE 7 Evolutionary Architecture Continuous Integration Programming Languages Design Patterns TDD Lot’s of Automatisation Continuous Delivery Evolutive Design
- 8. 8
- 9. AGILE TOOLKIT 9 jUnit, TestNG, Cucumber Design, Analysis, Architecture Patterns Gradle, Maven, Ant, Ivy Jenkins, GO, Snap, Bamboo http://www.thoughtworks.com/radar Java, Ruby, Scala, Python, Clojure, Javascript
- 12. TOOLKIT CATEGORIES 12 Infrastructure Application & Product Development Testing Utilities & Support
- 13. INFRASTRUCTURE Your toolbox for fast and easy development. 13
- 14. SCAFFOLD 14 Several tools, several ways, several practices. Need to organise and give some good foundation - best practices, good design.
- 16. AUTOMATION 16 Lot’s of tasks to execute: compile, test, assembly, minify and deliver your code.
- 17. 17
- 18. AUTOMATION UTILITIES 18 While running your automated task you probably want some tools to help you go even further.
- 20. DEPENDENCY MANAGEMENT 20 Applications are getting complex, they rely on several other libraries and frameworks.
- 21. 21
- 22. APPLICATION & PRODUCT Application are getting complex, need for frameworks that support app development. 22
- 23. APPLICATION FRAMEWORKS 23 Main javascript frameworks to build user interfaces.
- 24. 24
- 25. APPLICATION UTILITIES 25 Libraries that will help when building the application.
- 26. 26
- 27. DYNAMIC LOADING 27 Big projects are split among several pieces of javascript for the sake of the modularisation. No all of them should be loaded at the same time.
- 29. DEVELOPMENT 29
- 30. OTHER LANGUAGES 30 Have a syntactic sugar element, or even completely different syntax (that in the end turns into javascript to run in the browser).
- 32. TESTING Testing is all around. Need to test in different browsers, need to write the tests, need to run the tests, need to report the results. 32
- 33. TEST RUNNERS 33 Applications are getting complex, they rely on several other libraries and frameworks.
- 34. 34
- 35. FRAMEWORKS 35 Tools to allow you write your tests.
- 36. 36
- 37. END TO END 37 Test the whole flow of your application.
- 38. 38
- 39. TEST SUPPORT 39 Support libraries for writing and running tests.
- 40. 40
- 41. UTILITIES & SUPPORT The support you need while writing Javascript 41
- 42. DOM UTILITIES 42 DOM selection and manipulation, some auxiliary functions, need for utilities that make work simple.
- 43. 43
- 44. LANGUAGES UTILITIES 44 Clean utilities, functional programming style, reactive programming features, helpers and utilities.
- 46. CI 46 Continuos integration, continuous delivery, continuous deployment.
- 47. 47
- 48. WRAP UP 48 Different needs/tools and their relation Agile demands for you as a developer Keep your mind open
- 49. For questions or suggestions: Tania Gonzales @taniadgv tgonzales@thoughtworks.com THANK YOU
Editor's Notes
- Run a sustainable business Champion software excellence and revolutionize the IT industry Advocate passionately for social and economic justice.
- Agile adoption
- Where did it start? why do we need many tools for build, integration? Agile adoption as best process for software development
- Users, priorities, scope, time Resolve to problem Agile is more linked to process - > iterations, story planning, stand ups, retro
- Adopt ->Feel strongly that the industry should adopt Trial -> Worth pursuing , try in project can handle the risk. Assess -> Worth exploring, how it will affect the enterprise Hold -> Procede with caution
- Why it didn’t have the explosion many years ago when agile did?
- Node gave javascript the ability to be used in process like build, validate, compile, execute No more the browser language First class citizen
- Users, priorities, scope, time Resolve to problem Agile is more linked to process - > iterations, story planning, stand ups, retro
- generators
- Minify, treat images, compile css, concatenation
- Grunt -> Plugins are based on configuration via a Javascript object, no code logic Gulp -> relies on code logic based on pipelines brocoli -> tree based approach, every step makes use of cache Community and plugins
- Uglify -> JavaScript parser / mangler / compressor / beautifier library for NodeJS JShint is a fork of JSLint, jshint -> community-driven
- npm -> management for node libraries, things that are going to stay on the server … npm for developer tools, bower -> for front-end Bower is optimized for the front-end. Bower uses a flat dependency tree, requiring only one version for each package, reducing page load to a minimum. component -> does everything from package management to building, Component uses GitHub as a registry
- Sauce Labs: Automated testing in the cloud for CI.