1. Look beyond PHP
02/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

6. Master PHP first

7. levenshtein()

9. http://twig-project.org/extend

11. spl_object_hash()

12. $o1 = new stdClass();
$o2 = new stdClass();
spl_object_hash($o1) !== spl_object_hash($o2);
spl_object_hash($o1) === spl_object_hash($o1);

13. Traits in PHP 5.4?

14. Learn the basics

15. JavaScript

16. HTTP / RFC 2616
http://tools.ietf.org/wg/httpbis/

18. Use the right tools...

19. IDE / Editor

22. Use the right tool for the job
Use software written in other languages...
don't reinvent the wheel

23. ConFoo - Migrating MVC to the front-end using Backbone JS by Martin Drapeau

24. Juggernaut
ConFoo - Realtime Web Apps with WebSockets by Igor Wiedler

25. ConFoo - Build more with LESS CSS by Jake Smith

26. ConFoo - High traffic website search with Apache Solr by Satish Tallapaka
ConFoo - ElasticSearch [R]evolution: Welcome by Andrei Zmievski

27. Varnish
ConFoo - Varnish, the easy way to speed up your websites by me

28. ConFoo - Scaling with MongoDB by Rick Copeland

29. ConFoo - Redis - Your advanced in-memory key-value store by Jordi Boggiano

31. Learn from other's code...
whatever the language

32. Python

33. from bottle import route, run
@route('/hello/:name')
def index(name='World'):
return '<b>Hello %s!</b>' % name
run(host='localhost', port=8080)

34. Jinja2... Twig

35. Logbook... Monolog

36. Webassets... Assetic

37. http://www.flickr.com/photos/davemorris/3431970729

38. http://www.flickr.com/photos/hawkexpress/328322067

41. Symfony2
ZF
CakePHP
Django
Rails

43. This also applies to
documentation and processes

44. PEP vs PSR/RFC

45. 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 aren't 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 you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

46. PSR-0
“Mandatory requirements that must be adhered to for autoloader
interoperability.”
https://github.com/php-fig

47. Javadoc vs Phpdoc

48. ReST / Sphinx

49. What can we learn from others?

50. What should you learn now?

51. Be curious
Be passionate
Be Curious

52. Thank You