Currently I’m a GTPM at Meta and this is the expectation we have for onboarding to a new team unless you’re early in career. I’ve seen this be the case for SWE and other roles in the technical domain. Typically you have an expertise area and at least on my team a starter project or 2 with a tangible deliverable to get you going on something while you ramp and meet others and figure things out. Meta is a big place though so could be other expectations in other organizations.
For Japanese go server, I'd suggest IGS aka PandaNet.
It's hard to say how much larger it is than OGS. OGS has an enormous population of correspondence players but generally smaller for live play maybe by 3x?
Most of the buildings I spent time in for the last 7 years didn't have private offices any longer. Studios A-D had hybrid models where leads and the most senior engineers often had very small glass offices and teams sat in bays (I think some of those might have reverted to all small glass offices). 16,17,18,40,41,42,43, some of the buildings in the 30s as well had all moved to open. Many of the newest buildings (which I forget the numbers of were open) and IIRC , the new campus when complete was to be open. There were still to be sure many many buildings with offices but as buildings were remodeled they were mostly converted to open offices.
Ah fair enough. It's been a little while. I'm surprised the Office buildings (16-18) turned hybrid, since weren't the buildings themselves architected to basically only have window offices? It was shaped like a snake to optimize for that.
Recalling my time there, one tweak-- EVP > CVP so those are backward. There are a hand full of EVPs but quite a lot of CVPs running around. TBH Past Partner (68) I'm not sure the levels really matter much and I forget the pure Software Eng equivalents to those higher levels (Distinguished Engineer and Technical Fellow).
I do agree on avoiding electron if possible as users do notice. I've seen folks who perhaps don't know the intricate details of software run into performance issues.
A public example: Dwyrin is a YouTube streamer playing Go/Baduk. After most streams he reviews the game and likes an app called Sabaki. About 8:10 minutes in, he remarks on the performance of the app (https://youtu.be/vrX4qlbpQfU?t=492). Sabaki is an electron based app.
I do however disagree with removing right click / highlighting. That makes copy paste difficult or impossible for the typical user. I spent years working on Silverlight and UWP and one of the things I recall the team looking back on particularly with Silverlight and regretting was that TextBlocks by default didn't have highlightable text. Its too useful for users sharing error messages with you as the developer or data with each other to get their jobs done.
When I see apps going Electron to me they're saying "I care more about making this easily available and focusing on features other than performance" - which is absolutely fine it's a value statement.
Electron likely helped Sabaki focus on other features with good enough performance, while being the best looking and most skinnable Go app by a country mile (I created a How to train your Dragon skin to temp my partner into learning Go :D)
Only so many hours to dedicate to a project, you have to pick what you value most. This comme T is partially because I'd hate for the people involved with Sabaki to not hear that at least some of their users "get it" and love it.
MDN's compat chart doesn't make clear if Edge supports this or not but manual experimentation suggests not although trimRight is supported so a possible polyfill. I filed a bug against Edge just now.
