Re:Why You Shouldn't Interrupt a Programmer
by tmikaeld on Monday October 28, 2013 @04:45AM
(#6625832)
http://i.imgur.com/xvNRKIT.png
[ Parent
| on HN ]
I downvoted you before I realise you just provided a copy of the actual post. Please include some context next time and not just dump an imgur link.
Re:Why You Shouldn't Interrupt a Programmer
by lignuist on Monday October 28, 2013 @05:45AM
(#6626010)
So you downvoted something that you did not even look at?
A post that expresses little thought should be down-voted. The post in question is of value since the original link 503'd, but that value is obfuscated to some by the lack of a quick "Here's a mirror" explanation.
Is this really a big deal?
Back when I first tried opening the page it 503ed and there was just one page of comments, one of them was this image link. Its purpose was fairly clear, actually. And helpful.
Re:Why You Shouldn't Interrupt a Programmer
by strickjb9 on Monday October 28, 2013 @11:15AM
(#6627417)
No it's not clear but it was helpful. There is an implication that a simple imgur link could be a mirror of the comic image. But then you would have to know that the content of the article was a comic image.
Re:Why You Shouldn't Interrupt a Programmer
by matthuggins on Monday October 28, 2013 @12:19PM
(#6627822)
The original page 503'd for me as well, and I wouldn't have known that the imgur link was a mirror if it wasn't for the replies to it (since I just Cmd+F "mirror" to find this).
Re:Why You Shouldn't Interrupt a Programmer
by Cthulhu_ on Monday October 28, 2013 @06:11AM
(#6626103)
Well, links are always better with context or a title. Same with youtube links - I frequently don't click them when there is no context or any clue about the contents. And in youtube's case, it could be a rick roll.
Anything but a rick roll!