At a job I had they wanted me to install an instant messaging app on my compute! I refused point blank. I said they could email me and I'd look at he email every so often. If it was really important they could get up and walk to see me. If it wasn't important enough for others to walk then it definitely wasn't important enough to interrupt me. Before that I was at a place where they had tannoys. I moved the tannoys a…
"Instant messaging" is just as disruptive as email if you have notifications turned on. There is zero difference between your email program going ding ding ding on every incoming email vs slack/teams/whatever doing the same. My current company has _all_ of their communication on Slack, the only emails I get are meeting invitations and status emails from automated systems that haven't been integrated to Slack yet. I c…
Programmer interrupted: The cost of interruption and context switching (2022)
211–220 of 271 posts
Re: Programmer interrupted: The cost of interruption and context switching (2022)
#212Re: Programmer interrupted: The cost of interruption and context switching (2022)
#213Earlier quoted context omitted.
The cause of all this is the grafted on management caste, that does not code. For them the whole endavour suspicously looks like not doing a thing, for to do a thing, there needs to be communication, information flowing up and down the hierarchy. Not some dude sitting there like a zen monk, reading, ocassionally typing. Slackers! Best load there calendars, to get them going..
I'd say the cause of this is the developers can't explain themselves, cannot defend why they need isolation, why they should not be interrupted, and more often than not can't explain what they do, what their jobs are and why they are required, in an understandable manner to the management caste. They act as they do because the developers are an opaque pool who talk nonsense when asked questions. Of course they/we get…
Lets say it that way, such a mindset ought to be valuable to the extreme. Thats why we see a constant stream of meddle-managers, setting out to make compliance and "apply presure" startups. Its definatly at the core of value generation.
ChatGPT: Ask me on the hour, every hour for my status and remind me of the deadline..
Re: Programmer interrupted: The cost of interruption and context switching (2022)
#214Earlier quoted context omitted.
And then you're finally fed up with all this and go full remote, if the company allows it. Congrats, now you lost access to 80% of what is going on and fell out of the loop for anything important, and you're now guaranteed to lose in any power struggle that could happen. In one of the companies I worked for, it was comfortable in the beginning - there were offices, 2-3 programmers in each, not too crowded, but close…
A modern version of the Panopticon, so to say: https://en.wikipedia.org/wiki/Panopticon
https://99percentinvisible.org/episode/the-panopticon-effect...
Re: Programmer interrupted: The cost of interruption and context switching (2022)
#215Earlier quoted context omitted.
> no slack, no zooms, no one tapping your shoulder, no conversations about the weekend distracting you on the periphery My teen jobs were in stores, restaurants, and manufacturing. In those contexts, everybody understands that when you're working, you're actually working. Even managers understand that even small discussions need to be fit neatly into the flow of the work, and actual meetings require careful planning…
Similar raising. At one point I was ASE certified, at another I was a landscaper. The first thing I noticed about white collar work was how gossipy and lazy everyone was. We didn't have time for that in blue collar work. I had no idea how these people were useful to work or society. It seems so bizarre to me, even today, that most white collar jobs make more money. It's like they took the people who couldn't work phy…
Re: Programmer interrupted: The cost of interruption and context switching (2022)
#216Sadly, the cost of context switching is well-known, and has been proven, over and over again, for decades. But managers don't care (and many co-workers also). A quick shufti at most modern open-plan offices, shows the contempt that managers have for developer context. They know better, and have made the conscious decision to go open, anyway. I remember visiting the Facebook/Instagram building, in NYC, and was aghast…
>But managers don't care (and many co-workers also). i bet 99% of time people are interrupting themselves. Like i just did to browse HN.
I interrupt myself when I'm in the flow absolutely never!
Re: Programmer interrupted: The cost of interruption and context switching (2022)
#217I actively like being distracted when I'm programming. I tend to approach a problem from lots of different directions, each time fizzling out, hitting a block or having some sort of mental reset, until something unconsciously clicks and an overall structure, understanding or solution emerges. Continually leaving and returning to the problem is a part of that process, so I tend to find someone walking up with a questi…
Indeed, this seems unusual in programmer land. As evidence we have a thread like the current one reaching the front page several times a day. But your way is also my way. I am active in a very wide array of topics, and happy to flit between them. Sometimes I dive deep, but it's usually in a critical moment of synthesis when ideas developed over months or years come to clarity and I put them to action. This is working…
I think this may be a variation on the "same" thing. For me, I only look at code or the UI output, or the requirements, or a database query at any one time.
But... I really like if the code is always in the same place, and the output is always in the same place, and I can just look between them if I'm thinking about how and why the code is resulting in the thing it is. But I know where each of those things is at any time, and it might only be a glance away, or an alt-tab away.
(For me, it's 2 27" QHD monitors rather than one big or small monitor.)
Re: Programmer interrupted: The cost of interruption and context switching (2022)
#218Not that I like to be interrupted, but if it’s inevitable, here is my method. I’m using it when interruptions are planned, when a task is complex by itself, at refactorings and on bad/lazy days. Log all your key thoughts, realizations, decisions and taken steps on paper. It shouldn’t be long or long-term clear, only clear to today’s you. Gibberish to a bystander. Text, bullets, arrows, acronyms, verbs, marks, anythin…
My mental state isn’t easily capturable on paper since I use visual/spartial memory for programming. Witting it down requires enormous amounts of translation.
Re: Programmer interrupted: The cost of interruption and context switching (2022)
#219Earlier quoted context omitted.
I feel that this is extremely dismissive of the reality that other people do in fact have similar focus requirements, but simply have learned to take notes or otherwise deal with interruptions. There are more demand driven roles but probably every person you interface with on a day to day basis professionally has hard work to do. Sales copy? Focus. Figuring out some accounting discrepancy? Focus. Trying to actually p…
I feel in turn that this comment is the dismissive one, and in fact extremely so. The issue is not that programmers need to focus, is that they need to focus on deep, complex work. At least a few of those other tasks you mention (don’t have much experience with sales copy, and in rather terrible with both sales and copy) do require focus but have smaller reasonable increments of progress. Stop thinking about the work…
Re: Programmer interrupted: The cost of interruption and context switching (2022)
#220Earlier quoted context omitted.
> And sure, why don't you put me next to the salespeople making calls all day. I’ve worked next to people with zero volume control and who like to take calls on speakerphone. I decided there and then that cubicles has material benefits over open offices.
I'm old enough that I remember a time when developers had offices... sometimes private, sometimes 2 to a large office, but usually shared with other developers who generally also understood the benefit of not being interrupted so it worked out fine. Young me's head would explode if I got a glimpse into a future where cubicles are now looked at as the good old days. And the progression keeps going with a lot of compan…