CTO at SourceLevel·

Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.

SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.

As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?

READ LESS
Git, Linters and SourceLevel: how tools enable a more inclusive language and diverse culture – SourceLevel (sourcelevel.io)
15 upvotes·5 comments·318.4K views
Tracy Loisel
Tracy Loisel
·
July 31st 2020 at 1:30PM

First, I thought it was too much. After reading your article, it makes sense ! thank you

·
Reply
Weverton Timoteo
Weverton Timoteo
·
July 31st 2020 at 7:37PM

Yeah! I felt the same when I saw this for the first time, then I kept reading more about inclusive language and it changed the way I communicate through code and in other aspects of my life.

·
Reply
Ajay M
Ajay M
·
August 2nd 2020 at 5:42PM

Please don't get offended but I completely disagree with these recent changes.

And after seeing these posts, I think I'm using this as a platform to rant and I already apologise for that.

I don't care what terminologies you're using in your code, if it makes sense to put it there and it works then you're more than welcome but please don't go changing the standards which are been there for so many years.

This whole idea of changing names is stupid, only people who don't have much to do have time to start a drama over these things.

Why don't pianist are going the same way? Cause they're busy practising their butt off with master pieces. They don't have time to go over the thoughts like "Oh, if I call it black will it offend others" "I can't call it a minor key"

People getting offended by just "words" not actual meaning behind what the person really wants to convey is simply stupid.

·
Reply
Weverton Timoteo
Weverton Timoteo
·
August 3rd 2020 at 2:06PM

Hi Ajay, you're free to disagree! It's fine! But I'd recommend to always keep looking for better terminologies, usually, the people that didn't get offended cannot see how this is important.

If someone got offended and it's saying that these terminologies can be better, why not?

People are changing all the time, I see this as an opportunity to keep evolving as a developer and person and start communicating better with my teammates.

·
Reply
Ajay M
Ajay M
·
August 3rd 2020 at 2:17PM

I understand that if something makes someone uncomfortable in work environment then it should be pointed out and be changed if required.

I just can't wrap my head around why or how someone can just get offended by mere use of word "black", "white", "master/slave" while others are busy with their programs cause it is not working without even leaving anything on error log (elasticsearch that's for you!)

·
Reply
Avatar of Weverton Timoteo

Weverton Timoteo

CTO at SourceLevel