Your SlideShare is downloading. ×
0
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Rails conf2010 how to kill rails
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Rails conf2010 how to kill rails

997

Published on

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
997
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
1
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



  • bad practices
    minority of developers
    bad will for the Rails community

  • Rails rocks
    high end frame work
    huge amount done.
  • Rails provides short cuts
    get MORE done in the same time
    not the same done in LESS time

  • recent clients
    bad experiences with application developers
  • $3,000 website,
    PHP and Joomla developers here?
    Just don't do it. Say no
  • Not providing the service you promise.
    If you say you will do XYZ, then DO XYZ
  • We are all rock stars
    Quote 4-7 hours, and get it done in 5.
    Don’t do it the other way

  • Hidden costs, not being up front about costs
    Server costs
    Ramp up costs
    Get them used to PAYING for hosting
  • Not answering the phone, not having a phone number
  • Not answering email, answering in short "yes" or "no"
  • understanding client needs - we implement communication in our systems all the time, apply those same processes to your communication with your client
  • It is not a dirty word. Use your logo, have a style sheet
  • Keep a tone of effortless competence
    Logos consistent
    Have services you can refer to by name
  • Don’t trash your opposition
    Not cool
    unprofessional and under informed.
    Usually no idea on the other guys story
  • Refer to others, be honest
    By all means take on work to ramp up
  • Thanks
  • Transcript

    • 1. HOW TO KILL RAILS
    • 2. WHO?
    • 3. github.com/mikel mikel lindsaar @raasdnil
    • 4. WHAT?
    • 5. WHY?
    • 6. RESPONSIBILITY
    • 7. REASON
    • 8. UNDERCUTTING
    • 9. UNDERSERVICING
    • 10. UNDERQUOTING
    • 11. OBFUSCATION
    • 12. COMMUNICATION
    • 13. COMMUNICATION
    • 14. COMMUNICATION
    • 15. PROFESSIONALISM
    • 16. STYLE
    • 17. COMMUNITY
    • 18. REFERRALS
    • 19. THANKS mikel@rubyx.com github.com/mikel @raasdnil

    ×