question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bad English writing

See original GitHub issue

Bug report

Hi! Thanks for this awesome project. This has alleviated a lot of configuration pains. However, I have some suggestions to make:

What’s wrong

Broken English in documentation and error messages all over the place, a good example is this. What do you mean “incorrect”? It’s correct, the linter just suggests an alternative style with little examples and bad English to explain the rationale.

This does not help the user to improve their code, this just adds confusion, or worse, nudge the users to turn off everything they don’t understand.

There are also lots of spelling errors, wrong usage of tenses, redundant words etc that make reading very unpleasant.

Even the Github issue template is bad. If should be “How should it be”, not “How is that should be”.

How is that should be

Get an English speaker on the team, or write strings in German, use gettext to extract them, and throw it into a service like Lokalise or Smartling to translate into English properly.

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:2
  • Comments:35 (21 by maintainers)

github_iconTop GitHub Comments

2reactions
Dreamsorcerercommented, Aug 18, 2020

The example given is perfectly valid English. I’m not sure why you think there is a language/grammar issue there.

It’s correct, the linter just suggests an alternative style with little examples and bad English to explain the rationale.

It’s incorrect according to the wemake rules, which should be implied by the fact you are using wemake’s opionated ruleset. I think reading the full explanation on that page is perfectly understandable for an experienced developer.

It could perhaps do with some minor improvements for less experienced developers though. For example: They may not understand some of the jargon (loop iter etc.) “…not make much sense. You can use tuples instead.” Doesn’t actually explain why. This is self-evident to an experienced developer, but newer developers might not understand why.

Overall, the level of English I’m seeing here is close to native, just some occassional small mistakes. So, I’m not really sure exactly why you think it’s a grammar/language issue, it seems to me that maybe you’re just expecting more detail? Maybe some examples of what you think it should look like would be useful?

1reaction
sobolevncommented, Sep 29, 2022

Sure, please change any docs you feel like changing 😃 I even cannot write well in my native language 😆

Read more comments on GitHub >

github_iconTop Results From Across the Web

Can you write bad English? - Quora
No. No one can. Good or bad are just relative things depends upon one's perspective. Like, your English might be bad from the...
Read more >
Bad English: 33 Grammar Lessons to Help Students Write Better
Bad English : 33 Grammar Lessons to Help Students Write Better. Catching the Dream is looking for a few good essays from Native...
Read more >
Bad Writing - sample pages from Improve your Writing Skills
Bad Writing - sample pages from Improve your Writing Skills, a downloadable PDF eBook covering all aspects of writing and communication skills.
Read more >
Your English writing is BAD because... - YouTube
If you like my videos, I think you'll really enjoy my full courses. Check out the link to get a special discount! https://www.lukepriddy....
Read more >
Sample BAD and GOOD paragraphs - Writing Help (formatting ...
Writing Help (formatting, templates, and writing samples): Sample BAD and GOOD paragraphs. APA, MLA, Chicago styleguide help; sample assignment, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found