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.
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.
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.
Can you shed more light on doing one thing at a time? Is this about removing distractions while you're trying to learn or is this as much about picking one topic to learn at a time? IE don't try to learn to play the piano and learn to speak Chinese in parallel? My assumption is that section 1 is about the small distractions but I was also wondering if the research indicates anything for multiple courses of study in parallel.
There were the below two items [0], [1] which are runtime and tooling pieces. I've used them years ago in side projects and they were helpful but haven't kept up with them recently. They both help find or handle argument validation issues as enumerated above.
1st Problem: Went through a round of interviews a while back and was talking with friends about the feedback or lack thereof and thought, wouldn't it be cool if you could practice and get feedback from someone who actually does this and made . . .
2nd Problem: Grew up playing Star Control 2 which was open-sourced as the urquan masters. However, the project seems to have lost some momentum and I feel like (on Windows at least) finding all of its exact dependencies is not easy.
Project: I've been porting a fork of UQM (http://sc2.sourceforge.net/) to Windows 10 and SDL 2 (still private) and playing with VCPKG at the same time.
My interpretation of the shift from < 32 bits into 32 bits is: before we had do do crazy things to algorithms we used to fit in those address spaces. When we transitioned to 32 bits, we didn't have to do that anymore.
So the question might be are there any surprising workarounds in the code because you're only dealing with 32 bit code where if you had 64 bits you could write some more elegant solution.
Given the recent discussion on Apple's earnings, this bit seemed to be interesting new data point:
"historically a new MacBook Pro has usually helped improve Apple's Mac sales significantly. The late 2013 model boosted overall Mac sales in its debut quarter by 19 percent year-over-year, the mid 2014 variant pushed sales by 21 percent, and even the recent 13- and 15-inch 2015 models both saw increases of around 10 percent in Mac sales in the separate quarters they debuted in."