I’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 worki…
Debate over 'fake work' and 'lazy management' in tech industry
61–70 of 249 posts
Re: Debate over 'fake work' and 'lazy management' in tech industry
#62Just 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 avoi…
> If someone is being paid more, this person has to work more No, they should deliver more value. Best managers I had didn't have that much tasks scheduled. They: 1. Made important decisions right. 2. Processed all incoming requests, both from their reports and from outside, swiftly and with full attention. 3. Had enough psychological stamina to say "no" when it's necessary and defend their team from pressure and anx…
Re: Debate over 'fake work' and 'lazy management' in tech industry
#63https://archive.is/3MbI7 (the site blocks ad-blockers, so ad-blocker users might find this URL helpful)
I 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
Re: Debate over 'fake work' and 'lazy management' in tech industry
#64I’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 worki…
i dont see a solution though, its not like upper management is going to fire themselves.
Re: Debate over 'fake work' and 'lazy management' in tech industry
#65Re: Debate over 'fake work' and 'lazy management' in tech industry
#66There’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.
Re: Debate over 'fake work' and 'lazy management' in tech industry
#67Working as intended - make them quit rather than fire them.
Re: Debate over 'fake work' and 'lazy management' in tech industry
#68I 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).
Re: Debate over 'fake work' and 'lazy management' in tech industry
#69I’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 worki…
On the contrary, worst time I had was when I was just receiving roadmaps to crunch through, that were "set in stone", came from "up there" and suggestions or personal findings weren't part of development. Yes, the technical challenge was there but that alone doesn't cut it. So it felt like I'm just a cog in a machine and after some time the mood just drops and burnout starts creeping in... I find it very consistent.
Re: Debate over 'fake work' and 'lazy management' in tech industry
#70I’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 worki…
I tend to agree but there's a real danger in leaving engineers to their own devices. I know this will be downvoted, but software engineers are the worst at planning their own work. The vast majority will just go off and do wtf ever they want. There really has to be guard rails to keep an organization sane and somewhat focused.
But this post is spot on, productivety is a business problem. Software engineers will work, probably more than anyone else in the org, typically.