So I started wondering why Apple would even want to add such a useless feature into an otherwise really powerful and useful editor, even back then in Xcode 3. And I remembered from my more recent experiences using Xcode that its git integration is not very useful and overly simplistic. One of the things that stuck out to me was the silly 'SCM' option in the NSOutlineView on the left side, which I had absolutely never touched. Yesterday I came across a screencast I made in 2009 back when Xcode had separate windows for the console and the editor, and Interface Builder was a completely separate program external to Xcode.

That's fine since most of Triplebyte's clients are probably looking for web frontend/backend skills, but I think this means that Triplebyte's test shouldn't be seen as an objective measure of programmer skill, just an objective measure of fit for Triplebyte's clients. They're all competent developers, but the version of Triplebyte's coding test that I took (and passed) would be in unfamiliar territory for people in this team. Several developers on this team are exceptions to the 'don't roll your own cryptography' adage. That's because their expertise is in low level security. However, in the team I currently work with, the team is in aggregate heavily C# with only secondary experience in web frontend/backend development. Fortunately for me, that was my background.

My experience of Triplebyte's interview process is slanted towards frontend/backend developers of web apps. I'm not accusing Triplebyte of 'being biased', but rather pointing out that Java and C# tend to correlate to a skill set that Triplebyte's test process values less. Having gone through Triplebyte's interview process, I'll propose another interpretation: Triplebyte's interview is on aggregate biased against Java and C# developers.

Visual studio code diff