Tech people I meet in LA are much less careerist in general compared to the Bay Area (where I used to live). They work for either big tech, smaller not household name companies, or remote. Pay is on average less than the bay. Tech people in LA live in LA for the lifestyle and use the job to fund their lifestyle.
Personally (and contrary to the other comment about LA) it’s been the best place I have lived. It’s a polarizing city, understandably. But I think if you can make enough money and are ok with driving there’s endless amounts of things to do and passionate people to meet.
the phrase I've heard about LA is that its "a company town for creatives."
- https://www.industrialempathy.com/posts/design-docs-at-googl...
- https://github.com/rust-lang/rfcs
- https://github.com/kubernetes/enhancements/blob/master/keps/...
- https://blog.pragmaticengineer.com/rfcs-and-design-docs/
Hint: tailor the process and template structure based on your org size/maturity and needs. Don’t try to blindly mimic/imitate.
Most RFC committee debates ime devolve into firing squads in which the presenter needs to answer every question with pin-point accuracy and perfect context from the asker. Otherwise, they look unprepared and the RFC is negated.
This is allowed to happen because everybody is a theoretical co-equal in the process. Thus, everybody wants to have their say. You'd hope people would read ahead of time but there's always somebody who doesn't yet feels entitled to ask pre-emptive questions. It makes for very combative discussions.
The exception is when a double-skip manager stops that from happening and lets the presenter "make their case" and walk through the whole RFC.