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.

1. Ruby in the US Government
Sarah Allen!
@ultrasaurus!
!
米大統領イノベーションフェロー!
Presidential Innovation Fellow

2. User Centric Design
Agile Development
US Government

5. Bridge Foundry

7. I love Ruby

8. “The goal of Ruby
is to make
programmers
happy.”

9. Ruby
also good for business

10. Flexible
Expressive
Solid Test Frameworks

11. Software
grows & changes
to meet market needs.

12. Language is Power
言語は、パワーです。

13. is Ruby good
for Government?

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)

17. 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

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

23. https://playbook.cio.gov/

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/

29. https://playbook.cio.gov/

32. US Government
Experience

33. 米大統領イノベーションフェロー!

34. http://bit.ly/exec-order-open-data

36. 19 博物館
9 研究所
23 図書館
15 書庫
archives
museums
libraries
research centers

37. 1.37億specimens, art works and other treasures...
with over...
13.6万 cubic feet
of archival material

54. ５百万 plant specimens

55. 3.7 百万
without
digital records

56. This
is the
record
(structured data)

59. Why Not Ruby?

60. Why Not Ruby?
三

61. CMS
High Level Components
Little Custom Code

62. 一
CMS
Content Management System

65. 一
Ruby CMS?

66. 0
300,000
600,000
900,000
1,200,000
Refinery
Comfortable!
Mexican Sofa
Browser CMS
Radiant
Alchemy
Locamotive
Drupal 7
Drupal 6
Downloads
Active Installs

67. 0
300,000
600,000
900,000
1,200,000
Refinery
Comfortable!
Mexican Sofa
Browser CMS
Radiant
Alchemy
Locamotive
Drupal 7
Drupal 6
Ruby CMS?
Active Installs

69. 二
High Level Components

72. I can build a blog in
5 minutes!

74. Ruby
Components

75. Ruby
Components
separate pieces assembled by a developer

78. OmniAuth

79. OmniAuth
Bootstrap

80. OmniAuth
Bootstrap

81. User Interface
Admin
Interface
Code

82. User Interface
Admin
Interface
Code

83. User Interface
Admin
Interface
Code

84. User Interface
Admin
Interface
Code

85. 自動にしないものは
What we do not automate
!
また繰り返す
we are doomed to repeat.

86. 三

87. 三!
!
Little Custom Code

88. 三!
!
Biggest Challenge
is not code

89. Framework choice
leads to language choice.
フレームワークの選択は、
言語の選択につながります。

90. CMS
CODE
time
100%
0%

91. CMS CODE
time
100%
0%
BIGREWRITE

92. Frameworks
are patterns for how we work
フレームワークは、
私達が働くパターンです。

93. Ever notice that the top
Ruby CMS options
are all Rails apps…?

94. A Ruby Story

96. https://github.com/18F/notalone
User Research
Tech Policy / LegalSecurity Design

97. https://github.com/18F/notalone
Admin Interface Web Site
markdown
yaml

99. Alternate
CMS
Approach

102. コンポーネントのエコシステム
語と同様に重要です。

103. 言語は、パワーです。

104. 私たちは
新たな力を生み出すことができる
We can create
new powers.

105. ルビーが良く
なるためには
新たな力が必要
!
!
We need
a few new powers
for Ruby to be better

106. ルビーが良く
なるためには
新たな力が必要
官庁の為に
We need
a few new powers
for Ruby to be better
for government
!

107. ルビーが良く
なるためには
新たな力が必要
官庁の為に
そして皆さんの為に
We need
a few new powers
for Ruby to be better
for government
and for everyone.

108. 質問はありますか？