You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2014-11-11-rubinius-3-0-part-2-the-process.markdown
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Our priority is to have an _impact_, providing value to people using Rubinius. W
16
16
17
17
> If it doesn't work when someone tries it, they may wait a long time before trying it again, if ever.
18
18
19
-
There are several problems with this fallacy. It confuses local and global effects. For every one person for whom a feature did not work, there are an unknown number of people for whom some feature did work. The latter group may have a much bigger global affect than the one person. It also does not account for the cost of people waiting for features. Finally, it's rooted in fear. The best antidote to fear is facts. If engagement is important, we should measure engagement and take steps to improve it.
19
+
There are several problems with this fallacy. It confuses local and global effects. For every one person for whom a feature did not work, there are an unknown number of people for whom some feature did work. The latter group may have a much bigger global effect than the one person. It also does not account for the cost of people waiting for features. Finally, it's rooted in fear. The best antidote to fear is facts. If engagement is important, we should measure engagement and take steps to improve it.
20
20
21
21
Now that we know what to *not* do, what should we do? To understand that, we need to question how we release software.
22
22
@@ -36,7 +36,7 @@ The fact that features are constantly being developed does not mean that a syste
36
36
37
37
As opposed to mechanical systems, biological systems are *very well adapted* to functioning as a whole while changing or growing. Consider the difference between a plant growing from a seed and building a car. It's only at the very end of the manufacturing process that a car is able to function as a whole. Meanwhile, the fundamental metabolic processes in a plant function from the very beginning. The plant changes as it grows, so not every part is functional at the start. The key is to decide which parts should function first.
38
38
39
-
Another important aspect of biological systems is where the boundaries lie. There are cellular boundaries, system boundaries, and the organism as a whole, which has a boundary between itself and its environment. These boundaries serve the dual purpose of keeping things separate but in contact. Along with these boundaries, different parts of a biological system have different degrees of resilience. For example, a skeleton versus soft tissue. These two concepts—boundaries and joining different types of resilience—can be useful in understanding software release. I'll return to them later.
39
+
Another important aspect of biological systems is where the boundaries lie. There are cellular boundaries, system boundaries, and the organism as a whole, which has a boundary between itself and its environment. These boundaries serve the dual purpose of keeping things separate but in contact. Along with these boundaries, different parts of a biological system have different degrees of resilience. For example, a skeleton versus soft tissue. These two concepts—boundaries and joining different types of resilience—can be useful in understanding software releases. I'll return to them later.
40
40
41
41
### Releasing Costs A Lot
42
42
@@ -77,7 +77,7 @@ Besides changing the focus of the release process, we are adding a feature to Ru
77
77
The first time you start Rubinius after a fresh installation, if the setting does not already exist, you'll get a message like the following:
78
78
79
79
Rubinius is able to automatically install new versions. Installing
80
-
a new version will not overwrite you existing version.
80
+
a new version will not overwrite your existing version.
81
81
82
82
Enable this feature? ([Y]es, [n]o, [a]uto, ne[v]er, [h]elp):
0 commit comments