![Who am I? ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (16)
Similar a Passing The Joel Test In The PHP World
Similar a Passing The Joel Test In The PHP World (20)
Más de Lorna Mitchell
Más de Lorna Mitchell (20)
Último
Último (20)
Passing The Joel Test In The PHP World
- 1. Passing the Joel Test in the PHP World
- 3. PHP Developer at Ibuildings
- 4. Personal site http://lornajane.net
- 5. European Rep for phpwomen.org
- 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
- 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?
- 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?
- 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?
- 30. Improving your current organisation
- 31. Scoring your next organisation http://jobs.joelonsoftware.com
- 33. Ibuildings: 8 or 9
- 34. eZ Components: 8 or 9
- 35. Red Embedded: 10
- 36. Your organisation … ?
- 39. Change history
- 43. Traditional Source Control user repo user user user
- 44. Distributed Source Control repo repo repo repo repo
- 46. Has full history
- 47. Commit locally
- 49. Recommendations subversion Developers using command line IDE plugins git-svn, bzr-svn bridges Designers using TortoiseSVN Managers using WebSVN
- 52. Tagging
- 53. Versions
- 59. Test suite execution and feedback
- 61. Packaging
- 63. Rollback
- 64. Databases
- 65. Sounds like Continuous Integration
- 67. Responds to commit (and/or hooks)
- 68. Performs tasks
- 69. Gives feedback
- 76. I have a personal bug tracker
- 78. Who does what?
- 79. Progress for each task, keep updated
- 86. sourceforge
- 89. Cannot estimate bug fix time
- 92. Buggy behaviour
- 94. Smallest possible replication case
- 98. Scheduling Workflow collect requirements write specification separate into discrete tasks estimate task duration
- 100. At least someone who could do it
- 101. Never cut estimates
- 103. When it is due to finish
- 105. What is next
- 107. May include acceptance criteria
- 109. form fields
- 111. Always on time at start of sprint
- 112. Estimates and spec detail can be prepared per sprint
- 114. Tasks have estimates
- 115. Sprint is as many tasks as you have man-hours
- 116. Burndown Example
- 123. Interruptions Meetings Phone Email
- 126. Hardware
- 127. Resources
- 128. All cost money (or time, or effort)
- 130. Visual Studio (£200)
- 132. Paint Shop Pro (£400)
- 133. free alternatives
- 134. Hardware
- 142. How to train your employer
- 145. As part of recruitment process
- 146. Ibuildings uses this
- 147. The coding task makes a big impression on the candidate
- 150. Testers are not developers Developers are not testers
- 152. SimpleTest
- 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
Notas del editor
- 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