111–120 of 184 posts
The article isn't about exercising once or twice a day though. It's about you sitting around too much during the day. Not regularly being even minorly active, no?
Perhaps I'm mistaken but it seems like the people talking about their once or twice a day exercise arent on the same page as the article.
Earlier quoted context omitted.
> if your role is so demanding that you cannot hold a conversation (presuming a work conversation but also applies to social - up to a point obviously), then your either not very good at your job or your employer sets unrealistic expectations... Or they are a developer. Being interrupted while programming is really rough. It's like being an insomniac and having trouble falling asleep, when someone walks up and starts…
I don't know why people think devs are special in this regard. Being interrupted is a universal human problem, there is no need for an analogy for something that anyone who works in a professional (or hell even non professional) job experiences.
Earlier quoted context omitted.
It never ceases to amaze me how much others think they entitled to your time while working. They'll start conversations when all nonverbal signals show you are trying to get something done. Im at the point where I am going to be forced to be outright rude, which is not easy for me, just to be able to work undisturbed.
"Can we talk about this later? I need to get done by ." isn't rude (at least by my barbarian standards), and it would be very rude to ignore such a request.
My experience has been that, unless delivered in an exceptionally conciliatory manner (exaggeratedly, actually), this kind of request gets interpreted as rude by a lot of people. For me, at least, I think it comes from many people assuming they have a "quick question" or that their "small" request isn't difficult to fulfill.
Earlier quoted context omitted.
I don't know why people think devs are special in this regard. Being interrupted is a universal human problem, there is no need for an analogy for something that anyone who works in a professional (or hell even non professional) job experiences.
Are you a developer? I recall studies that say any interruption costs 30 minutes of productivity for developers. When you put it into cost terms, someone talking in an open office for 30 seconds can literally cost hundreds or thousands of dollars of productivity.
Even with programming it does matter what tasks you are working on. Many tasks don't need that much time to get into and out of it, only some do.
Earlier quoted context omitted.
Are you a developer? I recall studies that say any interruption costs 30 minutes of productivity for developers. When you put it into cost terms, someone talking in an open office for 30 seconds can literally cost hundreds or thousands of dollars of productivity.
I think that his point was that similar drop of productivity happen to other professions. Programming is not the only work that requires focus. Even with programming it does matter what tasks you are working on. Many tasks don't need that much time to get into and out of it, only some do.
Oh, I see. Yes, I would wholeheartedly agree with that. To his point, I would say many people on here don't necessarily think developers are special in that regard, but most people are developers and they are speaking on that which they know.
I'm a developer (obviously) and I couldn't intelligently speak on how interruptions would disrupt a soft skill profession such as marketing, sales or HR.
Earlier quoted context omitted.
I don't know why people think devs are special in this regard. Being interrupted is a universal human problem, there is no need for an analogy for something that anyone who works in a professional (or hell even non professional) job experiences.
Are you a developer? I recall studies that say any interruption costs 30 minutes of productivity for developers. When you put it into cost terms, someone talking in an open office for 30 seconds can literally cost hundreds or thousands of dollars of productivity.
And with all this complaining about interruptions and lost productivity, its really only the "sexy tech startups" that seem to have ping pong and foosball tables to waste time playing.
Earlier quoted context omitted.
It never ceases to amaze me how much others think they entitled to your time while working. They'll start conversations when all nonverbal signals show you are trying to get something done. Im at the point where I am going to be forced to be outright rude, which is not easy for me, just to be able to work undisturbed.
I moved office to the other side of the site, up some stairs an into a (admittedly vast) office with no windows in part because of this, people don't get programmers, your 5 minute non-important (to either of us) interruption costs me 15-20 minutes of lost productivity after you walk away from my desk. I have a phone on my desk that is set to flash, not ring and only then if it's the boss, everyone else just silently…
and they don't have a clue how destructive they are.
it's such a great example of clashing perspectives. they think they're being friendly and reasonable. the hapless and frustrated programmer thinks they're ignorant, lazy, and annoying.
Earlier quoted context omitted.
> if your role is so demanding that you cannot hold a conversation (presuming a work conversation but also applies to social - up to a point obviously), then your either not very good at your job or your employer sets unrealistic expectations... Or they are a developer. Being interrupted while programming is really rough. It's like being an insomniac and having trouble falling asleep, when someone walks up and starts…
I don't know why people think devs are special in this regard. Being interrupted is a universal human problem, there is no need for an analogy for something that anyone who works in a professional (or hell even non professional) job experiences.
If you're doing something simple, then it's just a matter of regaining focus. Sometimes devs are doing simple things and interruptions aren't such a big deal, but when we're deep into a debugging session or something it's more of a problem.
This is not to say devs are the only people who work on complicated problems like this, but plenty of non-technical people in software shops don't, and tend to not understand that interruptions are a real problem sometimes.
> Anyways, it’s not that complex to tackle this. A few changes in your habits should do the trick. This is complete garbage. The fact is, there is nothing you do to do 100% reverse the effects of sitting all day. You can maybe improve things by 20% or something like that. Progressive people keep hoping that you can use some kind of technology to change things but you can't. Standing desks don't do anything, standing…
It isn't the same as being a hunter gatherer in the forest, but I would hypothesize it does more than 20% to improve the situation.