AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Git annotate vs git blame12/28/2023 ![]() ![]() ![]() In the case of git, I couldn't care less to be honest. What I mean here is, it's not a one size fits all approach and I disagree when you say positive language is always better. It has to do with the context, but not how well you know the person (btw if you know the person you probably don't need to remind him/her that). ![]() So, if I really want someone to be on time, I'll ask that person not to be late. "93% of PhD students registered early when a penalty fee for late registration was emphasized, with only 67% doing so when this was presented as a discount for earlier registration." There's also an example showing negative language works better: I didn't say you claimed that, but it's interesting to see you assumed someone did. But it makes me feel happy to use positive language whenever I can □ Now, git credit does the same job as git blame! Turns out it's not that complicated if you are some weird person like me who likes to use positive language in your git commands. Give yourself some credit you rockstar ❤️ Well, that's a lot more positive! Maybe I want to find who wrote that code so I can congratulate her on such a beautifully crafted piece of engineering. Publicly acknowledge a contributor's role in the production of (something published or broadcast). Why go with negative language when we could have something positive? We just want to find who wrote some code! But there are no mention that it's to find a fault or wrong doing. So, git blame tells you who wrote what code in a specific file. Git-blame - Show what revision and author last modified each line of a file But what's the point of the git blame command anyway? Isn't it kind of strange that they went with a negative word such as blame for the command?įeel or declare that (someone or something) is responsible for a fault or wrong.Įw, that's not really joyful. The reason I got to think about this was because of git blame. You'll be more likely to choose the option with the positive connotations rather than the option with the negative ones. In the second set, it is known as the framing effect. Well, in both cases I'd rather hear the second version of those statements. Please be on time at the restaurant tonight.Ħ6% chances you won't die, 33% chances you will die.Ħ6% chances it will save you, 33% chances you will be saved. Please don't be late at the restaurant tonight.Which of these would you like to hear better? Positive statements get more quickly received by the audience, but they are also well-received. How we express our ideas and our desires has a big impact on how our words will be received. ![]()
0 Comments
Read More
Leave a Reply. |