Recipes for successful CakePHP projects
3 likes1,467 views
The document discusses best practices and tools for successful CakePHP projects, with a focus on effective communication through email and instant messaging. It highlights the importance of task management, unit testing, and continuous integration, as well as the advantages of using Git over older version control systems. Additionally, it emphasizes techniques like pair programming and the Pomodoro technique to enhance productivity in coding environments.
Recipes for successful CakePHP projects
- 1. Recipes for successful CakePHP Projects Tools & best practices for tasty cake apps
- 2. Felix Geisend旦rfer CakePHP since 2005 Worked on core since early 2007 ThinkingPHP.org -> Debuggable.com
- 3. Good Communication (= less code, more results)
- 4. E-Mail
- 5. E-Mail The Good Parts No need for instant responses Decentralized Works of鍖ine
- 6. E-Mail The Bad Parts CC, BCC, Threads - who knows what? Full inboxes, people waiting Return on Investment
- 7. When to use e-mail Time zone differences Announcements, Spawning debates Emergency noti鍖cation
- 8. E-Mail Tools Mailing lists Shared e-mail accounts Automated e-mails for commits, etc.
- 10. IM The Good Parts Instant communication Group chat Voice, Video, Screen
- 11. IM The Bad Parts Distraction !! Multi-tasking = yeah, right History, Incompatibility
- 12. IM Tools iChat, Adium, etc. Camp鍖re Skype
- 13. Task Management (getting less done in more time)
- 14. The truth 鍖rst
- 15. Problems with Task Management Getting tasks in Tracking tasks Getting tasks done
- 16. Tools I like Pen & paper + text 鍖les OmniFocus (Mac only) Lighthouse / TheChaw (Trac for Git)
- 17. Focus Nobody else will do it for you
- 18. What works 25 minute sessions (pomodorotechnique.com) E-mails t wice a day, IM off in morning Clear goals, every day
- 19. Unit Testing
- 20. Failing at unit testing 100% code coverage Test driven development Expecting everybody to write & run tests
- 21. Where the money is Top-down testing Performance testing Re-assembling
- 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 its worth it
- 24. Pair programming Scaling your coding powers
- 25. Pair Programming 101 1 Computer, 2 people One person types & explains One person listens & suggests
- 26. Virtualization So you can destroy the environment
- 27. virtual box vmware
- 28. Version Control (Because there is plenty of blame to go around)
- 29. In the beginning, there was pain
- 30. CVS & SVN gave some hope
- 32. So Linus gave us Git
- 33. CakePHP & Git CakePHP is switching from SVN to Git Git is fantastic for cake apps as well Decentralized, of鍖ine, fast
- 34. Command Line (= power)
- 35. The Chaw (= CakePHP based Git GUI)
- 36. GitHub (= Commercial & Free Git hosting)