Developing the unknown
•
0 likes•249 views
This document discusses frameworks for web development and why they are useful. It recommends adopting a framework approach to development, even for small projects currently, as requirements tend to grow over time. Frameworks provide reusable code bases that allow developers to focus on their specific application needs rather than rebuilding common functions. The document also provides examples of popular frameworks for tasks like web applications, CSS, JavaScript, and project management processes. It emphasizes choosing a framework with active community support and good documentation.
Report
Share
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Developing the unknown
Similar to Developing the unknown (20)
Recently uploaded
Recently uploaded (20)
Developing the unknown
- 1. Developing The UnknownA simple story of refactoring our way to happy clients!Why we use frameworks for everything!MVC, Scrum, CakePHP, Jquery, 960 & anything else we can get our hands on. Doesn't matter what the framework is, pick one & have fun!Paul Rhodes @paulrhodesuk paul@22blue.co.uk
- 2. IntroWeb Developer for over 13 yearsFounder of 22 Blue, Previously MindBlipThanks & ApologiesPurely based on personal experienceCustom In-House Frameworks since 2002Using Open Source Frameworks for last 3 years
- 3. THE REALITIES OF DEVELOPMENTDeveloping the UnknownIt’s All About ‘Change’ ManagementClient or Internal Product DevelopmentProduct Owner will always want new featuresHow well these can be integrated is critical“Coffee Machine is now pumping out Ice-Cream”Refactor don’t Rebuild
- 4. What is a framework?Lots of different definitions“A reusable partially complete program that embodies a design for applications in a particular domain. Programmers complete the program by providing application-specific components.”open source, object-oriented web application frameworks
- 5. WHY USE a framework?Building Blocks - Solid base upon which to buildNot Just Database – so much more… Set of GuidelinesConcentrate on features (Business Logic)Complements Design ProcessNot going to talk about anything I haven’t used
- 6. WHAT Frameworks ARE AVAILABLE?100’s – vary in some degreeWeb Applications: Zend, CakePHP, .NET MVC, Yii, Code Igniter, WordpressCSS Systems: 960.gs, Blueprint, YAMLJavascript: jQuery, MooTools, Prototype, YUIProcesses: Agile, XP, Scrum
- 7. REFACTORING MADE EASYMost Developers ‘inherit’ an internal frameworkMVC is the KeyReal World Example: APIRed, Green, RefactorTesting SuiteUpdates can be purely view based
- 8. CUSTOM VS OPEN SOURCEDocumentationKey Man DependencyBusiness ConstraintsOpen Source: bug fixes, 1000s hours developmentCustom systems sometimes reach breaking point and require more investment to fix
- 9. WHAT TO LOOK FOR IN A FRAMEWORK?Good DocumentationMVC & Design PatternsConvention over ConfigurationActive Community: IRC, Google Groups, Forums, Blog, ScreencastsExtending the Core: Plugins / ModulesCallbacks & HooksRegular Releases, Development & Maintenance
- 10. SUMMARYWhat do I use?CakePHP, SCRUM, JQuery, 960.gsMagento, Zend Framework, RailsNo matter how big the requirements are todayAdopt a pro framework approachContribute