(add section header "Case studies") |
(→Case studies: counterfactual) |
||
| Line 3: | Line 3: | ||
== Case studies == |
== Case studies == |
||
In 2020, [https://jekyllrb.com jekylrb.com] (<small>[http://web.archive.org/web/20200622190810/https://jekyllrb.com/ jekyllrb.com archived]</small>), the homepage of the Jekyll [https://en.wikipedia.org/wiki/Static_site_generator static site generator] is an especially good example. Jekyll is implemented in Ruby, and the Jekyll developers feel at home in the Ruby ecosystem. The Jekyll developers, therefore, are operating from a foregone conclusion that Ruby is available and that it will be an easy task for its audience to run Jekyll. There's an implicit assumption that a user's computer will have a system configuration that is close to the Jekyll developers' own machines. It is very likely the case, however, that a given user's machine does not have the necessary software to run Jekyll, since |
In 2020, [https://jekyllrb.com jekylrb.com] (<small>[http://web.archive.org/web/20200622190810/https://jekyllrb.com/ jekyllrb.com archived]</small>), the homepage of the Jekyll [https://en.wikipedia.org/wiki/Static_site_generator static site generator] is an especially good example. Jekyll is implemented in Ruby, and the Jekyll developers feel at home in the Ruby ecosystem. The Jekyll developers, therefore, are operating from a foregone conclusion that Ruby is available and that it will be an easy task for its audience to run Jekyll. There's an implicit assumption that a user's computer will have a system configuration that is close to the Jekyll developers' own machines. It is very likely the case, however, that a given user's machine does not have the necessary software to run Jekyll, since Jekyll's potential audience is simply the set of people that would find a static site generator to be useful, and not merely the set of all Ruby developers who is in the "market" for a static site generator. It is this assumption that is responsible for the fact that the Jekyll homepage touts that one is able to "get up and running <em>in seconds</em>" (emphasized in the original) and presents a facsimile of a terminal emulator showing the three commands that comprise the "Quick-start Instructions". |
||
The Jekyll folks—including its developers <em>and its users</em>—are experiencing a sort of "tunnel vision" that makes them blind to the the potential pitfalls that the uninitiated are likely encounter. On the Light Table blog, the Light Table team documents a generalization of this phenomenon under a post titled "[http://lighttable.com/2014/05/16/pain-we-forgot/ Pain We Forgot]". |
The Jekyll folks—including its developers <em>and its users</em>—are experiencing a sort of "tunnel vision" that makes them blind to the the potential pitfalls that the uninitiated are likely encounter. On the Light Table blog, the Light Table team documents a generalization of this phenomenon under a post titled "[http://lighttable.com/2014/05/16/pain-we-forgot/ Pain We Forgot]". |
||
Revision as of 12:44, 16 April 2022
Implicit step zero is the step that natives of a particular ecosystem always leave out of their onboarding and setup instructions. Usually, this "step" is actually multiple steps, which are themselves some combination of tedious and/or deflating from the perspective of the uninitiated.
Case studies
In 2020, jekylrb.com (jekyllrb.com archived), the homepage of the Jekyll static site generator is an especially good example. Jekyll is implemented in Ruby, and the Jekyll developers feel at home in the Ruby ecosystem. The Jekyll developers, therefore, are operating from a foregone conclusion that Ruby is available and that it will be an easy task for its audience to run Jekyll. There's an implicit assumption that a user's computer will have a system configuration that is close to the Jekyll developers' own machines. It is very likely the case, however, that a given user's machine does not have the necessary software to run Jekyll, since Jekyll's potential audience is simply the set of people that would find a static site generator to be useful, and not merely the set of all Ruby developers who is in the "market" for a static site generator. It is this assumption that is responsible for the fact that the Jekyll homepage touts that one is able to "get up and running in seconds" (emphasized in the original) and presents a facsimile of a terminal emulator showing the three commands that comprise the "Quick-start Instructions".
The Jekyll folks—including its developers and its users—are experiencing a sort of "tunnel vision" that makes them blind to the the potential pitfalls that the uninitiated are likely encounter. On the Light Table blog, the Light Table team documents a generalization of this phenomenon under a post titled "Pain We Forgot".
Triple scripts were invented to tackle the problems associated with implicit step zero in traditional software development. The triplescripts.org group urges project creators and maintainers follow the ABCs of triple scripts to eradicate implicit step zero.