6 ms·
Tell it to my boss So tired of the distractions, non-value adding work, and context switching.
by giantg2 5y ago
Tell it to my boss
So tired of the distractions, non-value adding work, and context switching.
- deleted 5y ago[deleted]
- spacemadness 5y agoI’d tell it to your boss but they’d probably put multiple meetings on your calendar to discuss then give you a bunch of “action items” to fix the issue yourself. Sound about right?
- giantg2 5y agoOr fire me
- __MatrixMan__ 5y agoIf your manager reacts negatively to candid discussion of how they're preventing you from being productive, then you don't want that job anyway. Prolonged work under managers like that is what burns people out. Yeah switching jobs is a pain, but it's peanuts compared to switching careers.
- giantg2 5y agoI don't have a career, just a job. I need the income to support my family.
- elpakal 5y agoMaybe sharing some research from GitHub will help? https://github.blog/2021-05-25-octoverse-spotlight-good-day-project/ https://github.blog/2021-05-25-octoverse-spotlight-good-day-... > In our study, going from two to three meetings per day lowered the chances of developers making progress toward their goals from 74% to just 14%. And developers who average just one meeting per day have a 99% chance of knocking out high quality work — it really is about getting focus time and connecting with our colleagues to brainstorm ideas. > With minimal or no interruptions, developers had an 82% chance of having a good day, but when developers were interrupted the majority of the day, their chances of having a good day dropped to just 7%. By minimizing distractions and creating focus time, we not only get work done, we create better and less stressful days for ourselves.
- blooalien 5y agoIt's positively painful to try to get people to understand this incredibly simple concept for some reason. People just can't wrap their brains around the idea that this type of work requires focus, and that breaking that focus derails the whole activity for a period of time.
- dvtrn 5y ago”for some reason” Are they the ones having to do this kind of work? Probably not, right? At least in some cases? There’s at least part of the answer. Question in my mind becomes: how do we get the people who aren’t doing this work to understand and empathize with the productivity needs of those who are? I’m out of answers because everything that probably can be said about it HAS been said about it from people far smarter than I am-from blog post to published airport book to published academic studies-and yet here we are still having this conversation amongst ourselves as developers and engineers.
- MarkMarine 5y agoThe people distracting (PMs, Managers) are often the ones charged with getting the most out of the people being distracted, and honestly I don’t even think it’s their fault. They don’t see the work happen unless they are in a meeting where it’s done, and their schedule is mainly meetings so that is their impression of doing work.
- elpakal 5y agoI just don’t think it’s possible unless the people making the distractions have once been the people being distracted, and even more so there are people whose livelihoods depend on meetings happening (scrum masters for eg). Just IMHO there will always be friction between people who cant afford to be distracted and those that need to be distracted when people like this work together.
- __MatrixMan__ 5y agoMaybe we need to get rid of the managers and instead take turns being manager. I'll focus three days a week and manage one day a week. The other four members of my team do the same. The fifth day is for meetings, and if we don't need all day for that, it's for going outside.
- agumonkey 5y agoProgrammers trained to make everything as efficient as possible but managed by people working hard at the opposite.
- Smoosh 5y agoThe other irony is that those same managers will be pressuring the programmers to meet deadlines.
- serverholic 5y agoThe work is broken up by meetings and the meetings are broken up by work. Everything is so damn fractured it drives me crazy. If we are starting a new epic then we should spend a day or two figuring out what exactly what we're building, then go build it. Instead planning itself is fractured 1 hour here, 15 minutes there and it's hard to keep track of what the hell you're planning on doing.
- giantg2 5y agoYep that's basically why I'm slow. I got a bad rating and an effective 4.5% pay cut this year.
- tpoacher 5y agoA tiny thing, and I'm probably alone here, but one thing that absolutely wreaks havoc on my concentration is the simple act of 2FA for every little thing. Say I need to check an email relating to the code I'm working on. By the time I - open firefox - go to outlook - open keepass (because yes I care about security and delete cookies) - fill in my keepass master password - find the relevant entry from keepass - fill in my password via keepass - wait to be greeted by the authenticator message - grab my phone - use my pin to unlock phone - go to the authenticator app - use my pin to unlock the authenticator app - accept the authentication token for my email - confirm authentication via my phone's pin - search for the email I no longer even remember what I'm coding anymore, let alone what I needed that email for. This is particularly true if, like me, 2FA pisses you off, and your focus is replaced by rage.
- deleted 5y ago[deleted]
- darepublic 5y agoYes I basically prevent my computer from sleeping to minimize these 2fa interactions
- phonon 5y agoUse a yubikey plugged into your computer instead?
- tpoacher 5y agoIsn't that something my organisation needs to support before I can use it? (I don't think it does).
- Shared404 5y agoIt seems like the solution for this specific instance is to not use web mail. Is there a reason you're locked into outlook?
- tpoacher 5y ago
- jrockway 5y agoI suppose to some extent, work is more than just typing in code. As software engineers, we bring a lot of the distractions, non-value adding work, and context switching upon ourselves. One problem is that we get away with being specialists, leading to an organization full of specialist teams. That means to get anything done, high-overhead communication among the specialists is required. A specialist that understands the user tells you what features to work on, then you write some code and ask the security team for input, then you need to deploy this thing to production so require the help of the operations team. Finally, the testing team finds a bunch of bugs you missed, and now you have to go back and fix them. The alternative is to just do all those jobs yourself. That is what most 2-person startups do, and they can do a lot. I think this is just an anomaly in the job market. You try to hire "software engineer" and get 1% of the candidates you were hoping for, so you can't say "also you need to know security, operations, and testing". The result is a slowdown for everyone, as you staff up with specialists to support that one software engineer that actually applied for your job. (My strategy here is to know all these things myself, and teach them to my team, so we can be as self-sufficient as possible. But there's pushback; the time spent learning is time not spent getting through the bug backlog. And, why learn more skills when you get paid the same knowing only one? The market doesn't support the strategy of being a generalist, but it does support the strategy of having a lot of teams, and team leads to integrate them.) Ultimately, I think this is just a fundamental law of the universe. One person can do a one person project. Four people can do person twice as big. Eight people can do a project 3 times as big. I think this is just how society works, and it's not something that can be changed. Software engineers are "weird" in the sense that most of us are self-taught, so we have a very good handle on how much work one person can do; all of our projects were one-person projects until someone invited us to undertake a project that's 4 times as complex as that (and thus requiring 16 people). There is some debate as to whether this is exponential or quadratic, but the idea is the same; your value as an individual is much lower when you're working on a big project. At some bigger organizations, it's pretty much zero. So if you do more than zero work each day, you're ahead of the curve. (It of course takes 7 hours of meetings to determine what code you should write in the remaining hour. If you didn't do that one hour of code, then your output is actually 0, and you get fired.) None of this feels good, but it's just how the Universe and humans work, I think. Gravity pulls you down to earth, and needing to do a two person project means you have to talk to another person instead of programming. It's the law.