Your SlideShare is downloading. ×
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Look beyond PHP
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Look beyond PHP

13,212

Published on

Published in: Technology
1 Comment
30 Likes
Statistics
Notes
  • How I monetize my searching skills. Complete guidance at makecash25.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
13,212
On Slideshare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
0
Comments
1
Likes
30
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Look beyond PHP02/29/2012 | fabien.potencier.org | @fabpot
  • 2. Why?
  • 3. A Web Developer http://www.flickr.com/photos/dunechaser/160405823
  • 4. A Web Developer http://www.flickr.com/photos/dunechaser/142079357
  • 5. Master PHP first
  • 6. levenshtein()
  • 7. http://twig-project.org/extend
  • 8. spl_object_hash()
  • 9. $o1 = new stdClass();$o2 = new stdClass();spl_object_hash($o1) !== spl_object_hash($o2);spl_object_hash($o1) === spl_object_hash($o1);
  • 10. Traits in PHP 5.4?
  • 11. Learn the basics
  • 12. JavaScript
  • 13. HTTP / RFC 2616http://tools.ietf.org/wg/httpbis/
  • 14. Use the right tools...
  • 15. IDE / Editor
  • 16. Use the right tool for the jobUse software written in other languages... dont reinvent the wheel
  • 17. ConFoo - Migrating MVC to the front-end using Backbone JS by Martin Drapeau
  • 18. JuggernautConFoo - Realtime Web Apps with WebSockets by Igor Wiedler
  • 19. ConFoo - Build more with LESS CSS by Jake Smith
  • 20. ConFoo - High traffic website search with Apache Solr by Satish TallapakaConFoo - ElasticSearch [R]evolution: Welcome by Andrei Zmievski
  • 21. VarnishConFoo - Varnish, the easy way to speed up your websites by me
  • 22. ConFoo - Scaling with MongoDB by Rick Copeland
  • 23. ConFoo - Redis - Your advanced in-memory key-value store by Jordi Boggiano
  • 24. Learn from others code... whatever the language
  • 25. Python
  • 26. from bottle import route, run@route(/hello/:name)def index(name=World): return <b>Hello %s!</b> % namerun(host=localhost, port=8080)
  • 27. Jinja2... Twig
  • 28. Logbook... Monolog
  • 29. Webassets... Assetic
  • 30. http://www.flickr.com/photos/davemorris/3431970729
  • 31. http://www.flickr.com/photos/hawkexpress/328322067
  • 32. Symfony2ZFCakePHPDjangoRails
  • 33. This also applies todocumentation and processes
  • 34. PEP vs PSR/RFC
  • 35. PEP 20 - The Zen of Python Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases arent special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess.There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless youre Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, its a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- lets do more of those!
  • 36. PSR-0“Mandatory requirements that must be adhered to for autoloader interoperability.” https://github.com/php-fig
  • 37. Javadoc vs Phpdoc
  • 38. ReST / Sphinx
  • 39. What can we learn from others?
  • 40. What should you learn now?
  • 41. Be curious Be passionate Be Curious
  • 42. Thank You

×