Recipes for successful CakePHP projects

3,432 views

Published on

Slides from the talk given by Felix Geisendörfer during the CakeFest #3 - July 2009

Note: the original pdf can be found on cakephp.org

Published in: Technology, Self Improvement
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,432
On SlideShare
0
From Embeds
0
Number of Embeds
53
Actions
Shares
0
Downloads
82
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Recipes for successful CakePHP projects

  1. 1. Recipes for successful CakePHP Projects Tools & best practices for tasty cake apps
  2. 2. Felix Geisendörfer CakePHP since 2005 Worked on core since early 2007 ThinkingPHP.org -> Debuggable.com
  3. 3. Good Communication (= less code, more results)
  4. 4. E-Mail
  5. 5. E-Mail The Good Parts No need for instant responses Decentralized Works offline
  6. 6. E-Mail The Bad Parts CC, BCC, Threads - who knows what? Full inboxes, people waiting Return on Investment
  7. 7. When to use e-mail Time zone differences Announcements, Spawning debates Emergency notification
  8. 8. E-Mail Tools Mailing lists Shared e-mail accounts Automated e-mails for commits, etc.
  9. 9. Instant Messenger
  10. 10. IM The Good Parts Instant communication Group chat Voice, Video, Screen
  11. 11. IM The Bad Parts Distraction !! Multi-tasking = yeah, right History, Incompatibility
  12. 12. IM Tools iChat, Adium, etc. Campfire Skype
  13. 13. Task Management (getting less done in more time)
  14. 14. The truth first
  15. 15. Problems with Task Management Getting tasks in Tracking tasks Getting tasks done
  16. 16. Tools I like Pen & paper + text files OmniFocus (Mac only) Lighthouse / TheChaw (Trac for Git)
  17. 17. Focus Nobody else will do it for you
  18. 18. What works 25 minute sessions (pomodorotechnique.com) E-mails t wice a day, IM off in morning Clear goals, every day
  19. 19. Unit Testing
  20. 20. Failing at unit testing 100% code coverage Test driven development Expecting everybody to write & run tests
  21. 21. Where the money is Top-down testing Performance testing Re-assembling
  22. 22. Continuous Integration
  23. 23. Rolling your own CI box Post-receive Hook from Git Run unit tests, check exit code Log results, notify IM / Email / etc. Expect 1 day of work, but it’s worth it
  24. 24. Pair programming Scaling your coding powers
  25. 25. Pair Programming 101 1 Computer, 2 people One person types & explains One person listens & suggests
  26. 26. Virtualization So you can destroy the environment
  27. 27. virtual box vmware
  28. 28. Version Control (Because there is plenty of blame to go around)
  29. 29. In the beginning, there was pain
  30. 30. CVS & SVN gave some hope
  31. 31. But branching sucked
  32. 32. So Linus gave us Git
  33. 33. CakePHP & Git CakePHP is switching from SVN to Git Git is fantastic for cake apps as well Decentralized, offline, fast
  34. 34. Command Line (= power)
  35. 35. The Chaw (= CakePHP based Git GUI)
  36. 36. GitHub (= Commercial & Free Git hosting)

×