Passing The Joel Test In The PHP World

  • 5,929 views
Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
5,929
On Slideshare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
72
Comments
0
Likes
12

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
  • svn: existing backups, hooks, stable server
  • http://www.flickr.com/photos/barnaby_s/2689622236/
  • caches like APC actually do compile + store
  • bug trackers integrate with source control
  • Users like this are like a mongoose backed into a corner: with its back to the wall and seeing certain death staring it in the face, it attacks frantically, because doing something has to be better than doing nothing. This is not well adapted to the type of problems computers produce. Instead of being a mongoose, be an antelope. When an antelope is confronted with something unexpected or frightening, it freezes. It stays absolutely still and tries not to attract any attention, while it stops and thinks and works out the best thing to do. (If antelopes had a technical support line, it would be telephoning it at this point.) Then, once it has decided what the safest thing to do is, it does it.
  • drop hourly rates absorb overrun BUT DO NOT CUT ESTIMATES
  • http://www.flickr.com/photos/uk_parliament/2524365036/
  • Phone: and those nearby Meetings: and what time of day Email: expected instant response? Its about control Telecommute helps
  • http://www.flickr.com/photos/stefanyasin/2434657543/
  • http://www.flickr.com/photos/spadgy/313251515/
  • http://www.flickr.com/photos/artnow/1351601518/sizes/l/
  • http://www.flickr.com/photos/bfionline/3117948329/
  • For each task write test test fails write code test passes End up with a suite of tests covering application ties in to continuous integration and automated testing
  • PEAR/PECL Frameworks Javascript libraries/frameworks Beware license restrictions
  • Resources Courses Events Encourage advancement

