it always annoys me when people can't properly write about what they've done. For example, the description says, with reference to C: "I've turned it into something of a dynamic and powerful functional language which it might have once been" ...is his wording wrong or what? ...'cause C has never been a "powerful functional language"
Perhaps 'it might once have become' would make more sense there, in that it was a development the author thought could have happened in the past but did not?
not everyone is good at writing and expressing themselves in written language. quite a lot of good engineers actually struggle with this. definitely no need to be "annoyed", may be try helping him out?
I don't mean literary style or PR magic or anything, just using the words right so what comes out is exactly what you mean, not something that means something different but you have to use the context to understand what he probably thought about when writing that... If one can express his thought in a programming language, one can also use basic grammar like tenses and modes to say what he means... all this "words don't matter" attitude is what eventually ends up spreading and making wonderful pieces of software engineering unusable because of broken docs...
Comments
it always annoys me when people can't properly write about what they've done. For example, the description says, with reference to C: "I've turned it into something of a dynamic and powerful functional language which it might have once been" ...is his wording wrong or what? ...'cause C has never been a "powerful functional language"
Perhaps 'it might once have become' would make more sense there, in that it was a development the author thought could have happened in the past but did not?
not everyone is good at writing and expressing themselves in written language. quite a lot of good engineers actually struggle with this. definitely no need to be "annoyed", may be try helping him out?
I don't mean literary style or PR magic or anything, just using the words right so what comes out is exactly what you mean, not something that means something different but you have to use the context to understand what he probably thought about when writing that... If one can express his thought in a programming language, one can also use basic grammar like tenses and modes to say what he means... all this "words don't matter" attitude is what eventually ends up spreading and making wonderful pieces of software engineering unusable because of broken docs...