Download as PDF, PPTX
Uploaded byMatthias Noback
How Symfony changed my life (#SfPot, Paris, 19th November 2015)
The document reflects on the author's journey with Symfony over the past decade, detailing the evolution from earlier programming methods to adopting Symfony's framework. It highlights the significant changes brought by Symfony 2, such as the introduction of dependency injection, templating with Twig, and improved code maintainability. The author shares personal insights on development practices and the impact of Symfony on their career growth.
More Related Content
Similar to How Symfony changed my life (#SfPot, Paris, 19th November 2015)
How Symfony changed my life (#SfPot, Paris, 19th November 2015)
- 1. Matthias Noback Paris, November19th 2015 10 years! How Symfony changed my life
- 3.
- 4. From ASP usingVBScript and a MS Access database To PHP with a MySQL database "You should try PHP!"
- 5.
- 6. From PHP 4and one mega Page class To PHP 5 with proper scoping for methods and properties, and autoloading
- 7. From PHP &HTML in the same file To PHP classes and Smarty template files
- 8. From copying snippets fromthe Internet To downloading single-purpose libraries
- 9. Feeling mighty fine SQLinjection Register globals Session hijacking Magic quotes CSRF XSS
- 10.
- 11. But... performance was verygood ;)
- 12.
- 13. symfony (1) with alower-case s
- 14.
- 15. The Book (back then) FrançoisZaninotto (Propel) symfony 1.1
- 16. Working with symfony 1meant... MVC Fat controllers Fat models (Zend devs wrote fat services as well)
- 17. Not in thecontroller or the model? Put it in: A "peer" class A utility class Or: create a global singleton for it
- 18. What's a singleton? Static Global Single instance classSingleton { private static $instance; private function __construct() { } public static function getInstance() { if (self::$instance === null) { self::$instance = new self(); } return self::$instance; } }
- 19. God object sfContext::getInstance() getUser(), getResponse(), getRequest(),getLogger(), getI18N(), ...
- 20.
- 21.
- 22.
- 23.
- 24. Tweaking symfony Event listeners:add missing methods on the fly (!) Filters: chain of responsibility factories.yml and other config files
- 25. Switch to Doctrine Itwas... new version 1.0
- 26.
- 27.
- 28.
- 29. SymfonyLive Paris 2011 Almost releasing Symfony2.0 Excitement all over the place
- 30. Start using 2.0? Nobackwards compatibility No best practices No CMS
- 31. Not even... ... an admin generator onlyfor scaffolding ;)
- 32. Migrating to 2.0? Companyowners didn't dare to take the step (I agree with them now!) I left the company :)
- 33. Symfony2 capital "S" no space,for Google
- 34. Infrastructure 1. Git forversion control 2. Install script or Git submodules for vendor code 3. At some point: composer started handling dependencies
- 35. Templating Twig: Own syntax No PHPcode "Auto-safe" Fast (the engine that is) "Templating engines in PHP" by Fabien Potencier
- 36. Dependency injection container Major improvement:everything can be configured No runtime resolvers anymore
- 37. What's dependency injection? class Foo { private$bar; public function __construct(Bar $bar) { $this->bar = $bar; } }
- 38. What's a DI container? classContainer { public function createFoo() { return new Foo($this->getBar()); } private function createBar() { return new Bar(); } }
- 39. What does DIgive us? Single responsibility Testability Dependency inversion Speed Flexibility
- 40. Active record -> datamapper Doctrine 1/Propel Doctrine 2/...
- 41. Active record sample class Invoiceextends Record { } $invoice = new Invoice(); $invoice->save();
- 42. Data mapper sample class Invoice { } $invoice= new Invoice(); $entityManager->persist($invoice); POPO
- 43. Why is thatbetter? Isolation Model first Decoupling (not always a good reason)
- 44.
- 45.
- 46. A bundle foreach feature
- 47. Framework coupling Libraries are framework- independent Bundlesare explicitly meant to couple code to the framework
- 48. Bundles: service definitions Service definitionfiles Bundle extension Bundle configuration Compiler pass
- 49.
- 50.
- 51.
- 52. Security So very hard Documentedin many different ways It's really good though Simplified at code level now
- 53. Symfony is an earlyadopter PHP-FIG PSR-0, PSR-1, PSR-2, PSR-3, PSR-7 - very quickly adopted
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 62.
- 64.
- 65. Symfony - The biggestchange Dependency injection (container) Which is an enabler for better code Because: maintainable and testable
- 66. My personal development: 1. Ilove symfony 2. I love Symfony2 3. I want to decouple from it 4. I want to fully embrace it whenever that's okay
- 67. For me it'sabout Knowing your framework Being fast with it Not being totally dependent on it
- 68.