Lean mean php machine

8,453 views
8,298 views

Published on

Implementing software development “best practices” can be a challenging feat, especially if you are in a very small team of developers. Little to no budget, stress to just “get something out”, and lack of understanding from management of what you really do means you have to make sacrifices, right? This talk will give you some insight on accomplishing your goals of being a top-rated development shop, even if you are an army of one. From justifying those best practices to utilizing free services to hiring additional help, this talk will run the gamut of running a software development shop at a small scale.

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

  • Be the first to like this

No Downloads
Views
Total views
8,453
On SlideShare
0
From Embeds
0
Number of Embeds
169
Actions
Shares
0
Downloads
22
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Lean mean php machine

  1. 1. Lean Mean PHP Machine Jason Austin @jason_austin TEK-X Friday, May 21, 2010
  2. 2. A little about me... Friday, May 21, 2010
  3. 3. The team at NC State 2 full time employees 2 part time students 1 manager Friday, May 21, 2010
  4. 4. We do “the internet” Support apps Campus-wide initiatives Community engagement Friday, May 21, 2010
  5. 5. A little history Started with one part-time developer No standards No best practices No idea what I was doing Friday, May 21, 2010
  6. 6. A little more history... Added a developer and a manager Went to ZendCon 2006 Plugged into #phpc Re-invented ourselves Friday, May 21, 2010
  7. 7. Daily challenges Our business is not so'ware Budget Educating management Demanding clientele Friday, May 21, 2010
  8. 8. David vs. Goliath Friday, May 21, 2010
  9. 9. Goliath Shops Project managers UI designers Code developers QA staff Support staff flickr @gadgetgirl70 Friday, May 21, 2010
  10. 10. Goliath Shops Multiple people responsible Focus on a single part of a project Anonymity Lack of payoff Friday, May 21, 2010
  11. 11. David Shops Everyone is responsible for everything Hazy job responsibilities flickr @helico Friday, May 21, 2010
  12. 12. David Shops Focus on the whole project (or multiple projects) Support a'er release Make your mark See the payoff Friday, May 21, 2010
  13. 13. To be successful Hire and retain great developers Spend money wisely Communicate and collaborate Code smarter Friday, May 21, 2010
  14. 14. Tip #1 Successful shops are built on the backs of successful people Friday, May 21, 2010
  15. 15. It starts with hiring Know your needs Targeted, clear job descriptions Post everywhere Recruit Reputation Friday, May 21, 2010
  16. 16. Hiring is risky Contract positions Part-time workers Outsource Friday, May 21, 2010
  17. 17. Bad hires are poison Trust Efficiency Culture clash Friday, May 21, 2010
  18. 18. Who do we interview? LinkedIn, Resumé Blog, twitter, facebook Ask for code Virtual interviews Friday, May 21, 2010
  19. 19. Interviews suck Not a true representation of skill Easy to fake Time waster for the existing team Friday, May 21, 2010
  20. 20. But if it’s required... Don’t play games Have a loose plan Ask what you want to know Friday, May 21, 2010
  21. 21. Face time See how they think Problem solving skills Communication skills Friday, May 21, 2010
  22. 22. The successful types: Motivated (are you interested) Go-getter Eager to learn Engaged Team Player Friday, May 21, 2010
  23. 23. Be part of the process Read resume’s Research Interview if you have to Friday, May 21, 2010
  24. 24. Team assembled. Now what? Friday, May 21, 2010
  25. 25. Care for the team Feed and water daily Encourage participation Engage Reward Compensate Friday, May 21, 2010
  26. 26. Build team chemistry Get away from your workspace Sports? Video games? Beer? Whatever it takes Avoid crazy HR team building exercises Friday, May 21, 2010
  27. 27. Keep the good devs Hiring new devs is expensive Training Exposure to apps Institutional knowledge Friday, May 21, 2010
  28. 28. Tip #2 A happy developer is a productive developer Friday, May 21, 2010
  29. 29. Developers are unique Platform IDE Hours Work environment Friday, May 21, 2010
  30. 30. Listen Open participation Feedback sessions Find what fits each dev and go with it Friday, May 21, 2010
  31. 31. Shield the new guys Meetings generally suck Block out time Keep politics to a min Friday, May 21, 2010
  32. 32. Management Manage up or around Facts Deliverables Friday, May 21, 2010
  33. 33. Training Continuous and Strategic Webinars are cheap Team up Friday, May 21, 2010
  34. 34. Telecommuting Works for some, not all More focus Small, dark places where awesome code lives Friday, May 21, 2010
  35. 35. Tip #3 Spend money where you get the most bang for your buck Friday, May 21, 2010
  36. 36. Open Source is your friend Project Management Issue Tracking Administrative Tools Productivity Tools Friday, May 21, 2010
  37. 37. Use existing tools Codebase management Support Cheaper in the long run Friday, May 21, 2010
  38. 38. Prove the value Case studies Documentation Expert Trusted advice Friday, May 21, 2010
  39. 39. Follow through Results are critical Credibility Makes the next request easier Friday, May 21, 2010
  40. 40. Tip #4 Join in the discussion at every level flickr: @danielygo Friday, May 21, 2010
  41. 41. Get local Meetup.com Find a user group Connect with colleagues Friday, May 21, 2010
  42. 42. Get global IRC at #phpc Twitter Conferences Friday, May 21, 2010
  43. 43. Put yourself out there PHPers aren’t scary (mostly) Take initiative Connect yourself, then connect others Friday, May 21, 2010
  44. 44. Tip #5 Reduce, reuse, recycle Friday, May 21, 2010
  45. 45. Write once, use many Code reusability Module portability Testability Friday, May 21, 2010
  46. 46. Frameworks! Use them...now Zend Framework CakePHP Symphony Whatever Friday, May 21, 2010
  47. 47. Code re-use OT Framework Auth and ACL Navigation Themes It’s an app shell Friday, May 21, 2010
  48. 48. Re-use benefits Setup time Common methods Upgradability Friday, May 21, 2010
  49. 49. Last Tip Integrate best practices from the start flickr @enerva Friday, May 21, 2010
  50. 50. Development is not just typing Testing is a requirement, not a feature Plan for usability and accessibility Design then develop Single-step deployment Friday, May 21, 2010
  51. 51. flickr @lwr Any questions? Friday, May 21, 2010
  52. 52. Rate me on Jason Austin @jason_austin http://www.jasonawesome.com Review this talk at http://joind.in/1608 Friday, May 21, 2010

×