Ask HN: Is all code patchy and bad in FANG?

Re:Ask HN: Is all code patchy and bad in FANG? by throwaway_fred on Sunday October 10, 2021 @09:24AM (#28818234)

This resonates, I also suggested that I might not be a good fit as I dont think the result impact is there. This was probably not good career move here, as it is being discussed higher up. But I honestly am unable to create impact with this codebase. This could also just mean that I am not fit for the job and they need other people.

I do understand the goal tho, that's why I raised the issue that I cant deliver enough impact in my eyes. And I think it's the right thing to raise.

Thanks for your reply, it now makes sense that quality is not a goal. At my level I should be able to work with this instead of just complaining.

[ Parent | on HN ]

Re:Ask HN: Is all code patchy and bad in FANG? by Sevii on Sunday October 10, 2021 @08:31PM (#28823277)

FAANG wants people who can 'get things done' in the byzantine code bases that they maintain. That is why they pay so much and why turnover is so high.

Fundamentally fixing the problem is not necessarily possible. At FAANG basic things like maybe upgrading from Java 8 to Java 11 are three year 50 person projects.

[ Parent | on HN ]

Re:Ask HN: Is all code patchy and bad in FANG? by tdeck on Sunday October 10, 2021 @11:14PM (#28824262)

It's also very possible that you'd be happier and more effective on a different team at the same company. All of these companies are big enough to have a great diversity of systems, from nascent projects to polished but boring workhorses, to unmaintained balls of tech debt that they can't turn off but nobody wants to work in. Often if you want to influence the direction of a codebase, it's best to get in on a new project or system that's just being built.

[ Parent | on HN ]