The piece was a good read but its so personal to me that it doesn't really help sadly.
The piece was a good read but its so personal to me that it doesn't really help sadly.
The most successful advice I’ve found is to find a way to reset after meetings without using your computer. For whatever reason, they’re emotionally drained after meetings. They get back to their computer and reach for Reddit or Twitter or something for a low effort snack, which then spirals into an hour or more of doomscrolling or distractions. This then translates into self disappointment at their low productivity, which further drives them to seek more cheap online entertainment and the cycle repeats.
So try something else. After your standup, go for a walk. Don’t use your phone. Do some stretches if you WFH or have a quiet place. Whatever you do, don’t fall into the rut that destroys your productivity.
- taking breaks
- thinking through a problem
Regardless I would never allow myself to browse anything not work related when I'm actually working (i.e. twitter, reddit) even when I'm "destroyed". I think cutting the unproductive crap out completely when working and trying to find more healthy coping mechanisms is far better.
I've had this problem too. But now that I have more meetings, it's become much easier to transition back to focused work. It's only the occasional more-stressful-than-usual meeting that eats up my attention for hours afterwards.
I don't know what the solution is for most people. I guess this is why some people who transition manager --> IC can be so effective.
- Everything destroys my flow anyway. So $#&#$% fragile.
- Standups are 100x less destructive to my flow than random unscheduled synchronous communication.
- For management and collaboration purposes, I recognize the need for some kind of synchronous communication for most projects/jobs.
- When working remotely I've found video standups help keep me feeling connected to humanity.
- Most teams I've been on are quite understanding if you choose to miss standup and offer an update via Slack instead because you're "in the zone."
So.... they suck, but they have upsides for me, and I accept them as kind of a "least-bad compromise solution."
It’s still better to state your problem. I like to use the “non-violent communication” as a template. Something like, “When we have the standup, I have a hard time refocusing on work afterwards. I’m concerned about the impact this has on my productivity. Can I send status updates via Slack?”
I’m not gonna pretend that this is a solution to your problem; I just want to sympathize and have a conversation about some of the strategies that we can use to fix problems with management that interfere with technical work.
Don't worry about it. I think this is good advice for any software engineer. Eventually you'll be senior enough or on a different team and it won't be a problem.
For nearly all working relationships, I think it's reasonable to keep an emergency communication channel open.
Hopefully it doesn't sound too combative, but I wanted to express that it's a two way street and compromises have to be found. I dislike various things in my company on a personal level, but often make sense from company/team point of view.
Thanks.
Beyond that I refuse to do daily standups. I'll quit a company if they won't let me do async or communicate through slack. I'm not logging in and the start of my day being a meeting every single day. Absolutely not. I've been there before.
At two companies the actual CEO and CTO were in every single one of our standups (startups of course).
But I know good engineers (who are also good communicators) that loathe them with a great passion.
I didn't say a single thing about paired programming. Christ. Did I say that the dev wanted to pair program? No, I didn't. I would have happily hopped in a huddle with him as OPPOSED to scheduling a meeting 3 days later.
I am sick of meetings and people who are incapable of working async, especially when we're in different timezones, which is exactly what this thread I'm responding to is about.
this sounds like pair programming imo.
> Great, now instead of being able to respond while working on other things I have to cut out an entire hour of my day just for you.
this reads as a bad attitude towards mentorship. sorry for that assumption.
My frustration is not knocking this out over 10 slack messages right now and having to round back to it days later. I want it done and off my plate.
I'm ADHD. I don't want lingering tasks floating around giving me anxiety when they can be done quickly. I'm going to forget it exists until 10 minutes before when it pops up on my notifications, then I'll have to context switch over to that situation.
One of my biggest coping mechanisms is as soon as something pops into my mind I do it RIGHT NOW. If I walk by the laundry basket and think of doing laundry I grab it and do it RIGHT now. Or I'll just walk by it for a week completely oblivious to it.
I'd much rather just get an interruption out of the
blue than have someone schedule a meeting to talk to me
After 15+ years of exploring my own ADHD and learning about others' experiences, I'm still constantly wowed by how differently we all react to this stuff.For me, out-of-the-blue interruptions are a worst case scenario for my ADHD. It's very hard for me to get into the "flow" if I know that I might be interrupted at any moment. I prefer scheduled meetings as a less-evil alternative.
But many many feel similarly to you.
Also, somewhat contraintuitively, I often avoid starting some new work e. g. 30 minutes before a scheduled meeting, meanwhile without it I just start, and if interruption happens,... it just happens.
Also, somewhat contraintuitively, I often avoid
starting some new work e. g. 30 minutes before a
scheduled meeting
No, I think that makes sense and is pretty common.It's hard for me to get into the zone if I know I've got a hard stop in 30 minutes.
Two workarounds for me. One is that I tell myself I'll spend the final 5 minutes jotting down todo's so I can pick back up relatively close to where I left off. I normally work in 20-30 min bursts anyway. This is actually not super successful for me but better than nothing.
Slightly more effective for me is using those 30 minutes to bang out some smaller tasks. Review a small pull request. Pay a bill or two. Apply some software updates. Gotta be done eventually so I get them out of the way now, in service of more focus time later.