4 ms·

So, you can't really just appeal to the author's authority without addressing a single one of the parents points. Is he wrong? Do the statements from the artic

by doktrin 12y ago

So, you can't really just appeal to the author's authority without addressing a single one of the parents points. Is he wrong? Do the statements from the article make sense to you? Because the stuff he quoted looked like a bunch of nonsense.

thaumaturgy 12y ago
Oh, I have no idea if he's wrong or not. Honestly, programming isn't something I usually think deeply about; I'm sort of tired of all the usual arguments. But you don't have to assume that someone's a novice to disagree with them. That seems to be a common thing for programmers to do to each other and it's disgusting.
- doktrin 12y ago
  I feel ya. We're definitely a critical community, both for better and worse.
Dewie 12y ago
> So, you can't really just appeal to the author's authority without addressing a single one of the parents points. The 'appeal to authority' is addressing one of the parents points/claims: that he seems to be a rookie.
Blackthorn 12y ago
The parent's points were literally about his authority, so the response was perfectly fine.
- deleted 12y ago
  [deleted]
- doktrin 12y ago
  No, while he did make assumptions about the author's experience he directly addressed multiple points from the piece. It wasn't "just" about authority. Assumptions were made about authority based on bush league level mistakes in the writing.
geocar 12y ago
Sean wasn't making points. He was being obtuse and dismissive, and made repeated statements about the author and how much he was laughing at the idea that this was being read by anybody. I read it: I enjoyed it. I didn't run into anything I didn't understand, but I did feel like the phraseology was chosen to offend rather than inform. For example, "global variable" was used to describe any memory cell that could change from any point in the program, either directly or indirectly. Obviously any public function (setter or method) can change that value. If the instance variable is static or a member of a singleton, then it really is a global variable, but if the object is simply long-lived it might be equivalent with regards to the impact it has on debugging. Given that this isn't the ordinary use of the term "global variable", one has to read the article to understand that this is what is intended, but at least the article isn't very long. However because the author chose to overload the term (rightly or wrongly), it makes extracting the essence from a few quotes very difficult. However if you read the article: What part did you have trouble understanding?

by doktrin 12y ago

thaumaturgy 12y ago

Oh, I have no idea if he's wrong or not. Honestly, programming isn't something I usually think deeply about; I'm sort of tired of all the usual arguments. But you don't have to assume that someone's a novice to disagree with them. That seems to be a common thing for programmers to do to each other and it's disgusting.

doktrin 12y ago
I feel ya. We're definitely a critical community, both for better and worse.

Dewie 12y ago

> So, you can't really just appeal to the author's authority without addressing a single one of the parents points. The 'appeal to authority' is addressing one of the parents points/claims: that he seems to be a rookie.

Blackthorn 12y ago

The parent's points were literally about his authority, so the response was perfectly fine.

deleted 12y ago
[deleted]
doktrin 12y ago
No, while he did make assumptions about the author's experience he directly addressed multiple points from the piece. It wasn't "just" about authority. Assumptions were made about authority based on bush league level mistakes in the writing.

geocar 12y ago

Sean wasn't making points. He was being obtuse and dismissive, and made repeated statements about the author and how much he was laughing at the idea that this was being read by anybody. I read it: I enjoyed it. I didn't run into anything I didn't understand, but I did feel like the phraseology was chosen to offend rather than inform. For example, "global variable" was used to describe any memory cell that could change from any point in the program, either directly or indirectly. Obviously any public function (setter or method) can change that value. If the instance variable is static or a member of a singleton, then it really is a global variable, but if the object is simply long-lived it might be equivalent with regards to the impact it has on debugging. Given that this isn't the ordinary use of the term "global variable", one has to read the article to understand that this is what is intended, but at least the article isn't very long. However because the author chose to overload the term (rightly or wrongly), it makes extracting the essence from a few quotes very difficult. However if you read the article: What part did you have trouble understanding?