This is why you shouldn't interrupt a Programmer
Posted November 1st 2013 01:47 pm
I recently subscribed to the Startup Digest mailing list, which has been full of very helpful articles and references. Today, though, I saw something that I just had to share.
I previously wrote about my Thought Process and all of the steps that go into planning something mentally as far as all of the steps/obstacles/designs/concepts/etc that go into planning a site/program/application. However, I don't think that got the point across that I was trying to make.
Instead, this comic does a perfect job of making my point:
In summary: when a programmer, like myself, is deep in thought trying to figure something out, don't bother us with a tech support question, personal issues, clarification requests, etc. When we get into the thought process "zone", getting out is easy, but getting back in is hard (insert joke here).
Here's a reference from The Big Bang Theory to help illustrate my point (ignore the Raccoon virus stuff):
I previously wrote about my Thought Process and all of the steps that go into planning something mentally as far as all of the steps/obstacles/designs/concepts/etc that go into planning a site/program/application. However, I don't think that got the point across that I was trying to make.
Instead, this comic does a perfect job of making my point:
In summary: when a programmer, like myself, is deep in thought trying to figure something out, don't bother us with a tech support question, personal issues, clarification requests, etc. When we get into the thought process "zone", getting out is easy, but getting back in is hard (insert joke here).
Here's a reference from The Big Bang Theory to help illustrate my point (ignore the Raccoon virus stuff):