![]() ![]() ![]() With a heavy heart I had to abandon an editor that I had valued at 70 dollars, which at that time was also the largest sum I had ever paid for software.Īs soon as VS Code started to gain traction, I made the switch. I had to choose between two borderline unusable and one functioning but heavy editor. Meanwhile Atom was released and it got its bug fixes and new features regularly, even though it was and still is really slow. The timing was really bad as ST2 still had showstopper issues (for me) that were fixed in ST3, which in turn had another bunch of unfixed bugs. Then came 2014 and it started to look like the Sublime developer had taken a hiatus. Another reason was that ST2 had long outstanding bugs that were already fixed in the ST3 development version, which was made available to paying customers only, and it felt like a good idea to support the development. The primary one was that it felt like Vim with everything configured out of the box. I originally had two reasons why I bought Sublime. For git, Magit is the same secret weapon that pg claimed Lisp was for programming. I tried both for a few weeks each, but absolutely nothing compares to Magit. I use Xcode and VS Code ever day, and I absolutely never use the Git functionality in either of them. And I imagined this scenario where they were brainstorming and someone higher up in the Xcode team was like "ok guys, I got word from above that 'source code' is becoming a big thing now, and we need to add it somewhere" and someone was like "how about the project navigation list?" and someone else maybe piped up "but it doesn't really fit hierarchically in the metaphor" and someone else was like "dude it's 4:30pm some of us have families to get back to can we just forget about the metaphorical inconsistencies?" and they just added it as an expandable item. 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. Visual studio code js complexity analysis windows#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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |