this post was submitted on 24 Aug 2023
387 points (97.8% liked)
Asklemmy
44151 readers
1164 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm not (maybe an hour at most because I just started my job/training as software engineer), but long meetings are way more tiring than sitting there and coding. And coding while needing to listen to a meeting is even more exhausting.
Coding is something you can do for longer stretches as you get better at it. I struggle with 3 or 4 hours straight out of college. Now I run 7 hours no problem.
The dichotomy is that the more proficient you are at coding, the more meetings you need to be in to give engineering input... So the less time you spend coding. As a staff SWE I'm rarely able to get more than 3 or 4 hours straight to sit and code. Rather it's an hour here or there broken up my meetings.
I relish my no-meeting days to sit and actually get concepts out into code.
I'm spent at the end of 7 hours coding though. I've crunched to 14 before... But the code I wrote was shit for 5 of those hours.
My company started prioritizing developer time by heavily discouraging meetings with devs before noon, and one day a week is supposed to be meeting free. We also just don't respond to pings before noon now unless it's an absolute emergency. Took managers a bit to catch on, but my efficiency has honestly skyrocketed and I'm loving it.
Yeah we do no-meeting Thursdays.
Problem is when SLT decides they want a demo of progress and see all this "free time" called focus time on our calendars and stick a 30m meeting about 1 hr before lunch.
Mark it as busy in the calendar, that might keep them away. If marking the whole day is suspicious, make 1-2 hour marks with 10-20 minute gaps (or longer as long as it doesn't allow sticking a meeting in). Then make these "appointments" weekly and set the subjects(focus time) to private.
I'm not even allowed to work more than 10h a day so I'm not even able to crunch 14h except they are personal projects
It's vanishingly rare that I need to do that but if something breaks or an emergency happens I'm senior enough that I need to step up.
I get time off in recompense. Usually an entire day once the 14hr crisis has passed.
If my time would be better spent coding than being in the meeting I just decline. It depends on the culture of the org though if that kind of approach is ok or not.