Programmers, teach non-geeks the true cost of interruptions (2014)
1–10 of 253 posts
Re: Programmers, teach non-geeks the true cost of interruptions (2014)
#2Re: Programmers, teach non-geeks the true cost of interruptions (2014)
#3Re: Programmers, teach non-geeks the true cost of interruptions (2014)
#4Re: Programmers, teach non-geeks the true cost of interruptions (2014)
#5Re: Programmers, teach non-geeks the true cost of interruptions (2014)
#6Similarly, if you are interrupted in the middle of a "solve" it may be difficult to jump back in - especially if the puzzle hasn't been created correctly and you are trying to "debug" which numbers conflict. Some puzzles are harder than others. At times you don't have a pen and paper so you have to keep a mental model of the whole puzzle in your head which makes an interruption that much more jarring.
Not a perfect analogy, but close enough to get me a 15 minute buffer at the end of the day and fewer knocks on the office door :D
Re: Programmers, teach non-geeks the true cost of interruptions (2014)
#7For me, programming only works when working from home and I'm alone.
Re: Programmers, teach non-geeks the true cost of interruptions (2014)
#8Actually, HN is more of a distraction to me than random people popping by.
Re: Programmers, teach non-geeks the true cost of interruptions (2014)
#9To add to this, there’s a lot of neurodiversity in the programming world. A lot of people have brilliant brains that just don’t work well with interaction. I had a discussion with other people on my team recently and realized I was the only extroverted person on the team. I think it’s also worth saying I personally think I’m one of the worst developers on the team but being able to context switch is unfairly rewarded…
Re: Programmers, teach non-geeks the true cost of interruptions (2014)
#10https://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt...