Meta and Google are cutting staff

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 ]