4 ms·
It was quite readable for me, although there were some sentences which stood out. How I see it is: A developer whose first language is not English (or even any
by jeswin 7y ago
It was quite readable for me, although there were some sentences which stood out. How I see it is: A developer whose first language is not English (or even any of the Western Languages which share similarities) made a fairly good README - which could be improved further by native speakers.
If you ask me to write a similar README in Japanese/Chinese/Thai, I wouldn't even know where to start.
- imtringued 7y agoI envy people who suck at grammar but are still capable of expressing their ideas because they know their vocabulary. They somehow managed to succeed at the hard parts before mastering the easy parts of a language.
- deleted 7y ago[deleted]
- andai 7y agoArguably, vocabulary is the easy part.
- sanxiyn 7y agoNo, vocabulary is the hard part. It's where you spend most of learning time.
- andai 7y agoIf you define vocabulary to include not just the words, but the appropriate usage-in-context, then sure. Arguably that's not a short formal list of rules you memorize, but an intuitive understanding of thousands of specific cases that can only be acquired through massive exposure to the language. I'm not sure what the word for that is, it's neither vocabulary nor grammar, and yet more important than either of them -- actually even more important than both vocabulary and grammar put together (lists of words and lists of rules).
- wongarsu 7y agoVocabulary is hard, but in asynchronous communication (like writing readmes) dictionaries allow you to reach far beyond your own vocabulary. Even choosing the right word for the specific context and audience is well covered by good dictionaries. For grammar there are barely any useful tools. Even tools like Gramarly are fairly primitive.