Meta and Google are cutting staff

Re:Meta and Google are cutting staff by battery_glasses on Wednesday September 21, 2022 @05:55PM (#32932074)

Diff count/LoC count is recorded and made publicly available for all engineers in a graph that lets you easily compare metrics between developers and teams. This means if you are constantly comparing your output to the rest of the team.

The multi-axis performance review criteria that requires you to show deliverables on things like your impact on team-building or culture. This means that when you might normally get a couple week low-output time between projects, you are usually looking for something to fill in the non-coding axis, like organizing a team virtual offsite event or searching for a way to improve the codebase.

Organizing team activities and code quality initiatives are a good thing, but the explcitivity in which you need to show deliverable impact on all axis is something I found unique to Meta and very exhausting.

[ Parent | on HN ]

Re:Meta and Google are cutting staff by Johnny555 on Wednesday September 21, 2022 @06:05PM (#32932173)

Doesn't that just encourage writing code for max LoC rather than efficiency or maintainability? Instead of generalizing a procedure you use in multiple places to make it a single function, if you write it out (slightly differently) each time you do it, then you get a higher LoC count?

[ Parent | on HN ]

Re:Meta and Google are cutting staff by battery_glasses on Wednesday September 21, 2022 @06:30PM (#32932436)

I mean people there aren't stupid and there is a fairly high engineering bar, your code won't get through review if you're doing stuff like that.

Where it really digs is when you are 1.5 weeks into writing an in depth project plan, meeting with other engineers, coordinating cross teams, researching, reviewing code etc. you better have a good explanation why your delivery over time graph has a big flat spot.

[ Parent | on HN ]

Re:Meta and Google are cutting staff by outworlder on Wednesday September 21, 2022 @07:17PM (#32932891)

> Where it really digs is when you are 1.5 weeks into writing an in depth project plan, meeting with other engineers, coordinating cross teams, researching, reviewing code etc. you better have a good explanation why your delivery over time graph has a big flat spot.

That's 95% of what I do in my company. I guess by Meta's standards I'm not working?

[ Parent | on HN ]

Re:Meta and Google are cutting staff by n0tth3dro1ds on Wednesday September 21, 2022 @08:17PM (#32933345)

How are non engineers graded then? Is it just the “GitHub metrics” of merged LoC?

I know architects that spend most of their time writing design docs. Does that not get measured as a deliverable? That’s literally their job

[ Parent | on HN ]

Re:Meta and Google are cutting staff by kevin_thibedeau on Wednesday September 21, 2022 @06:15PM (#32932282)

That penalizes those implementing one line bug fixes buried in the codebase. Each one may be worth 10K lines of new code but numeric driven management will never know.

[ Parent | on HN ]

Re:Meta and Google are cutting staff by aaaaaaaaaaab on Wednesday September 21, 2022 @06:38PM (#32932517)

I've never experienced this at Meta. In fact I've worked considerably less intensely there than at my previous place, and I was considered a high performer in my team.

[ Parent | on HN ]

Re:Meta and Google are cutting staff by battery_glasses on Wednesday September 21, 2022 @06:49PM (#32932625)

Were you on a product or a platform team?

[ Parent | on HN ]

Re:Meta and Google are cutting staff by aaaaaaaaaaab on Wednesday September 21, 2022 @07:11PM (#32932851)

Product. RP org.

[ Parent | on HN ]

Re:Meta and Google are cutting staff by znpy on Friday September 23, 2022 @05:54PM (#32957569)

Jesus Christ, I definitely dodged a bullet.

That definitely sounds like pushing you to be “productive” as much as your body allows without burning out.

[ Parent | on HN ]