13 ms·
Debate over 'fake work' and 'lazy management' in tech industry
- harimau777 3y agoWhy do we expect to have good managers when we promote based on technical competency rather than leadership ability? Sure, a certain basic level of technical competency is needed, but after that management and development require different skills.
- deleted 3y ago[deleted]
- onlyrealcuzzo 3y agoDo we? I was under the impression that we promote based on who games the promotion system best.
- SpicyLemonZest 3y agoIt’s easy to over-focus on gaming the promotion system because that’s the part that’s under your control. If someone comes to ask me for advice on how to get promoted, I can’t exactly say “try being smarter and delivering results faster”, even though those factors have a lot more impact than micro-optimizing the promotion review committees.
- deleted 3y ago[deleted]
- i_k_k 3y agoAnother problem is that much of the industry sees getting into management as a promotion. This is something that Microsoft tried, at least, to get right: pay/rank was mostly divorced from job function.
- kevinventullo 3y agoFacebook and Google also have parallel tracks up to very senior levels.
- disgruntledphd2 3y agoI mean yeah, theoretically. It's nonsense though. Just count the number of individual contributors vs managers at a director level and it quickly becomes apparent that one of the parallel tracks is much, much larger than the other.
- lupire 3y agoNot entirely fair, because most of those low/mid managers are active developers too. What's stranger is that managers write more code than high level (not line level) "org tech leads" who sit in meetings all day.
- disgruntledphd2 3y ago> Not entirely fair, because most of those low/mid managers are active developers too. I dunno, certainly at IC5 (so I think IC4 now) level at FB, my manager was totally judged on the output of her team, and strongly discouraged from working on her own projects. Meanwhile, at the same level as an IC, I was working on my own projects but mostly helping others accomplish theirs.
- Sohcahtoa82 3y agoI'm finding many companies are learning that technical ability and leadership ability are entirely different functions. I consider myself highly technically competent, but if you asked me to lead a team, delegate, etc., I would crash and burn. I just don't have the interpersonal and communication skills to set expectations. Could I learn those skills? Oh, certainly. But why? The work doesn't interest me. The more I'd go up the management chain, the more I'd get disconnected from the technical work that I actually find interesting, and my day is spent in bullshit meetings where we'd rehash the same bullshit plans on a weekly basis.
- watwut 3y agoI did not seen all that much promotions based on technical competency. We promote based on impressions of upper management that have zero to do with technical competency and zero to do with leadership ability. Also, pretty much all non technical lower level managers were disaster. And issue was not just their lack of tech knowledge in pure form, but their insecurity, inferiority complexes and what not everybody else had to deal with. And profound not understanding of culture around tech just lead to completely unnecessary misunderstanding. Lack of technical knowledge in the context of managing technical people imply that you will fail in social aspect too.
- bensonperry 3y agoagree, but agree with another reply that it doesn't even seem like technical competency is the skill used outside of potentially engineering. feels like optimizing for "managing up" (which is code for "making people above you happy" and doesn't necessarily correlate with delivering any type of value) is what these managers do. in other R&D roles (design, product) most managers i've met aren't actually gifted at executing in an IC context
- screye 3y agoFirst, it's ego. Engineers are a deeply opinionated species that will not heed the advice of a man they deem to be inferior to them in technical ability. Technical competency based promotion is about managing hubris and egos. For the second, I have a hot-take: "All problems in tech are work estimation problems." And so too is who gets to be manager. Nothing annoys an engineer more than a manager who estimates arbitrary times to tasks. Similarly, nothing annoys a manager than being unable to establish accountability for work effectiveness of an employee. So non-technical managers set up metrics (LOC, Hours worked, tickets moved) for accountability. Average Metrics are bad and bad metrics are disastrous. Metrics are exploited by the politically savvy, set up micromanagement structures and discourage those who are actually well aligned with product success. A good engineer makes work-estimation easier, avoiding the need for some of these toxic structures.
- lupire 3y agoWork estimation isn't very important. Priority estimation and value estimation are very important. What matters is finding the 10x to 1000x value thing to build, and putting resources (usually many people) building it. It doesn't matter how long it takes, as long as it's something people need and can afford and you are able to build it.
- say_it_as_it_is 3y agoThere are a lot of managers who haven't done any of the work that their reports do, and those that do have field experience but not even expertise.
- krickkrack 3y ago[flagged]
- petermcneeley 3y agoYou can live your dream now https://news.ycombinator.com/classic https://news.ycombinator.com/classic Also note as you suggest the article in question does not appear on frontpage
- krickkrack 3y agothumbs up Also it does not appear on the front page any longer (but that is where I saw it).
- Simulacra 3y agoI thought this article might have been on bullshit jobs in the tech industry but it's not. Are their bullshit jobs in the tech industry?
- Cthulhu_ 3y agoYeah, building POCs to make people above you look good to their seniors.
- wahnfrieden 3y agoAdtech
- pharrington 3y agoI might be completely wrong here as I've never worked in adtech, but the field seems like a really weird mix of bullshit jobs (the kind David Graeber wrote about), snakeoil, adtech that actually works as advertised, but still feels bad to work on because it's mostly harmful to society, and adtech that's actually legit and ethically neutral.
- bombolo 3y agoPlenty of it. Who do you think is writing all the comments about how copilot can easily make them redundant, for example.
- falloutx 3y agoThis article itself represents fake work. Remember what keeps you employed, if we only did necessary things, none of us would be employed.
- moffkalast 3y agoThat is assuming anyone able to fire you actually knows the things you do are unnecessary.
- manicennui 3y agoDoesn't this point to a fundamental problem with our economic systems? It is only going to get worse over time as more jobs can be automated. I also don't think that most people would choose to do "work".
- greatpostman 3y agoThe older I get the more appalled I am at what managers are bringing to the table versus senior engineers.
- galleywest200 3y agoI appreciate a good manager, but not really middle managers. I moved to DevOps and I report directly to a VP and it is a game-changer compared to when I reported to a middle-manager in Support. However, the Principal (senior) Engineer I work with can be a bit of an angry ass sometimes and I am unsure he would make a good manager.
- lupire 3y agoA good middle manager is a good manager of your managers. Unblocking them and coordinating with other teams. You wouldn't even know them, unless your manager was a bad apple and you needed middle manager's help. A bad middle manager is out there thought leading and babbling distracting garbage to everyone.
- rs999gti 3y ago> what managers are bringing to the table What I noticed in my org, are the senior managers are the ones who get to talk to the business people and get to muddle the waters and do a lot of repetitive work. Sometimes things do not get done until a project manager or senior dev actually talks to the business person and gets the correct requirements out. I don't know why it is this way at my org, but the IT director does not want to talk to PMs, Devs, or Analysts. He would rather have a top level circle of senior managers who insulate him from the actual work.
- juve1996 3y ago> I don't know why it is this way at my org, but the IT director does not want to talk to PMs, Devs, or Analysts. He would rather have a top level circle of senior managers who insulate him from the actual work. To me this makes...sense. A general doesn't meet each individual field soldier, it's not feasible and doesn't scale. Not sure what kind of firms people on here work for, but most of my managers all the way up have 0 life at all. They're constantly working dealing with millions of little details where they have to make an instant decision. It honestly looks like hell.
- sokoloff 3y agohttps://archive.is/3MbI7 https://archive.is/3MbI7 (the site blocks ad-blockers, so ad-blocker users might find this URL helpful)
- galleywest200 3y agoI have been getting this error from archive.is for two days now, I am unsure if this is on my end or what: > An error occurred during a connection to archive.is. Cannot communicate securely with peer: no common encryption algorithm(s). > Error code: SSL_ERROR_NO_CYPHER_OVERLAP
- ohthatsnotright 3y agoI get it too, in Firefox 114 on Linux.
- anonym29 3y agotry archive.today || archive.ph
- T3RMINATED 3y ago[dead]
- JamesHinnek 3y agoJust a reminder that lazy managers are the source of burnout for those who are under them. As a manager I can say, there is no easier job than just forwarding requests from directors directly to developers, not planning, and promising crazy deadlines to avoid conflict with higher management. If someone is being paid more, this person has to work more, I have seen so many people becoming managers just to actually avoid work, or thinking that tech is too hard and too much to study. So they instead go to a whole different area where most of your previous knowledge won't be required anymore, and they don't think that they are starting from zero, so they just don't study and read 2 blog articles and think that they got how is to work with people.
- sanp 3y ago> If someone is being paid more, this person has to work more Why? Companies don’t pay more for more work. They will try to get away with the least they can pay. Workers should do the same.
- RankingMember 3y ago> If someone is being paid more, this person has to work more In my experience, pay rarely has any kind of correlation to the amount of work being done. I see it merely as a pay for responsibility for the work of those under you or, more succinctly, "being paid to throw yourself under the bus in lieu of anyone you're managing".
- wahnfrieden 3y agoManagers usually fire team members rather than take the fall for the team.
- RankingMember 3y agoI certainly wouldn't dispute the existence of those managers- I'm thankful to have had some good managers who go to bat for their direct reports.
- 3y ago
- snide 3y agoMaybe I'm missing a core piece from this article, but it leaves out quite a bit of agency from the employee. I never understand pieces like this that rail against employers, but also seem to cast the employees in such a helpless light. If you're stuck in a situation where you're not getting great feedback on what to work on, that seems like a great time to just build things and experiment on your own. Do it within the rails of the corporate environment you're in, or hell do it outside and put that energy into something else. Just because someone doesn't provide a map, doesn't mean you can't escape the labyrinth and get creative.
- Gorbzel 3y ago> it leaves out quite a bit of agency from the employee Good catch. Of course it does, as the easiest and most lazy trend in software engineering thinkpieces is to blame middle management. Keep in mind that 90% of the article (itself “fake work” as another commenter pointed out) has nothing to do with managers. The only substantiated mention there is from a gaggle of “strategic” academics at overpriced universities, i.e. those part of what is currently the biggest scam industry of them all. Nonetheless, the causes here are so glaringly obvious that the article somehow still calls out 1) overhiring endorsed from the very top and 2) infantile responses from engineers who take absolutely no responsibility for their circumstances or trying to make things better. And yet, there’s absolutely no accountability for either of those groups. C-suite is rewarded by the market, fueled by culture that fetishes misguided views of developers. Nowhere is this worse than HN, where engineers can do no wrong. Yet speaking of make work, completely pointless arguements and “Show HN”s building a CRUD API client app for the thousandth time predominate. These (lazy/pointless) projects are then evidence that these super talented minds deserve $200k+ jobs where, yet again, managers have to deal with their egos and it’s the manager’s fault when shockingly these “individual contributors” have no idea how to contribute value to a project or in many cases even act like an adult.
- intelVISA 3y agoYou don't pay someone $200k to churn out CRUD - there's plenty of lowcode solutions like Flask for that! I somewhat agree, though, the core issue with "paying for business value" is how difficult it is to really define that across an org.
- devjab 3y agoHaving spent a few decades in Enteprise digitalisation, both in the public and in the private sector I think this issue is sort of unsolvable. I’m not convinced it’s fully down to managers, but this is obviously the anecdotal and non-tech organisation point of view, because they manage people. What I mean by this is that I’ve had excellent managers who didn’t know half their staff wasn’t doing anything remotely useful. That may sound off to you, but I think the culprit is that a lot of process and management people actually think what they are doing is creating value, despite it being a load of nonsense. I even sort of get why that is, because sometimes the business processes are actually helpful and other times they aren’t, and it’s really hard for non-business-value producers to tell the difference because of how the systems work. Say you bill clients by the hour and work this directly into your Atlassian ticket system all the way down to the developer level. You can do that, and you can even have a lot of business intelligence to show that you’re doing great, meanwhile if you ask any actual developer off the record they are likely going to tell you that it’s terrible. They will tell you things like how they game the systems instead of producing the best code. They’ll tell you how the senior developers don’t want to help the junior developers, because every minute they spend on non-billable tasks is a minute that will make them look worse on the performance matrix. Now something like that can work, and if can even involve a bunch of process/management people (as well as the BI people) who all feel what they do is useful and have data to show that it is, meanwhile the actual software development is an absolute shit show compared to what it could be if the processes didn’t get in the way. Obviously the flip side is having too little process/management and then having people cruise along doing whatever they want. Though to be fair, in my anecdotal experience you still get more value from a developer department that does this than one that tracks issues by the hour. Anyway, I’ve never seen anyone come anywhere close to solving it. Personally I tend to try to work in the places that suck the least, and shift if the process part of development becomes too tedious for me. Exploiting that it’s not so easy to find a senior developer. But I’ve honestly given up trying to impact the process/management side of things, and now just flee the ones I dislike.
- bena 3y agoThat's still a problem with management. The entire system is designed to incentivize this behavior. If your people's individual compensation is tied to their personal billable hours, your people will maximize for personable billable hours.
- taeric 3y agoOdds are silly high that this will be a ton of talking past each other in experiences. Good management is almost certainly situation specific. Such that for a good manager, you also need a good organization. And for that organization, you likely need a certain kind of worker. Tech work is an odd one as we can't decide if we are general contractors, artists, or line workers. Each will have different quirks on how they work. And, annoyingly, all could probably work at any given task. Especially if the full team and organization is aligned with those quirks.
- blitz_skull 3y ago> for a good manager, you also need a good organization False. Being a good manager is aligned with being a good leader, which is 100% down to the person who is the manager. Sure you may not have an "effective team" without a good organization, but as a manager your job is to make the team succeed, and if you're following the laws of leadership, it has nothing to do with your organization.
- noirbot 3y agoThe difficulty becomes that, in a bad organization, a good manager can easily get stuck unable to both be a good leader to their team and be a good manager as seen by the organization. I've had multiple managers fired/reassigned because they were leading the team well in a fractured organization, but because they weren't prioritizing the things that upper management wanted over the objections of their teams. If what the team wants to do to succeed is at odds with what the organization thinks it wants, the manager often can't square that circle.
- blitz_skull 3y agoNo doubt. This is the dichotomy of leadership. The alternative is don't become a manager in a bad organization. But barring that solution, your only alternative is to grind on both sides of the wall until you've either got breakthrough... or you get fired. It's not a good answer, but it lines up with the reality I've experienced.
- eysquared 3y agoI’m seeing a lot of comments that seem to point to first line management as the problem here. In my own anecdotal experience, I’ve seen a lot more “fake work” come from listless leadership that lacks a true vision for the product. That rolls down to Product Managers that can’t prioritize features and don’t really understand what they’re building or why. Ultimately this leads to engineers and members of the team working on things they don’t believe in or that don’t actually move the needle and are scrapped. In places like this the engineers and managers closest to the product and customers tend to have a better feel for what to work on, but in a large enough org it’s impossible to align those priorities across teams to get things done. This leads engineers to either POC ideas that aren’t possible in production yet or to focus on smaller features that don’t have dependencies. The blame there lies solely in upper level leadership who often care more about org size than output. I’m tired of the messaging around “lazy workers” pointing the finger where it doesn’t belong. Gut from the top if you want to get rid of the problem. It’s not the L5 engineer or the first line manager that’s holding any product back. These people tend to be the most invested in building something in my experience.
- endtime 3y agoPart of why I left Google was poor leadership at the VP level. The org wasn't set up for success and - as far as I could tell - the vision was myopic and incoherent. VP performance was more or less opaque to me for most of my career there, but eventually I got senior and experienced enough to have a real opinion. Really liked my direct manager, but we were in it together, and there was nothing he could have done about it.
- cmrdporcupine 3y agoUltimately "fake work" is work disconnected from the bottom line or profit goals of the company, since this is capitalism and that's the ultimate measure and purpose of a corporation. It's not much of a surprise that Google, Meta, etc. are full of this kind of thing, because they have embarrassing quantities of ad revenue, and yet also a burning "need" to employ in areas almost entirely disconnected from ads (for now). I won't dispute that these companies can and should do these speculative or non-revenue-bound things. But you can see how they go off the rails very easily, and this is what ultimately ties back to the article's main point about lazy management. In the end responsibility, shared vision, and clear goals are key. And I'm not entirely convinced that those things "scale up" to the organization size and sheer insane revenue-firehose of FAANG type companies.
- diego_moita 3y ago> But based on conversations with over 30 people involved in the tech industry, including current and former tech employees, I do accept the writer hypothesis that there are lazy managers but "30 people said so" as an evidence of anything is just very lazy.
- say_it_as_it_is 3y agoGreat employees facilitate bad managers by simply being themselves and doing great work. Managers just collect the karma for being there. They also interview for other positions staking a claim to work they had nothing to do with. They play great politics, though, with peers and upward.
- DeathArrow 3y agoThis article reminds me of this: https://www.businessinsider.com/rest-and-vest-millionaire-engineers-who-barely-work-silicon-valley-2017-7 https://www.businessinsider.com/rest-and-vest-millionaire-en...
- quadrifoliate 3y agoThis is sloppy and lazy in its generalizations from Google and Amazon to "tech companies" in general. They should really say something like "monopolistic tech behemoths that are in the top 10 of the S&P 500". I've worked in tech before, during, and after the hiring boom; but not for any of these companies. I have seen very little of the sort of make-work that is described in the article. Sure, there is no guarantee that research efforts will be utilized, but making that the goal from the start for political reasons is so terrible that it's likely that only FAANG bureaucracy is bloated enough to sustain it.
- arbitrage 3y agoI too have worked in tech before, during, and after the hiring boom; but not for any of these companies. I have seen very much of the sort of make-work that is described in the article. It seems our anecdotes might cancel each other out.
- cdavid 3y agoMiddle management (above first line manager) in large organizations is hard to do well. I think it is difficult to understand if you have never done it, and it is even difficult to articulate why. I find it much much harder than working as an engineer or Eng Mgr. Fundamentally, I think it is an incentive and systematic issue: what is expected of middle managers, and incentivized, requires almost complete dedication to managing up and laterally. People who spend time w/ their reports are the exceptions because there is close to 0 correlation with getting promoted. Caring about your report either require crazy number of hours, or ignoring what people above you will expect. The latter will ultimately affect their report. Many people in that line of work do the minimum ? Yes, I can believe this. But the odds are stacked against you. I used to joke "as a middle manager, doing above average work requires extraordinary dedication". 1. Lack of agency: once you are above first line management (EM), you actually have much less agency. As an EM, you can tweak processes, and improve things. You only are accountable to your manager, and maybe 2-3 other people. Once you are above that, the number of stakeholders explodes, and any perception of failure will get at you. You can't say no to many useless meetings because you have to be there. If you don't go, and something goes wrong, guess whose teams/projects will be slashed next time. 2. Corollary: spooky action at a distance. Once you're middle manager, you will get random people with random level of competence ask you things you don't even understand. I regularly encountered "You have not done X yet, and this is slowing down other teams", and that was the first time I heard of X. Everybody knows you can't do half of what you are asked, but you better not be perceived as not doing all of it. 3. Solitude: As an EM, you can foster your team. Above, you just have a bunch of individuals who very much don't work as a team. Very difficult to keep some cohesion. 4. You need to own shit you are not responsible for: You have to explain often nonsensical decisions you had no authority on, but you also cannot say "sorry guys, this is coming from above". 5. Outside of exceptions, doing a good job is completely unrelated to how you will be evaluated. There are many things you know in your heart will negatively impact your team that you absolutely have to do. The best middle managers are the ones who manage to balance the kafkaiesque and still maintain good environment in their report line. This requires an enormous amount of time that you can only do for so long, most burn out quickly. It is slightly over cynical, but I think avoiding what spakhm describers on his blog is impossible to escape above a certain size: https://www.spakhm.com/p/how-to-get-promoted https://www.spakhm.com/p/how-to-get-promoted
- treis 3y agoIMHO the real culprit is the monopolistic nature of the tech industry. Roughly, the companies are all mono/duopolies or trying to get there. It's all Golden Gooses and everyone is doing anything and everything they can to get/keep theirs. For companies like FAANGs it's no problem to waste 95 out of every 100 million they spend because that one team that hits on something might increase the market cap by half a billion. The scale is lower for smaller companies but the math is essentially the same. And once you accept waste as an acceptable cost of doing business it explodes. Because it's very hard to tell the difference between a reasonable idea that didn't work and one that never had any shot or was poorly executed.
- jgalt212 3y agoFake work exists because of VC-driven hiring. After taking VC funding, usually the easiest way to show some results is via a hiring spree. However, usually the current product suite or customer base does not need such a large support staff. Then follows the fake work.
- cornercasechase 3y agoIs there really a “debate” over “fake work”, or is that just some made up term a clueless and unethical VC tweeted? There’s been a hard push from capital to put pressure on labor. All these fantasy stories about “fake work”, “people working two jobs”… are all just cover stories for capital and execs to ramp up the pressure and punitive actions. I’m sure BusinessInsider is more than happy to play along. While this article may look pro-labor in the surface, it’s trying to legitimize concepts that are very much pro-capital.
- giantg2 3y ago"It was simply an exercise to satisfy the terms of his performance plan and string out his employment, he was told. Graham left Amazon soon after." Working as intended - make them quit rather than fire them.
- jkingsbery 3y ago> We have a good leader, which makes all the difference. I think this is the trick right here. Our paycheck might come from such-and-such company, but really we work for the people in our management chain. I'm currently at Amazon, and I've been pretty lucky with having good leaders, but part of that is because I've had the luxury of being selective (my first director in my time at Amazon was someone I had worked with previously, and when I switched teams I joined to work with someone I knew).
- ngvrnd 3y agoManagers are a form of government; that is to say, a necessary evil. Companies should spend as much energy reducing the number of managers as they spend worrying about useless employees. But it never seems to be that way.
- smugma 3y agoI’ve never heard anyone from Netflix or Apple describe this phenomenon. Netflix loves to fire people and Apple likes to starve its teams of headcount to force efficient use of people resources.
- iceflinger 3y agohttps://theanarchistlibrary.org/library/david-graeber-bullshit-jobs https://theanarchistlibrary.org/library/david-graeber-bullsh...
- cs702 3y agoThe real culprit is actually make-busy work, the main use of human labor in bullshit jobs: https://en.wikipedia.org/wiki/Bullshit_job https://en.wikipedia.org/wiki/Bullshit_job Producing new documents that get passed around in enterprises but which no human being reads may well be the most suitable application for LLMs. If you feel like you're drowning in corporate bullshit, I hate to tell you: It looks like it's going to get worse.
- yboris 3y agoProbably very related: Bullshit Jobs: A Theory by David Graeber https://www.amazon.com/Bullshit-Jobs-Theory-David-Graeber/dp/150114331X https://www.amazon.com/Bullshit-Jobs-Theory-David-Graeber/dp...
- evo_9 3y agoEven the laziest manager is 10 times more useful and effective than a scrum master. They are the biggest BS jobs in the tech industry by a mile.
- starbugs 3y agoHad to smile a little bit when I read this. I think most scrum masters are employed to virtue signal some kind of agility and organizational potential for change. Which then never results in anything tangible. It’s quite sad. If you really care and do what you are supposed to as an SM, you are very likely to get into trouble, because upper management usually isn’t interested the least bit in real change. Real change is hard and will only happen if the pain is already too strong. Real change might involve talking to your customer and changing the processes they are used to, which is usually not beneficial to the “management” level. It’s really not about scrum as such, but about the incentive structure that’s present in most medium to big sized companies.
- geodel 3y agoI feel this whole Agile industry is to distribute tech riches to wider group of people who otherwise have no interest or skill to work in IT industry. A nice benefit to companies are improved diversity numbers.
- jillesvangurp 3y agoThis kind of finger pointing / blaming is not helpful. Basically, the reason why big organizations are a lot less efficient than smaller ones is the communication overhead; and the resulting miscommunication. Small groups of people don't even need managers because they can figure out between themselves what needs doing and in what order. Management is introduced when small groups become larger and point to point communication breaks down. Point to point communication works great with 3 people, a lot less with 30. Forget about it with 300 or 3000. And so on. Big hierarchical organizations get bogged down in management structures and there's a lot of communication that starts happening via multiple hops. So, a lot gets lost in translation. That kind of collective stupidity is very hard to deal with. Add politics to the mix and now you get intentional miscommunication, selective communication, and very biased communication as well where people work against each other. All that result in a lot of wasted effort, unnecessary meetings, and other non productive work. It's not fake. But also not all that valuable.
- netbioserror 3y agoAlso, the communications overhead of large corporate hierarchies often serves and sometimes incentivizes the reduction of work. Most people are not driven by a vision of a great product, a desire to create real value, or a desire to improve one's own value; there is a reason this is the exception, not the rule. Most people want to skate by on the absolute minimum required of them, and large hierarchies have all the leaky cracks that create opportunities to avoid, defer, delay, delegate, and generally abstain from work. In my own personal experience, if your desire is to work on something that has value or if you'd like to increase your own value, you should probably work at a small company, where the hierarchy is relatively flat and where you are as directly responsible and answerable for tasks and projects as possible.
- lupire 3y agoThat's exactly the problem that obscenely highly paid leaders are supposed to be solving. And when they don't, they still get paid obscene sums.
- TheLoafOfBread 3y agoI subscribe to that. I left my previous job just after two months because I was put into a chair as a developer and then ... nothing for two months. I literally got paid to do nothing. Manager? Product Manager? Team leader? They were all pretending that newly hired people does not exist. But they went great lengths to poach me from a previous job, to do nothing? I am perplexed by this behavior until today. I have quit and set up my own company where I have less money but at least I am working on something.
- arbitrage 3y agoI got poached from a job once to a) punish a manager in a different department, and to b) serve as a check on someone else who the new manager didn't trust. People can just use you and discard you. Our industry is awful right now. I'm glad you got out and started your own company. Good for you.
- getmeinrn 3y agoNow let's talk about how this extrapolates to the rest of society.
- meristem 3y agoTL; DR: the perception of “ghost work” can also appear when employees work in functions where failure doesn’t immediately break the company. The work may have value, but the contributions support longer tails, look not needed. ———- I used to ask direct reports “how does what you are doing map to company strategies?” And if they could not do so we’d talk about what they were working on, how ‘mapping’ might work, and then decide if the work was worth it/ how to learn more about the company so their tactical was also strategic. This was significantly easier in roles the company publicly supported. For roles where our team failure would destabilize things in a longer timeline, it was extremely easy to not be able to directly map to success, or feel fungible within the company.
- costanzaDynasty 3y agoIt’s not just tech. It’s everywhere. If pay X dollars to got to college/warehousing and there isn’t a job at the other end then the Ponzi scheme falls over. I didn’t know you could go to college and get a job planning pizza parties but at my last job there was someone who that was their only job.
- alexpotato 3y agoHaving worked in finance for many years at various types of firms (banks, hedge funds, fintech startups) and hired many FAANG folks, this breakdown from a former FAANG hire put it best: "At FAANG, there were always more people than work to do. This led to lots of infighting for the best projects. In finance, there is always more work than people so the fighting is more about trying to make multiple stakeholders happy with limited resources." Another ex-FAANG colleague called it "cookie licking" since everyone wanted to make sure a cool project was theirs before anyone else took it away. I can only imagine that this all happened due to the economic effects of being monopolies and therefore being able to just hire all of the best talent without necessarily having something for that talent to do.
- bob1029 3y ago> In finance, there is always more work than people It would seem the general theme is: If the work is "cool" or "new", there isn't much of it to go around. If it is "legacy" or "profitable", no one wants to be in the same building as it.
- lupire 3y agoIt's also that companies won't pay more for the work no one wants. And elite companies won't hire less "brilliant" but worth ethical to do the boring work. During the fat times, they paid people too much for work they hate that wastes their talent. Google is full of PhD scientists maintaining CRUD apps.
- didgetmaster 3y agoNothing for an engineer is more satisfying than seeing your code be used to solve real problems for customers. Positive (and negative) feedback from people actually using the product you built is the lifeblood of those who really care about making a difference. Conversely, there is nothing more 'soul-sucking' than to realize that something you have devoted months or years of work, effort, and thought into is thrown in the dustbin because there was just no business support for it. This can happen when your company is bought out by a competitor just so they could kill your project. This can happen because a SVP decided on a whim to suddenly change the whole direction of the company. It can happen because someone in the management chain just doesn't have a clue what they are doing.
- notShabu 3y agoI heard this theory once that one of the biggest jumps in cellular complexity was when cells started to use mitochondria for energy production. This created so much abundance that organisms could afford to diversify into all kinds of shapes and sizes and ways of life. Software similarly isn't like farming where the margins are so thin that processes become homogenized. Software companies traditionally have had so much "fat" that the structures built around this cashflow are arbitrary. Some build temples and monasteries, some create a monarchies or dictatorship, some are anarchist libertarian experiments, etc... What is common among them though is that the hierarchy revolves around culture rather than pure meritocratic ability. E.g. if a foreigner goes to work in Japan, he/she might think that it's all fake work meant to keep fax machine companies alive but it's not "fake" when viewed from the perspective of keeping a culture alive. In any institution, there will always be founders and traditionalists who need the culture to stay alive to support their position. This "support" exists in the form of followers which make up the bulk of the org body. Engineering is an outlier because it's more mercenary, the skills are transferable so there isn't a need to compound loyalty and connections at one single place. That is... traditional companies are like a national army. Even in times of peace it is held together by nationalism or peacekeeping. Tech companies are like mercenary armies, they are only held together when there is Something to Do.
- threadweaver34 3y ago> In one viral TikTok video, Brit Levy, Meta's former diversity, equity, and inclusion policy analyst, said she had to "basically fight to find work" The only surprising thing here is that people who work in the DEI space have deluded themselves into thinking there's that much work to do.
- geodel 3y agoExactly. It is hilarious but true. A ton of bullshit jobs like DEI Analysts, AI Ethicists and so on, are essentially product of zero-interest rate phenomena. However, it has led to some really believing that they are carrying the weight of earth on their shoulders.
- osigurdson 3y ago>> What do these people actually do? They go to meetings. This is the biggest problem in industry: pointless meetings with no agenda and no action items. There is a watershed moment for anyone however. Once your calendar is even 40% filled (particularly if meetings are randomly distributed), flow state is pretty hard to achieve. Therefore one is better off to book even more meetings so everyone knows that you can't possibly do any actual work. Then your day is naturally completely void of meaning but you simply clock in at 9am and out at 4pm. Once the day ends you don't have to think about work at all since your work literally is meetings. If you want to have a pointless meeting, be sure to book it in the evening or weekend so that you pay the same price as people that are actually doing real work.
- Eumenes 3y agoAre there success stories of companies that have grown to a respectable level w/o management of any kind? Perhaps Valve?
- braza 3y agoI have been in such a position in a Tech Mid-Cap (400 million MAU, 11B market value) and it was personally the best job that I had in my life in terms of cushiness and low pressure; but retrospectively it has almost thrown me into the oblivion of technical obsolescence. Fast forward, most of the days were 1 hour and half meetings to decide things like where we would spend company money in the next team event or how we would consume the credits from GCP in endless PoCs, and I came to a point where I started to do pro bono work just to keep my skills up to date. My manager at that time wasn't technical at all, and he barely understood what we were doing. In more than 4 months of work, we had less than 2 hours of 1:1 conversations; and he was one of the most active people on the RSU channel to get clarifications about taxes and so on. After 4 months I saw that I was lacking some 'real work' and moved to another position in a less capitalized company, but with some technical problems to solve. The sad thing about it is that several folks that worked with me are now trapped in this company and inwards they know that if they go to the market it will be tough to find something so good on the personal level.
- somsak2 3y ago>Graham's manager told him something stunning: The finished project, which Graham worked on for more than a month, wouldn't see the light of day. are you kidding? I've worked on projects way longer that ended up getting scrapped, and multiple times at different FAANGs. this guy must be quite inexperienced to be "stunned" by this. if you don't want this risk, go to a smaller company. it's really that simple
- willio58 3y agoAs someone who just started web dev management in my mid-20s, it's hard. It's hard to do _right_. It requires being able to support, build rapport, guiding but not nitpicking or micro-managing, etc. And it requires being able to work with people of different experience levels. I never want to go full manager, I love coding. But I do derive some pleasure from being a supportive manager. I think it's specifically because I've had some lackluster managers in my past. A good manager will provide challenges to you. They will support you enough to allow you to grow while having the time and energy to do so. So many managers out there just dread their work and come to work for the paycheck. A paycheck is great, but loving your job is almost as important when it comes to being a good manager.
- urda 3y agoIt's across all areas of the industry. I had a coworker from a startup I worked in SF, let's call them "Eric W". I kept in touch with Eric W after leaving SF, and through a chunk of the pandemic. However, the pandemic turned them both selfish and paranoid (they really got hung up on my ethnicity and religion supposedly controlling all of finance and only bitcoin could save us). They would parade on Discord and Steam how "little work I did today" and "how many games I played during meetings" as he drained whatever startup he went to and from. Some folks are just proud slackers. I'm glad I cut them out of my life.
- ma34esense 3y ago[flagged]
- jl2718 3y ago> Oftentimes, employees are getting plenty of work done; it's just that the projects are of little to no importance to the company's bottom line. a.k.a. “Innovation”. For whatever reason, I’m one of those engineers that big organizations seem to hunt down for their “innovation” agenda. I have much to say about these experiences. In particular, the advice given by innovation gurus like business professors, authors, and management consultants, is terrible.