Live data from Hacker News

Debate over 'fake work' and 'lazy management' in tech industry

businessinsider.com

181–190 of 249 posts

Re: Debate over 'fake work' and 'lazy management' in tech industry

#181
post #57

Earlier quoted context omitted.

Part 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 abou…

+1 on this. Spent 4 years at Google including spending time as a TLM. Left around 2020 so my impressions may be a bit out of date. I spent time in both the Geo and Search PAs, and IMO Google's biggest problem is listless senior leadership. Google's orgs tend to lack product vision - there's a lot of abdication to front-line teams to ideate, come up with their own ideas, and ship features. My VP-levels were AFAIK only…

[dead]

Re: Debate over 'fake work' and 'lazy management' in tech industry

#182
post #38
post #19

Maybe 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 th…

> 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,…

You 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.

Re: Debate over 'fake work' and 'lazy management' in tech industry

#183

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…

So spot on. You see tons of articles and "thought leadership" on Managers vs Leaders as if managers are holding a company back through incompetence or malice. Oh man. Reality is leadership sets processes because they believe the "last ounce of juice" hasnt been squeezed. I can point you to a whole bunch of leadership rubriks (at faang/maangs) that is all about showing "impact" vs getting actual work down - and they all get vocalized a lot more during perf/calibration seasons. I am pretty sure someone who is a "Leader" will just say true work always equates to quantifiable impact (north star metrics etc) all the while ignoring the fact that collaboration needs a lot of political skills - ie convincing why we should do what leadership wanted to begin with - but without their ack. "I trust you will sort this all out instead of depending on us leaders".

I know i know. I really apologize for sounding angry there. I have seen so many smart and well meaning people getting demotivated (and giving up) because the modern corp is built around "preventing" work getting done than channeling all this passion and then execs are surprised at why people are "saying they are burnt out" or not being productive.

Re: Debate over 'fake work' and 'lazy management' in tech industry

#184
post #84

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…

I think there's also an issue that execs can create the appearance of being busy (and may indeed spend a ridiculous number of hours in meetings) but it can be hard to see if they're contributing anything valuable. I was at a startup which over a period of years repeatedly had new execs come in, claim that something was wrong with our planning or goal-setting process, "restart" the whole thing in a way which was virtu…

I worked at a place where they had an entire division of people basically filled the role of Tom Smykowski from Office Space.

It was both pitiful and amazing. They didn’t really produce any valuable output, but by scheduling meetings and debriefings and briefings, etc they were able to engage at high levels. The dude in charge somehow took over project managers, and they literally started building these colored briefing binders inspired by some History channel documentary the featured the President’s daily briefing by the CIA.

At the end, I started losing talented engineers to folks getting significant promotions to attend meetings with bigshots. The rationale was that in order to deliver the “CIA briefing” to the VP of Custodial Services, you had to be a Director or something.

Re: Debate over 'fake work' and 'lazy management' in tech industry

#185

Earlier quoted context omitted.

This is how you do high quality skip levels: 1. What is going well? 2. What is not going well? 3. What can be done to improve? Pretty much know what's going on. Anyone who BSes the second question needs to be layered or leave.

Isn't the necessity of skip meetings itself a pathological sign? The only thing you legitimately need to talk to your manager's manager about is things your manager can't handle -- i.e. mostly problems with and/or praise for your manager. Everything else should go through your manager, or what are they there for?

Depends on the org and the situation. Sometimes the guy a level up has a broader perspective.

Like anything, ymmv. If it’s setup as a way to rat out your boss in a deep org, that’s stupid. If it’s a way for the director to establish relationships with some of the ICs, that can be productive.

Re: Debate over 'fake work' and 'lazy management' in tech industry

#186

Earlier quoted context omitted.

This is how you do high quality skip levels: 1. What is going well? 2. What is not going well? 3. What can be done to improve? Pretty much know what's going on. Anyone who BSes the second question needs to be layered or leave.

Speaking truth to power is rarely easy. Some leaders can take genuine feedback others cannot. Until you have a good pulse on the situation, is it really surprising most people default to inauthentic critiques?

This is why I'm very skeptical on the use of 1-on-1 meetings with management as a means to keep a finger on what's going well or badly in an organization.

If someone is OK with telling management things they don't want to hear, they'll tell management those things regardless of 1-on-1s.

Re: Debate over 'fake work' and 'lazy management' in tech industry

#187

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…

So spot on. You see tons of articles and "thought leadership" on Managers vs Leaders as if managers are holding a company back through incompetence or malice. Oh man. Reality is leadership sets processes because they believe the "last ounce of juice" hasnt been squeezed. I can point you to a whole bunch of leadership rubriks (at faang/maangs) that is all about showing "impact" vs getting actual work down - and they a…

[deleted]

Re: Debate over 'fake work' and 'lazy management' in tech industry

#188

Earlier quoted context omitted.

This is how you do high quality skip levels: 1. What is going well? 2. What is not going well? 3. What can be done to improve? Pretty much know what's going on. Anyone who BSes the second question needs to be layered or leave.

Isn't the necessity of skip meetings itself a pathological sign? The only thing you legitimately need to talk to your manager's manager about is things your manager can't handle -- i.e. mostly problems with and/or praise for your manager. Everything else should go through your manager, or what are they there for?

How do you know that your direct reports are doing their jobs well if you never talk with the people they're managing? Just take their word for it?

"Yes boss, all my subordinates are happy and think I'm doing a stellar job at managing this team."

Re: Debate over 'fake work' and 'lazy management' in tech industry

#189

The older I get the more appalled I am at what managers are bringing to the table versus senior engineers.

Same. In my experience about 1 in 5 has been some help to the team (the rest hinder or contribute neutrally), but even they have an easier/less stressful job and work far less hours and apply far less mental bandwidth to each task. I'm convinced becoming a manager should mean a pay cut.

[dead]

Re: Debate over 'fake work' and 'lazy management' in tech industry

#190
>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

Post reply on HN