| ▲ | tacostakohashi 5 hours ago |
| One reason is that there are a lot of people that refuse to do anything unless there is a meeting. I work with people that... * When faced with some well-written, succinct email/text explaining both a problem and supposed solution, will "respond" with "let's discuss this" instead of an intelligent response, taking action as proposed, or even mentioning any particular concerns to be discussed / researched ahead of the meeting. They just need it to be spoon fed to them, and need to be "heard", before anything can happen. * Will ignore requests to review PRs, or look into problems, for weeks on end. When I ask "what would be a good day next week to block off time to review this?", they'll suddenly spring into action, or say that a meeting is not necessary, but prove that in fact it is by refusing to do anything before the prospect of a meeting is raised. |
|
| ▲ | weitendorf an hour ago | parent | next [-] |
| Most people just have no practice or experience writing. Asking them to respond to or write a large response to an email is a total non-starter for them. That's the default culture in the corporate world unless you have a strong company culture otherwise. You know how popular grammarly and 2023-24 era chatgpt were? The prospect of writing an email actually makes most people quite anxious. They are not in the comments of hacker news, as a rule - they're watching YouTube and TV and don't read blogs. Just the way most people prefer to live. |
| |
| ▲ | devin an hour ago | parent | next [-] | | It blew my mind to enter college and peer review other people's papers. Up until that point I understood that there was a range of capability with writing, but I figured that in college courses the floor would be pushed up. I was dead wrong, and it was shocking to me that these folks had managed to get all the way through high school writing like 8th graders. ETA: This is over 20 years ago, btw. I hear it's gotten materially worse. That terrifies me. | | |
| ▲ | nradov an hour ago | parent [-] | | The TOEFL is a joke. Several years ago (before LLMs) I proofread group project papers for my wife's coursework at a large US state university. The sections written by foreign students were usually even worse than what I would expect from a native 8th grader. I assume they had found some way to cheat. |
| |
| ▲ | Uncle_Brumpus an hour ago | parent | prev | next [-] | | There is somebody that I am having to work with right now that will not respond to a single thing I ask unless it is on a live phone call. I will ask a relatively simple question via email, and then he will call me back an hour later and leave a voicemail just saying "Sorry I missed you, call me back" instead of even answering my simple question. I'm almost never at my desk, always running around out on the production floor (manufacturing engineer). I'll get his voicemail, call him back and leave HIM a voicemail re-iterating my question, and then I will also send an email again re-iterating my question. We will go back and forth like this until EVENTUALLY we catch each other at the right time, then it's a quick 2-minute call. It takes days and days, sometimes over a week, to get one single answer that takes 2 minutes to talk over. He is an external consultant I am working with, so I can't even just walk over to his desk. Absolutely infuriating. As soon as this project is done I am never asking him another question again, I'll find someone else. (I inherited the project and don't have the resources to find another consultant right now) | | | |
| ▲ | SamuelAdams an hour ago | parent | prev [-] | | It’s about to get a lot worse too. Gen Z has had noticeably worse reading comprehension scores over the last 5-10 years and they are starting to enter the workforce now. Many prefer video over text and firmly believe that written text is “the harder medium”. |
|
|
| ▲ | Fordec an hour ago | parent | prev | next [-] |
| Not advocating this, just more addressing the mindset on it, but in the game of office politics people don't mention concerns ahead of time because they don't want to give the opposing view point opportunity to research how to defeat their argument in a meeting, not that they "can't" give an intelligent response. They're choosing not to in their own self interest. "The enemy must not know where I intend to give battle; for if he does not know where I intend to give battle, he must be prepared in a great many places. And when he prepares in a great many places, those I have to fight in any one-given place will be but few." |
| |
| ▲ | 8note 8 minutes ago | parent | next [-] | | im unconvinced. id place the reason that its more work to identify and raise those concerns ahead of time, since if they are correct, you did all that work coming up with the happy path and the issues ahead of time, vs if the issues come up later, you can focus on and fix them as they come up. i dont think the meeting is in focus at all | |
| ▲ | onlyrealcuzzo an hour ago | parent | prev | next [-] | | You generally also get paid with ~10% of everyone else, regardless if you get 3x more done or 3x less done. So, if like most people, your working to live instead living to work - your employer is doing a terrible job incentivizing you to do more than the bare minimum. We all know you are far better off doing almost nothing and then all your time trying to get promoted for it, than trying to get promoted by actually doing a good job and thinking you'll get promoted based on merit. | |
| ▲ | sublinear 36 minutes ago | parent | prev [-] | | Anyone who would advocate for this strategy against any SME is a moron anyway. It's like watching someone who's expecting a knife fight walk in with a concealed handgun only to be immediately confronted with a tank. The email is usually an attempt to not waste time in the meeting and get shit done. Leadership always favors those who can make it so. Anyone who stalls for time or hides information will always look bad. I don't get why people so desperately try anyway. Most of these strange gambits in office politics are a losing game for the inept and inexperienced. One can only wonder why we keep pretending like there even is such a "game" of office politics. |
|
|
| ▲ | bunderbunder 5 hours ago | parent | prev | next [-] |
| I believe that some of this is differences in communication style. I like written communication because I don't process verbal communication as well. But I've also had plenty of colleagues who are more comfortable with verbal communication, and may not process prose as well. Many of them seemed hesitant to believe they'd fully understood something until they'd had a chance to talk through it to confirm. And, yes, needed verbal prompting in the same way that I tend to need written prompting. The most functional workplaces understand and respect these differences and make room for everyone's communication style. |
| |
| ▲ | soupfordummies 2 hours ago | parent | next [-] | | Yeah that's true to an extent. I've also had many occasions where someone asks for an update on x and I respond with a two line email asking a yes/no question and the person just says "let's hop on a quick call" etc. That's so frustrating because they're turning 30 seconds into 30 minutes. Not the person you're responding to but just needed to vent that. It's been happening a lot lately in my world | | |
| ▲ | pmg101 an hour ago | parent | next [-] | | Some people just don't have enough to do and setting up "quick chats" makes them feel busy. | | |
| ▲ | 8note 6 minutes ago | parent [-] | | ornthey think they have a lot of questions and think they will be less disruptive by having a call. You also didnt give them the response they wanted to hear, which is that you own the problem and they can tell somebody else that its being handled |
| |
| ▲ | dprkh 2 hours ago | parent | prev [-] | | I feel you. |
| |
| ▲ | tacostakohashi 4 hours ago | parent | prev [-] | | I am sympathetic to the "different communication style" line of reasoning, but I don't really buy it in the example I used / people I work with at present. As far as I'm concerned, responding to some well-prepared prose with "lets discuss this", is just a non-response, and a refusal to engage. If one wanted to have a useful discussion, but preferred something verbal, actually picking up the phone, or responding with something like "I'm curuous about X/Y/Z. Let's discuss this at 2pm, I'll send you an invitation", or "please find some time in my calendar for us to look at this." That would keep the matter progressing, and provide the opportunity to prepare for a useful discussion. "lets discuss this" is just saying "I need you to spoon-feed this to me, but I'm not going to make arrangements for that, so you'll need to figure out how to deal with that.". | | |
| ▲ | stiglitz 4 hours ago | parent | next [-] | | My theory is that it’s an intuitive rate limiting scheme devised to cope with the corporate fire hose. There’s no limit on the amount of text coming into an office worker’s inbox in a unit of time. But if one focuses on verbal communication, there’s always going to be a single stream. Personally, I don’t do this; instead I deal with the stress of the fire hose by grinding my teeth to stubs at night. And for the messages I don’t get to, instead of “let’s discuss”, the sender gets nothing at all. | |
| ▲ | macNchz 4 hours ago | parent | prev | next [-] | | My gut based on what you're describing is that there is some degree of "strategic neglect" happening here, where people the people doing this are effectively allowing the things being asked of them to self-prioritize: the proposals/emails/PRs/etc that get attention are the ones where the person who sent it follows up or schedules a meeting to discuss it, meaning they're likely higher priority than things where the person doesn't make that extra effort. This is a longstanding if exasperating strategy many people use, but I think it's getting more popular now that lobbing out a long proposal is easier than ever (because of AI). | | |
| ▲ | chneu 3 hours ago | parent [-] | | I've worked with a lot of people who will not engage with a request until the request has been made multiple times. Its a very lazy way of filtering. "It couldn't have been that important" is their logic. | | |
| ▲ | bunderbunder 3 hours ago | parent | next [-] | | I mentioned elsewhere that I was once coached to do this. In that situation it honestly wasn’t lazy at all. At the time I was fielding such a high load of incoming requests that even reading and responding to them was eating up a huge chunk of my time and preventing me from getting anything else (i.e., actually doing any of the requested work) done. I realize that this looked to the people requesting my attention like deliberate stonewalling. That’s because it was. And it wasn’t cool. But, “This quarter I didn’t ship any software because I was too busy answering email,” would not have earned me a satisfactory performance review. And I certainly was not going to openly admit to anyone but my immediate manager that I was using persistence as a prioritization signal. I saw what happened to the poor schmuck who made that mistake. | | |
| ▲ | SoftTalker an hour ago | parent [-] | | Are LLMs are going to neutralize this as a tactic? Or reinforce it? They will happily bombard you with text, and you can set up an agent to fire back. More text than ever will be transmitted, with less and less of it ever coming to the attention of a human. |
| |
| ▲ | infamouscow 3 hours ago | parent | prev [-] | | What I learned managing high performers is a disproportionate number of them had very hard childhoods and carry permanent scars that make this behavior destructive. These are the people that generally get ignored in every aspect of their life because their brain is operating much faster than the rest of society and get mistaken for being insane in every facet of their life. So when they experience this kind of behavior in an environment that's supposed to reward them for their ideas, it's stultifying. Those high performers are not going to continue putting effort and energy into novel ideas if they're being ignored. The solution is pretty simple: just fire the manager. |
|
| |
| ▲ | bunderbunder 4 hours ago | parent | prev | next [-] | | Totally fair. I don’t know your actual situation and I also find these kinds of interactions to be infinitely frustrating. But it took me a long time to realize there can be a sort of “double empathy” problem across communication styles that makes it difficult for people to accurately infer each other’s intent. They might even be operating from two slightly etiquette norms, such that the same behavior is considered polite by one person and dismissive or hostile by the other. Not saying that’s your particular situation, just talking generalities since that’s all I reasonably can speak to on a pseudonymous forum like this. | |
| ▲ | ozgung 4 hours ago | parent | prev [-] | | This is similar to me asking some basic questions to the LLM instead of reading the text it wants me to read and review. The difference is that it’s a robot and you’re not. |
|
|
|
| ▲ | Jcampuzano2 4 hours ago | parent | prev | next [-] |
| Not gonna lie, I've had the PR issue before. The solution? Blast the PR into your shared slack noting that it isn't being reviewed on time because maybe XYZ person is busy. Watch how fast they are suddenly free to review when their name is attached to something in public. The real solution is to simply fire these people. There is no good excuse for ignoring requests repeatedly besides laziness or self importance. |
| |
| ▲ | starky 4 hours ago | parent | next [-] | | >There is no good excuse for ignoring requests repeatedly besides laziness or self importance. Not necessarily, there are also plenty of cases where a person's KPIs don't match their responsibilities or the actual needs of the team. This is frequently a management problem where resources haven't been properly assigned and the employee will always prioritize what they are evaluated on to minimize friction. Far too often managers collect responsibilities for their team (or are told to take on something), yet have zero plans other than "it will work itself out" and they don't bother to formalize how the requests will be dealt with. There are certainly a lot of people out there that refuse to do their jobs, but it is common enough that there is something else wrong that a discussion with the manager about where the process is failing is the first step. | |
| ▲ | dpark 4 hours ago | parent | prev | next [-] | | It’s not necessarily laziness. They just don’t care about your request. “This thing you’re asking for is not important compared to the other things I need do.” I used to run build call and this was the bane of my existence. People who just never engage (but pretend they are to get you to go away). | | | |
| ▲ | nradov an hour ago | parent | prev | next [-] | | Dogbert: "I can only please one person per day. Today is not your day. Tomorrow isn't looking good, either." | |
| ▲ | locknitpicker 4 hours ago | parent | prev [-] | | > The real solution is to simply fire these people. I don't think that firing people is an intelligent solution to a problem that boils down to your personal inconvenience. If you posted a PR and it's awaiting review, it is no longer your problem. You are literally blocked by others. Who knows what they are dealing with? Perhaps they have higher priority items than reviewing your work? I mean, would you stop making this complain after they review your 3rd or 30th PR? Everyone around you also has work to do. If PR reviews are slow, escalate the issue with your manager. | | |
| ▲ | Jcampuzano2 4 hours ago | parent | next [-] | | This is why I said "repeatedly" i.e. a pattern has already emerged. And in most companies I've worked at you are the one being held responsible for a PR/feature not being merged or finished on time - at least in my experience. You're often working on a different team from the people doing reviews, so in a large enough company they are just a faceless/nameless person from the perspective of your PM. | | |
| ▲ | locknitpicker 2 hours ago | parent [-] | | > And in most companies I've worked at you are the one being held responsible for a PR/feature not being merged or finished on time - at least in my experience. L You are responsible for delivering tasks, but if you are blocked by the process then it's not you who is preventing the task from being delivered. Whether it's the scrum master or sdm or project manager, someone else is responsible for keeping the tasks moving. Once you mark a task as pending review, you are blocked. From that point onward all you have to do is raise awareness of reviewers to the task pending review, and raise visibility with stakeholders that your deliverable is being blocked by the review. As long as you don't slack in raising awareness, it's not your problem anymore. | | |
| ▲ | tdhz77 2 hours ago | parent [-] | | Crazy solution to fire people. Found a toxic person in waiting. |
|
| |
| ▲ | dpark 4 hours ago | parent | prev [-] | | > it is no longer your problem This is absolutely not true. If I can’t check in a fix or a feature because someone else isn’t doing the review, it’s definitely still my problem. | | |
| ▲ | locknitpicker 3 hours ago | parent [-] | | > This is absolutely not true. If I can’t check in a fix or a feature because someone else isn’t doing the review, it’s definitely still my problem It isn't. It's your scrum master's/Manager's problem, because the ticket is blocked in review. In the meantime you moved on to another task. Because the review is not your problem. | | |
| ▲ | dpark 3 hours ago | parent [-] | | If I told my manager it was his problem to get my code reviewed, he would tell me to do my job. Offloading responsibility for getting code through review to a manager or scrum master sounds at least as dysfunctional as people avoiding doing the reviews. | | |
| ▲ | locknitpicker 2 hours ago | parent | next [-] | | > If I told my manager it was his problem to get my code reviewed, he would tell me to do my job. If that's how you interact with your team members, no wonder they refuse working with you. What any competent developer does is a) update ticket to move it to review, b) call out the PR in whatever system you guys use, c) after a reasonable amount or time inform your scrum master/manager that your task is code-complete and is blocked by the review, d) update ticket with a notice that PR is still pending review. Go back to step b) and repeat until the PR is merged. Done. Updating the ticket and making a best effort to get the ticket moving is all that's expected from you. By design. That's how things are supposed to work. If your manager doesn't care, it's nothing they want to push anyway, as proven by the ticket history. | | |
| ▲ | dpark an hour ago | parent [-] | | > no wonder they refuse working with you. Weird and abrasive assumption you make. > Updating the ticket and making a best effort to get the ticket moving is all that's expected from you. I have never worked somewhere that ran things as you describe. But then everywhere I’ve ever worked has expected a high level of personal responsibility, not “best effort” that consists of a one time Slack
message and tagging work as blocked. |
| |
| ▲ | watwut 41 minutes ago | parent | prev [-] | | It is managers responsibility to set priorities including those of other team members. Including priorities of code review. That is not offloading. It is also considerably less toxic then "I demand people to be fired because my code review was not done in 12 hours". Your PR is not the importantest thing being worked on. | | |
| ▲ | dpark 31 minutes ago | parent [-] | | I didn’t say anything about firing people. What I said is it’s not my manager’s job to wrangle people to do code reviews for me. It’s absurd that the immediate response to friction is to offload it to someone else. Certainly if there is a cultural problem, or misaligned priorities, discuss the general issue with your manager. But “I set the ticket to blocked so I’m done” is not an acceptable process anywhere I’ve ever worked. Much of the time the person I’m waiting on doesn’t report to my manager anyway. My manager can’t change their priorities any more than I can. | | |
| ▲ | radiator 21 minutes ago | parent [-] | | > Much of the time the person I’m waiting on doesn’t report to my manager anyway But there exists a manager who is the nearest common ancestor of your and their manager. |
|
|
|
|
|
|
|
|
| ▲ | zabriel_goss 5 hours ago | parent | prev | next [-] |
| I can see where this can be abused. (The PR review example is pretty rough!) I can also see where it's a strategy for triaging which tasks are a priority. I've had projects presented to me over email that sounded great and seemed like they would have good traction, but then fizzled out once I asked if we could discuss it further in person. Blocking off face-to-face time is a signal that the work is important enough to get done. |
| |
| ▲ | bunderbunder 4 hours ago | parent | next [-] | | I’ve even been explicitly coached to use this strategy as a sort of pre-triage. Because when you’re truly swamped with incoming requests even prioritizing starts to eat up a lot of time. | | |
| ▲ | hxugufjfjf 2 hours ago | parent [-] | | Me too. I used to be super dilligent about immediately responding to emails, requests, meeting invites and I never once benefited from doing so. I only trained my peers into learning that I was a "yes man" that always responded quickly, and they abused this. Therefore, I now no longer rush at all responding to emails unless its actually urgent and concrete. If someone sends vague requests, I just don't ansewr. If they don't come back, I can infer it probably wasn't that important or they found some resolution on their own. I also never respond to meeting invites just in case I can avoid the meeting. I think I've probably dodged 100 unnecessary meetings over the last couple of years by literally just never responding or showing up. I of course don't do this with 1-1 meetings, but meetings with: multiple people where I'm not needed, there is no listed agenda, and my involvement is not clear; F that. I also frequently just say "no, I can't", which I didn't for most of my carreer, and just suddenly realized I could do largely without consequences or repercussions. It's fascinating. |
| |
| ▲ | locknitpicker 4 hours ago | parent | prev [-] | | > Blocking off face-to-face time is a signal that the work is important enough to get done. This. I'd also add that not bothering to book a meeting means that people treat you like a low-value work queue that they use to dump low-visibility and low-accountability work. They invoke you to handle silly tasks that no one but you accept. By requiring a meeting, you're increasing the threshold of effort that your requester is willing to invest in getting it done. If they can't be bothered doing a meeting, you shouldn't bother doing the work for them. |
|
|
| ▲ | 8note 10 minutes ago | parent | prev | next [-] |
| this is to say that alignment and prioritization arent the same thing. they agree to the thing, but making a meeting moves the priority from low to high because you are signalling through making a meeting that it is high priority |
|
| ▲ | Nevermark an hour ago | parent | prev | next [-] |
| With any request, schedule a follow up meeting to discuss the completed work, or to perform an autopsy if there was some impediment. Make sure to actually say “autopsy”. “Inquisition”, “colonoscopy” or “employment review” all work well too. If you have two Bob’s definitely get them involved. Then have a practice of letting such meetings be cancelled if the work is done and went well. This can be done as a consistent and transparent inside joke. Humor often generates the social permission to communicate hard truths, by also providing psychological stress dispertion. I cannot vouch for any of this, but please share your experiences. |
| |
|
| ▲ | nitwit005 22 minutes ago | parent | prev | next [-] |
| In this second case, some people live life only bothering to deal with crises, and delay anything else. It's likely not the direct threat of a meeting, but that you've made it clear it's a crisis. |
|
| ▲ | aspir 4 hours ago | parent | prev | next [-] |
| 100% agree. Most of the time, when I hear "this could have been an email," it's from someone with a track record of not reading (or writing and responding to) emails meaningfully. |
| |
| ▲ | tacostakohashi 4 hours ago | parent | next [-] | | Totally... I've been through this cycle more times than I'd care to count: "What would be a good day next week to block off time to review this?" "We don't need a meeting for this, I can get to it <whenever>" "That's an excellent point, and I tend to agree. Nevertheless, this has been hanging out there for several weeks now. We can schedule the meeting now, and if it ends up getting done before then, it can be canceled.". | |
| ▲ | giantrobot 4 hours ago | parent | prev [-] | | I think not reading or responding to e-mails is largely (from my experience) indicative of more fundamental communication problems in the company/group. The first problem is e-mail fatigue. Many groups have ridiculous amounts of automated e-mails that amount to line noise. The information in them is rarely actionable and certainly never so critical it needs to be read by everyone immediately. "Everything is OK" alarms are fucking infuriating. It's very easy to miss the super highly critical e-mail from a manager that's just a lazily forwarded e-mail from the automated systems. The "Have you seen this?" with the entire contents of the line noise e-mail from the automated system. Second is people, especially middle management, that for some reason assume e-mail is a real-time communication medium. They send an e-mail and expect the recipients to drop everything to respond to it. Simultaneously the people actually doing work are actually working and not checking their e-mail every nanosecond to see if they need to drop their actual work to explain their actual work to management. So then the middle management sends a cascade of instant messages and schedules meetings to get the people doing actual work to drop everything to explain their actual work. These meetings will inevitably contain complaints about not getting work done. It's now even worse with AI in the middle. Instead of using LLMs to write easy to scan and digest bullet point e-mails they're used to expand bullet points into useless novellas. My solutions to these problems are thus: 1. RSS - Automated systems should just emit RSS feeds with their normal status with separate feeds for exceptional conditions. Only in those actual "machine on fire" conditions are e-mails sent by such systems. Parties interested in constant updates just watch their feed reader and everyone has a single source of truth for event logs from the automated systems. 2. Automated systems should just file tickets automatically so everyone involved has a single source of truth and can all collaborate in one place. Even better if the ticket/bug tracker supports RSS because it becomes dead simple for anyone to follow feeds they're interested in and even set up system notifications for new issues. 3. Company/group wide e-mail policies that constantly remind everyone it's not a real-time medium and that filling everyone's inbox with noise is not effective communication. This can be enforced with automated delivery delays guaranteeing e-mail won't be immediately delivered as a safeguard against people using it instead of actual real-time channels. 4. Verbose e-mails are also rarely effective communication and shared LLM prompts that make e-mails shorter and clearer would also help. Removing most of the noise from e-mail makes it more effective and can make it an actual communication medium. If e-mail becomes effective communication far less of everyone's limited lives needs to be spent zoning out in meetings where their only purpose is to "give a status update". Back in the days of paper memos the literal cost and effort required to send them required the sender to really think about what they were trying to communicate and how to say it best. Because e-mail is essentially free it is widely abused since so little thought needs to go into its composition and delivery. |
|
|
| ▲ | DenisM 4 hours ago | parent | prev | next [-] |
| How you asked them why? It could be more productive than being angry. Or not, but worth a try. |
|
| ▲ | pmg101 an hour ago | parent | prev | next [-] |
| I have this even on slack. I prefer text because it gives me time to thi k before responding but I think some people just don't have very good reading comprehension. Or writing skills. So they force everything to "let's set up a chat about this". |
|
| ▲ | malux85 5 hours ago | parent | prev | next [-] |
| They sound like poorly run companies, management should be aware and dealing with both of these problems. |
| |
| ▲ | tacostakohashi 4 hours ago | parent [-] | | They're annoying companies to work at, yes. They're also highly profitable, so it's difficult to make the case that they're poorly run. | | |
| ▲ | usefulcat 4 hours ago | parent | next [-] | | A highly profitable company can be poorly run and still survive exactly because there is so much more margin for error than for a company which is barely profitable (or worse). Granted, that kind of situation is unlikely to continue indefinitely, but it certainly can happen. | |
| ▲ | jaggederest 4 hours ago | parent | prev | next [-] | | Profitable companies are often very, very poorly run. The best run companies, in an absolute sense, are ones that are extremely close to breakeven on margin and thus have to shave every penny - my prototype for this would be Costco, for example. Companies in industries where you can print money (for a while...) usually haven't actually been put under any duress, so any fool can manage them and look like a genius. It's in hard times that you discover whether you're a good manager or not, when the decisions made in good times come home to roost. | |
| ▲ | malux85 3 hours ago | parent | prev [-] | | If you reduce a companies purpose to solely being "making money" then by that definition sure. But in my opinion the worship of money and reduction of everything to being solely a dollar maximizer is one of the biggest problems that humanity has at the moment - it is a reduction in purpose by the blind and greedy. My definition of a well run company is one that is still profitable, but has happy employees who are maximizing their potential and growth. Who is a good tax paying entity so that it contributes back to the society that is supporting it. Is making a healthy return for its shareholders despite all of this, and is not doing anything evil like producing toxic chemicals, harming vulnerable people or polluting the environment. Is it idealistic? Yes of course it is. Our collective description of greatness should be to aim at perfection so that even falling short of it is still excellent. Saying it must be well run because its profitable makes me sick, because that line of thinking feeds unrestrained greed, and is exactly the reason our state of capitalism is so unbalanced and full of greed right now. |
|
|
|
| ▲ | AnimalMuppet 3 hours ago | parent | prev | next [-] |
| Email chains can fail to converge. Yeah, the meeting could have been an email, but what if it was going to be 20 email back-and-forths? And not everybody is responding quickly? You ask three people what we should do about a problem. They float ideas. You think the discussion is converging on a solution, and then one of them (who hasn't been heard from for the last three days) suddenly protests where the group is going, saying that they don't agree at all, that they have several concerns, that nobody talked to this other group that needs to be consulted, and so on. Then for that other group, nobody responds for a week because they're busy on something else. A meeting can force people to say what they have to say, now, or be ignored. That forcing function has value. And it's not (just) that "people refuse to do anything". It's that multiple people, doing things asynchronously, on different time rhythms, sometimes means that the group consensus advances v e r y s l o w l y, if at all. |
|
| ▲ | tamimio 4 hours ago | parent | prev | next [-] |
| > * When faced with some well-written, succinct email/text explaining both a problem and supposed solution, will "respond" with "let's discuss this" instead of an intelligent response, taking action as proposed, or even mentioning any particular concerns to be discussed / researched ahead of the meeting. They just need it to be spoon fed to them, and need to be "heard", before anything can happen. You hit the nail on this, a lot coming from middle managers too who still think that a busy calendar of these meetings it means they are very productive. I remember a manager I worked with, he was so keen on having meetings, a discussion between me and a colleague and he overheard it? Meeting to discuss “the conflict”!! It was soul crushing experience thankfully i left quickly, only to know later he started having meetings for meetings, so in those meetings they discuss what they will discuss on the other meetings! Also, there are some other sinister reasons, an email is an artifact that can be traced and searched, a meeting usually is just verbal communication and even meeting minutes get challenged later. |
|
| ▲ | dreamcompiler 5 hours ago | parent | prev [-] |
| I've faced this same PR problem. Something is very wrong with a software development process when one developer can halt forward progress on the repo by simply ignoring PRs. One solution I've thought about is to automatically accept any PR that sits idle for 48 hours without comments or modification. After that, the reviewers lose the right to complain. If some nasty bug is later discovered, that's what git bisect is for. |
| |
| ▲ | radiator 4 minutes ago | parent [-] | | An innovative approach. And by submitting a PR on Friday afternoon, you might get a free hand to do anything you like! |
|