Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've had this argument with a Google Developer.

He told me that for efficiency, they had different stages in the content rendering and that the main page structure didn't have your user information yet. That's rubbish IMHO because the accept language header should be readily available in that phase.




I've seen similar dysfunctions in other big orgs where a feature or bugfix would need to cross team boundaries and the outcome inhabits zones of vaguely defined responsibility.

The guy you argued with sounds like they were semi-justifying this with the typical "noogler" rose colored glasses.


> He told me that for efficiency, they [had to make a broken product]

That's called premature optimization.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: