a detail you probably didn't know: nowhere in any #curl documentation do we use the word "very".
-
a detail you probably didn't know: nowhere in any #curl documentation do we use the word "very". It is a banned word enforced by a CI check. This rule encourages us to rewrite and instead use more appropriate words. Makes us write better English.
@bagder
s/very/way -
a detail you probably didn't know: nowhere in any #curl documentation do we use the word "very". It is a banned word enforced by a CI check. This rule encourages us to rewrite and instead use more appropriate words. Makes us write better English.
@bagder “Substitute ‘damn’ every time you’re inclined to write ‘very’; your editor will delete it and the writing will be just as it should be.”
-
@bagder curl transfers are much secure
@moritzdietz @bagder bigly secure. The hugest security.
-
a detail you probably didn't know: nowhere in any #curl documentation do we use the word "very". It is a banned word enforced by a CI check. This rule encourages us to rewrite and instead use more appropriate words. Makes us write better English.
@bagder for a non-native speaker, what exactly is not good with the word 'very'?
-
@bagder for a non-native speaker, what exactly is not good with the word 'very'?
@shaman007 it is too simple. There is almost always a better way to phrase the same thing without it. very happy = excited, very glad = thrilled, very hungry = starving, etc. So the use of "very" is a sign that it can be said better.
-
@shaman007 it is too simple. There is almost always a better way to phrase the same thing without it. very happy = excited, very glad = thrilled, very hungry = starving, etc. So the use of "very" is a sign that it can be said better.
@bagder o need to wrap my head around this, never thought about it before.
-
R relay@relay.an.exchange shared this topic
-
@bagder o need to wrap my head around this, never thought about it before.
@shaman007 it takes a little getting used to I admit, but I find that it helps me write better
-
@shaman007 it is too simple. There is almost always a better way to phrase the same thing without it. very happy = excited, very glad = thrilled, very hungry = starving, etc. So the use of "very" is a sign that it can be said better.
@bagder thank you, mmm... a lot. No, appreciate for your answer!
-
I can tell you that this bites me just about every time I write more than two sentences. Then I go back, edit and push a fixup commit and hope that I learned something. Again.
@bagder I also block "just" this way, and "easy"
-
@bagder I also block "just" this way, and "easy"
@derickr I'm actually currently in process of doing the same for "just"!
-
a detail you probably didn't know: nowhere in any #curl documentation do we use the word "very". It is a banned word enforced by a CI check. This rule encourages us to rewrite and instead use more appropriate words. Makes us write better English.
@bagder That sounds, good!
-
a detail you probably didn't know: nowhere in any #curl documentation do we use the word "very". It is a banned word enforced by a CI check. This rule encourages us to rewrite and instead use more appropriate words. Makes us write better English.
@bagder very good
-
I can tell you that this bites me just about every time I write more than two sentences. Then I go back, edit and push a fixup commit and hope that I learned something. Again.
@bagder that's very often
-
-
@shaman007 it is too simple. There is almost always a better way to phrase the same thing without it. very happy = excited, very glad = thrilled, very hungry = starving, etc. So the use of "very" is a sign that it can be said better.
@bagder @shaman007 I would add to that point by saying that in technical writing, it's usually better to use adjectives to add information, rather than just adding emphasis. For me, the only information that "very" adds to a phrase like "WizWoz is very fast" is "Wow, it sure sounds like they really want me to believe that WizWoz is fast."
I'm going to be more skeptical than if the "very" hadn't been there! If WizWoz really were fast, they wouldn't need to throw in adjectives to persuade me.
-
@bagder @shaman007 I would add to that point by saying that in technical writing, it's usually better to use adjectives to add information, rather than just adding emphasis. For me, the only information that "very" adds to a phrase like "WizWoz is very fast" is "Wow, it sure sounds like they really want me to believe that WizWoz is fast."
I'm going to be more skeptical than if the "very" hadn't been there! If WizWoz really were fast, they wouldn't need to throw in adjectives to persuade me.
@lindsey @shaman007 indeed a good point!
-
a detail you probably didn't know: nowhere in any #curl documentation do we use the word "very". It is a banned word enforced by a CI check. This rule encourages us to rewrite and instead use more appropriate words. Makes us write better English.
@bagder we did a similar sort of cleanup (not a CI check tho) in @bridgetown a while back removing the word "just". Nobody can "just" run this command or "just" install that plugin any more.
-
@bagder I'm very glad you have such high standards!
@geerlingguy
I am thorougly pleased as well. Very thoroughly.
@bagder -
@bagder I also block "just" this way, and "easy"
-
a detail you probably didn't know: nowhere in any #curl documentation do we use the word "very". It is a banned word enforced by a CI check. This rule encourages us to rewrite and instead use more appropriate words. Makes us write better English.