Transcript

  • 1. Passing the Joel Test in the PHP World
  • 2. Who am I?
    • Lorna Mitchell
    • 3. PHP Developer at Ibuildings
    • 4. Personal site http://lornajane.net
    • 5. European Rep for phpwomen.org
    • 6. PHPNW organiser
    • 7. Twitter: @lornajane
  • 8. Who is Joel?
    • Joel Spolsky
    • 9. Founder of Fog Creek Software
    • 10. Blogs at http://joelonsoftware.com
    • 11. Author of numerous books, particularly Best Software Writing
    • 12. Co-founder of http://stackoverflow.com
  • 13. What is the Joel Test?
    • 12 questions about your organisation
    • 14. "... a highly irresponsible, sloppy test to rate the quality of a software team"
    • 15. Rule-of-thumb for best practice
    • 16. How does it apply to PHP?
  • 17. The Joel Test (1-6)
    • Do you use source control?
    • 18. Can you make a build in one step?
    • 19. Do you make daily builds?
    • 20. Do you have a bug database?
    • 21. Do you fix bugs before writing new code?
    • 22. Do you have an up-to-date schedule?
  • 23. The Joel Test (7-12)
    • Do you have a spec?
    • 24. Do programmers have quiet working conditions?
    • 25. Do you use the best tools money can buy?
    • 26. Do you have testers?
    • 27. Do new candidates write code during their interview?
    • 28. Do you do hallway usability testing?
  • 29. What is the Joel Test For?
    • Scoring your current organisation
    • 30. Improving your current organisation
    • 31. Scoring your next organisation
    http://jobs.joelonsoftware.com
  • 32. Comparison Scores
    • Microsoft: 12/12
    • 33. Ibuildings: 8 or 9
    • 34. eZ Components: 8 or 9
    • 35. Red Embedded: 10
    • 36. Your organisation … ?
  • 37.  
  • 38. Source Control
    • Central storage
    • 39. Change history
    • 40. Enables collaboration
    • 41. Manage multiple versions
  • 42. Source Control Solutions
    • CVS
      • http://www.nongnu.org/cvs/
    • Subversion (svn)
      • http://subversion.tigris.org/
    • Git
      • http://git.or.cz/
    • Bazaar (bzr)
      • http://www.bazaar-vcs.org/
  • 43. Traditional Source Control user repo user user user
  • 44. Distributed Source Control repo repo repo repo repo
  • 45. Distributed Source Control
    • Local machine has repository
    • 46. Has full history
    • 47. Commit locally
    • 48. Commit globally later
  • 49. Recommendations subversion Developers using command line IDE plugins git-svn, bzr-svn bridges Designers using TortoiseSVN Managers using WebSVN
  • 50. Resources
    • git-svn
      • http://www.kernel.org/pub/software/scm/git/docs/git-svn.html
    • bzr-svn
      • http://bazaar-vcs.org/BzrForeignBranches/Subversion
    • WebSVN
      • http://www.websvn.info/
    • TortoiseSVN
      • http://tortoisesvn.tigris.org/
  • 51. Ask Me This In The Bar
  • 54.  
  • 55.  
  • 56. PHP is Interpreted
    • So do we care about builds?
  • 57. What's in a Build?
    • Code compilation
    • 58. Document generation
    • 59. Test suite execution and feedback
    • 60. Application deployment
    • 61. Packaging
  • 62. Ask Me This In The Bar
  • 65. Sounds like Continuous Integration
  • 66. Continuous Integration
    • A running process
    • 67. Responds to commit (and/or hooks)
    • 68. Performs tasks
    • 69. Gives feedback
  • 70. Continuous Integration
  • 71. Continuous Integration
  • 72. Continuous Integration Solutions
    • Hudson https://hudson.dev.java.net/
    • 73. phpUnderControl http://phpundercontrol.org/
    • 74. Xinc http://sourceforge.net/projects/xinc/
  • 75.
    • COMPULSORY
  • 76. I have a personal bug tracker
  • 77. Bug Trackers
    • Capture features/tasks
    • 78. Who does what?
    • 79. Progress for each task, keep updated
    • 80. Can reallocate items
  • 81. Bug Tracker Solutions
    • Trac http://trac.edgewall.org/
    • 82. Mantis http://www.mantisbt.org/
    • 83. Jira http://www.atlassian.com/software/jira/
    • 84. Eventum http://forge.mysql.com/wiki/Eventum/
    • 85. Hosted Options
  • 87.  
  • 88. Joel Says
    • Keep bugs near to zero
    • 89. Cannot estimate bug fix time
    • 90. Minimise unknowns
  • 91. Capturing Bugs
    • As a minimum, record bug
    • 92. Buggy behaviour
    • 93. Expected behaviour
    • 94. Smallest possible replication case
  • 95. How to Report a Bug
    • http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
    it's not worth reporting that the program generated an error unless you can also report what the error message was. if a computer does anything unexpected, freeze Some of the worst bug reports I've ever seen come from programmers Try to remember as much detail as you can about what you were doing to it when it did fall over, and if you see any patterns, mention them. Anything you can provide has to be some help.
  • 96.  
  • 97.  
  • 98. Scheduling Workflow collect requirements write specification separate into discrete tasks estimate task duration
  • 99. Who Estimates?
    • Ideally the do-er
    • 100. At least someone who could do it
    • 101. Never cut estimates
  • 102. Schedule
    • What each person is doing
    • 103. When it is due to finish
    • 104. Can record progress/actions
    • 105. What is next
  • 106. Specification
    • Holds the information needed for each task
    • 107. May include acceptance criteria
    • 108. More detail means fewer misunderstandings
      • mockups/pictures
      • 109. form fields
  • 110. Agile and Timings
    • Agile development is reactive
    • 111. Always on time at start of sprint
    • 112. Estimates and spec detail can be prepared per sprint
  • 113. Burndown Charts
    • List of tasks
    • 114. Tasks have estimates
    • 115. Sprint is as many tasks as you have man-hours
  • 116. Burndown Example
  • 117. Burndown Example (Mon)
  • 118. Burndown Example (Tue)
  • 119. Burndown Example (Wed)
  • 120. Burndown Example (Thu)
  • 121. Burndown Example (Fri)
  • 122.  
  • 123. Interruptions Meetings Phone Email
  • 124.  
  • 125. Tools
  • 129. Software
    • IDE
      • Zend Studio (£250)
      • 130. Visual Studio (£200)
      • 131. many free alternatives
    • Graphics
      • Photoshop (£450)
      • 132. Paint Shop Pro (£400)
      • 133. free alternatives
  • 134. Hardware
  • 135.  
  • 136.  
  • 137.  
  • 138.  
  • 139. Resources
    • Magazines
      • php|architect (£25 / year)
    • Site memberships
      • Experts' Exchange (pay per question)
      • 140. Safari (£155 / year)
    • Books
  • 141. Ask Me This In The Bar
    • Free resources
    • 142. How to train your employer
  • 143.  
  • 144. Assessing Candidate Code
    • During interview
    • 145. As part of recruitment process
    • 146. Ibuildings uses this
    • 147. The coding task makes a big impression on the candidate
  • 148.  
  • 149.  
  • 150. Testers are not developers Developers are not testers
  • 151. Tools for Testing in PHP
    • Unit Testing
    • Browser Testing
      • Selenium
  • 154. Points Missing from Joel's Test?
  • 155. Do you use test-driven development?
  • 156. Do you avoid reinventing the wheel?
  • 157. Do you help your employees to develop themselves professionally?
  • 158. And?
  • 159. http://joind.in/612