Download to read offline
Uploaded bySarah Allen
Ruby Nation: Why no haz Ruby?
The document discusses various initiatives aimed at improving citizen engagement with government services, including the MyUSA platform and various projects supported by the Smithsonian Institution. It emphasizes the importance of user-centric development and collaboration with non-developers in creating applications. The document also highlights the challenges of coding and the impact of choosing development frameworks on the innovation process.
More Related Content
Similar to Ruby Nation: Why no haz Ruby?
Ruby Nation: Why no haz Ruby?
- 2.
- 3.
- 4.
- 5.
- 9. 1. Sarah goesto Washington 2. What I did @Smithsonian 3. Why not Ruby?
- 13. Disaster Response MyUSA RFP-EZ Cyber-Physical Systems OpenData MyData Innovation Toolkit 21st Century Financial Systems Development Innovation Ventures VA Modernization Presidential Innovation Fellows Round 2 Projects
- 14. Disaster Response MyUSA RFP-EZ Cyber-Physical Systems OpenData MyData Innovation Toolkit 21st Century Financial Systems Development Innovation Ventures VA Modernization Presidential Innovation Fellows Round 2 Projects
- 15. http://MyUSA.gov easier access togovernment services
- 16. MyUSA is ajoint initiative between the White House and the General Services Administration to reimagine how citizens interact with government. A platform for building tools and services connecting citizens and businesses to government agencies. What is MyUSA?
- 17.
- 18.
- 19. Disaster Response MyUSA RFP-EZ Cyber-Physical Systems OpenData MyData Innovation Toolkit 21st Century Financial Systems Development Innovation Ventures VA Modernization Presidential Innovation Fellows Round 2 Projects
- 20. Disaster Response MyUSA RFP-EZ Cyber-Physical Systems OpenData MyData Innovation Toolkit 21st Century Financial Systems Development Innovation Ventures VA Modernization Presidential Innovation Fellows Round 2 Projects
- 21.
- 24. 19 museums 9 researchcenters 23 libraries 15 archives
- 25.
- 26. and members of thepublic to learn about. researchers to study and discover, curators to organize and document, The Smithsonian has seriously amazing treasures for...
- 39. Not Just Picturesof Things
- 40.
- 41.
- 42.
- 45.
- 46.
- 47.
- 49. Botany Workflow EMU Transcription Center US Herbarium 3.7MPlants Digital Surrogate 1000/wk EMU SI Staff Volunteer Work SI Staff SI StaffSI Staff Validation
- 50. Botany Workflow EMU Transcription Center US Herbarium 3.7MPlants Digital Surrogate 1000/wk EMU SI Staff Volunteer Work SI Staff SI StaffSI Staff Validation
- 51. Botany Workflow EMU Transcription Center US Herbarium 3.7MPlants Digital Surrogate 1000/wk EMU SI Staff Volunteer Work SI Staff SI StaffSI Staff Validation
- 52. Botany Workflow EMU Transcription Center US Herbarium 3.7MPlants Digital Surrogate 1000/wk EMU SI Staff Volunteer Work SI Staff SI StaffSI Staff Validation
- 53. Improved Botany Workflow EMU Transcription Center USHerbarium 3.7M Plants Digital Surrogate 1000/wk EMU SI Staff Volunteer Work Software SI Staff Validation Software
- 54.
- 55.
- 57.
- 58.
- 59. Writing code... can bechallenging
- 60. Writing code... not thehard part
- 61.
- 63. Choice of Framework = Choiceof Language
- 65.
- 67. Choosing functionality can bea “user concern” (James Edward Gray) Non-developers co-create our applications
- 69. Over 1 millionactive Drupal sites
- 70. Rails, not Ruby,leads us into a rigid dev-test-deploy cycle (Avdi Grimm)
- 71. Rails, not Ruby,leads us into a rigid dev-test-deploy cycle (Avdi Grimm) UI Features can be added at runtime
- 72. Ruby optimizes for developerhappiness
- 73.
- 74. the developer couldfocus on unique aspects that require innovation
- 75. We don’t sustainframeworks... ...with a user experience.
- 76. Framework leads tolanguage Add UI features at runtime? Non-developers are co-creators