In the United States, Ruby is a common technology choice for startups and is also gaining popularity in large companies. In contrast, Ruby is rarely used for US Government projects. Why do startups favor Ruby while the government makes other choices?
I have been both a startup founder and government employee. After developing a Ruby on Rails web app for my startup Mightyverse from 2009, I worked as a Presidential Innovation Fellow within the Obama administration. I will discuss work in both spheres, and highlight the common themes in the development process.
14. 130 most commonly used services
available on-line, anywhere, anytime,
and in both official languages
2006
Canada
Government On Line
http://publications.gc.ca/collections/Collection/P4-1-2006E.pdf
15. gov.uk replaced hundreds of websites
streamlining access to most used
services and information
2012
United Kingdom
Government Digital Service (GDS)
16. “the strategy is delivery”
— Mike Bracken, Head of Government Digital Service
United Kingdom
Government Digital Service (GDS)
18. “Making the thing makes scary things
feel exciting and achievable”
— Leisa Reichelt, Head of User Reseach
Government Digital Service
United Kingdom
Government Digital Service (GDS)
19. allow wider public access to government data
to improve the transparency of state affairs
2013
Republic of Korea
Government 3.0
20.
21. “I want us to ask ourselves every day,
how are we using technology to make a
real difference in people’s lives.”
— US President Barack Obama
United States of America
Digital Government Strategy
http://www.whitehouse.gov/sites/default/files/omb/egov/digital-government/digital-government.html
22. United States of America
Digital Government Strategy
United
States
Digital
Service
24. U.S. Digital Services Playbook米国. ディジタルサービスのPlaybook
1. 人々が必要とするものを
理解する。
2. 全経験に、始めから
終わりまで演説しなさい。
3. それを簡単および
直観的にする。
1. Understand what people need
2. Address the whole experience,
from start to finish
3. Make it simple and intuitive
https://playbook.cio.gov/
25. U.S. Digital Services Playbook米国. ディジタルサービスのPlaybook
4. 敏捷で、
反復的な練習を使用して
サービスをつくる。
5. 納品をサポート
する予算と構造を構築する。
4. Build the service using
agile and iterative practices
5. Structure budgets & contracts
to support delivery
https://playbook.cio.gov/
26. U.S. Digital Services Playbook米国. ディジタルサービスのPlaybook
6. 1人のリーダーを割り当て、
その人が説明責任を持つ
7. ベテランのチームで
6. Assign one leader and
hold that person accountable
7. Bring in experienced teams
https://playbook.cio.gov/
27. U.S. Digital Services Playbook米国. ディジタルサービスのPlaybook
8. 新しいテクノロジー
スタックを選ぶ。
9. 適用範囲が広いホ
スト環境で展開する。
10.テストとデプロイを
自動化する。
11.再使用可能な
プロセスによってセキュリティおよびプライバシーを管理する。
8. Choose a modern technology stack
9. Deploy in a flexible
hosting environment
10.Automate testing & deployments
11.Manage security and privacy
through reusable processes
https://playbook.cio.gov/
28. U.S. Digital Services Playbook米国. ディジタルサービスのPlaybook
12.データを使用して
決定する。
13.オープンであることを
デフォルトにする。
12.Use data to drive decisions
13.Default to open
https://playbook.cio.gov/