Fossil SCM

More typo fixes in the Rebase document.

drh 2019-09-04 20:02 trunk
Commit aaacce23cd81f057d1bac8271cc0db74aa6d3ce2b6f9458cd0e53ca0b560e2be
1 file changed +2 -2
--- www/rebaseharm.md
+++ www/rebaseharm.md
@@ -139,16 +139,16 @@
139139
one another. Similar finds arise in other disciplines. Keeping
140140
private branches is a key symptom of siloing.
141141
142142
[Weinberg][weinberg] argues programming should be "egoless". That
143143
is to say, programmers should avoid linking their code with their sense of
144
-self, as they makes it more difficult for them to find and respond
144
+self, as that makes it more difficult for them to find and respond
145145
to bugs, and hence makes them less productive. Many developers are
146146
drawn to private branches out of sense of ego. "I want to get the
147147
code right before I publish it". I sympathize with this sentiment,
148148
and am frequently guilty of it myself. It is humbling to display
149
-your stupid mistake to the whole world on the open internet that
149
+your stupid mistake to the whole world on an internet that
150150
never forgets. And yet, humble programmers generate better code.
151151
152152
## Rebase commits untested check-ins to the blockchain
153153
154154
Rebase adds new check-ins to the blockchain without giving the operator
155155
--- www/rebaseharm.md
+++ www/rebaseharm.md
@@ -139,16 +139,16 @@
139 one another. Similar finds arise in other disciplines. Keeping
140 private branches is a key symptom of siloing.
141
142 [Weinberg][weinberg] argues programming should be "egoless". That
143 is to say, programmers should avoid linking their code with their sense of
144 self, as they makes it more difficult for them to find and respond
145 to bugs, and hence makes them less productive. Many developers are
146 drawn to private branches out of sense of ego. "I want to get the
147 code right before I publish it". I sympathize with this sentiment,
148 and am frequently guilty of it myself. It is humbling to display
149 your stupid mistake to the whole world on the open internet that
150 never forgets. And yet, humble programmers generate better code.
151
152 ## Rebase commits untested check-ins to the blockchain
153
154 Rebase adds new check-ins to the blockchain without giving the operator
155
--- www/rebaseharm.md
+++ www/rebaseharm.md
@@ -139,16 +139,16 @@
139 one another. Similar finds arise in other disciplines. Keeping
140 private branches is a key symptom of siloing.
141
142 [Weinberg][weinberg] argues programming should be "egoless". That
143 is to say, programmers should avoid linking their code with their sense of
144 self, as that makes it more difficult for them to find and respond
145 to bugs, and hence makes them less productive. Many developers are
146 drawn to private branches out of sense of ego. "I want to get the
147 code right before I publish it". I sympathize with this sentiment,
148 and am frequently guilty of it myself. It is humbling to display
149 your stupid mistake to the whole world on an internet that
150 never forgets. And yet, humble programmers generate better code.
151
152 ## Rebase commits untested check-ins to the blockchain
153
154 Rebase adds new check-ins to the blockchain without giving the operator
155

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button