Erroneous Comments

Reading time ~1 minute

I am more and more becoming aware that when I make poor comments, especially when responding online, I have been blinded by some preconceived notion about the argument the other person was making and not addressing what the author actually meant.

Most recently I asked the author of an (article on Swift)[http://owensd.io/2014/08/28/tuples-new-struct.html] why he used tuples instead of multiple return values. Well, if I had done a little more digging I would have noticed that multiple return values are tuples. But when I originally read the article, I saw the named elements of the tuples in his example and didn’t connect that the multiple return values were tuples. Looking back it was quite clear, but I just missed it. Yes, I look foolish, but because I asked the author a question, at least I don’t look like a jerk.

I remember a couple of occasions online where I commented with my own arguments and looking back I didn’t fully comprehend the authors points and my own arguments just made me look like a loudmouth.

So, the lesson is to really dig a little deeper on an article you want to comment on. See if you truly understand the problem or issue the author is trying to address. Then if you still have a problem with their point of view, ask a question. Never assert your own arguments, especially online.

Perils of a Family-First Software Developer

I've just survived a RIF, my skills and tool set are built around technologies that were modern 10 years ago, my interviewing skills have...… Continue reading

AWS CodeStar and TypeScript - Part 3

Published on May 28, 2017

AWS CodeStar and TypeScript - Part 2

Published on May 17, 2017