Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Rise of Microsoft Visual Studio Code

triplebyte.com

Post reply on HN
Print view View original

181–190 of 327 posts

Re: The Rise of Microsoft Visual Studio Code

#181

Post by bitwize »

munchbunny wrote: post #68

Having gone through Triplebyte's interview process, I'll propose another interpretation: Triplebyte's interview is on aggregate biased against Java and C# developers. 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. My experience of Triplebyte's interview process is slanted towards frontend/backend deve…

I recall reading something to the effect that the most competent developers by Triplebyte's metrics used vim and Ruby on a Mac. That sounded too much like the typical hipster startup dev to be a coincidence, which got me wondering: is that really a snapshot of the best developers out there, or is it just what Triplebyte, hence their clients, are selecting for?

Re: The Rise of Microsoft Visual Studio Code

#182

Post by Waterluvian »

meowface wrote: post #179
Waterluvian wrote: post #178

Earlier quoted context omitted.

I feel like Python is your pepperoni pizza can't go wrong option for almost anything. Go feels similar but younger. I love languages with big standard libraries. Just need their package management story to settle down for a while. There's something wonderful about a language being so popular and around for so long that there's plenty of resources and answers on just about anything. I think that's a core part of what…

If Go adds generics and a smoother method of doing error handling, I could see it eventually taking Python's place. It already is doing so to an extent, but with those features plus everything else it can do better than Python, it'd be tough to beat. 95% of my programming is in Python, and I honestly don't really enjoy coding in Go that much, but with those changes I could see myself switching.

Same. 99% of my back-end and robot code is Python. Maybe this is a grass is always greener kind of thing but I'm hitting projects of a size where I miss static typing.

I will say that asyncio is amazing and really solves concurrency for me. But Go looks like you also get parallelism without a lot of work.

Re: The Rise of Microsoft Visual Studio Code

#183

Post by drewrv »

munchbunny wrote: post #68

Having gone through Triplebyte's interview process, I'll propose another interpretation: Triplebyte's interview is on aggregate biased against Java and C# developers. 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. My experience of Triplebyte's interview process is slanted towards frontend/backend deve…

That was annoying me the entire time I was reading this, the entire article has an unspoken assumption that their interview process couldn't possibly be responsible for any discrepancy in the data.

Re: The Rise of Microsoft Visual Studio Code

#184

Post by akavel »

btashton wrote: post #132
kbd wrote: post #37

Earlier quoted context omitted.

> This is a fantastic demonstration of why i exclusively use git from a command prompt... Thanks for this. I've always felt the same way but haven't been able to put my finger on why. As more things get integrated into my editor (I use VSCode) I feel like I should use the shiny features, but for source control I think I'm going to only use the commandline forever. (Edit: though plugins such as GitLens that give you s…

I also very much related to this, the two exceptions I find awkward from the command line are: * Doing partial adds with `git add -p`. I see the hunk it presents see what I want from it, but then sometimes have to go through several iterations of splitting, skipping etc.. A visual tool (even like the tool in vim-fugitive) is a huge improvement. At the end of the day I'm still looking at the staged diff before committ…

There's a somewhat hidden gem in vanilla git which can be sometimes useful:

    git gui
You can right-click on some line in the file and select "Stage Hunk for commit", etc. instead of `git add -p`. It can be also helpful for browsing history, esp. "blame digging".

Re: The Rise of Microsoft Visual Studio Code

#185

Post by dogma1138 »

feketegy wrote: post #164
Nimitz14 wrote: post #159

Earlier quoted context omitted.

> I would probably choose Go for core infra for being able to move quickly as a developer At the company I used to work at it took nearly a 1000 lines to replace an 80 line bash script. So I can't help but laugh at this statement.

Since when LoC is a meaningful metric?

Since always but it depends on what you actually take into account.

More LOC means more opportunities for error, and more resources needed to review that code and more time required for a new developer to get familiar with the code base.

That said if you have 85 LOC vs 1000 it usually means that the 85 LOC “app” used a metric ton of external dependencies which are on their own a good source for problems.

When comparing apples to apples (as in both apps use dependencies equally) I don’t see how such delta can be caused by using a different language, even using assembly would likely not cause this much inflation.

Re: The Rise of Microsoft Visual Studio Code

#186

Post by [deleted] »

hprotagonist wrote: post #11

There are some warts, but it seems nice from afar. The biggest wart is/was the "FUCK FUCK FUCK" git clean vs git reset UX error: https://github.com/microsoft/vscode/issues/32405 . This is a fantastic demonstration of why i exclusively use git from a command prompt -- i know what will happen and nobody's going to reinvent terms to put on buttons that just confuse me. In my life: - I'm committed to emacs for org-mode a…

[deleted]

Re: The Rise of Microsoft Visual Studio Code

#187

Post by mattbierner »

BeetleB wrote: post #88
asituop wrote: post #12

Earlier quoted context omitted.

Be careful that's it's only open-source if you build it yourself or if you use VS-Codium ( https://github.com/VSCodium/vscodium ). The VS-Code that everyone uses is under a Microsoft License and includes close source Microsoft telemetry (spyware?) and user data collection : https://code.visualstudio.com/License/

Not sure why you're downvoted. This is a concern. In my company, I downloaded VS Code to use it with F# for a toy project. But when I saw you cannot disable all data collection, I pretty much uninstalled it. Most likely there is no IP risk, but I did not want to go through the trouble of finding out precisely what data is collected, and/or cross check with our legal department. Plenty of people at the company do use…

I work on VS Code. You can disable VS Code telemetry and even disable all built-in online services if you like. This is documented on the website [1]

However VS Code cannot block the extensions that you install from collecting their own telemetry. Even if use a version of VS Code built from source, an extension that you install could still collect telemetry of its own. Same applies to most software that allows third party plugins (unless they do some serious sandboxing/capability restriction, or only allow installing specifically vetted plugins)

[1]: https://code.visualstudio.com/docs/supporting/faq#_how-to-di...

Re: The Rise of Microsoft Visual Studio Code

#188

Post by waynecochran »

emacsuserrrr wrote: post #19
NotANaN wrote: post #10

"Do Emacs and Vim users have some other characteristic that makes them more likely to succeed during interviews?" I think the Interview Pass Rates chart makes it clear that the answer is a statistical "Yes", at least for Emacs.

Maybe it’s because the editor was taught to students at places like MIT, Berkeley, etc?

I learned emacs in the late 1980's -- it is now an ingrained part of my brain. I hate when I have to use an IDE w a different editor -- at least most editors (and GUI components like browser textfields) respond to common emacs key-sequences.

Re: The Rise of Microsoft Visual Studio Code

#189

Post by ChrisCinelli »

munchbunny wrote: post #68

Having gone through Triplebyte's interview process, I'll propose another interpretation: Triplebyte's interview is on aggregate biased against Java and C# developers. 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. My experience of Triplebyte's interview process is slanted towards frontend/backend deve…

Well, what they hiring for, their questions in a specific language, how and who is evaluating the answers, the fact that a person is looking to work for them vs other companies are all biases. Nobody should try to extrapolate their results to the whole population of software engineers.

That said, Visual Studio is really on the rise. I used to think VSCode was late and could have never catch up with the Sublime's and Atom's ecosystem. So after trying it, I went back to my editor of choice. Lately though I went back to VSCode and I think it is pretty good out of the box and very good when you install the right plugins.

Re: The Rise of Microsoft Visual Studio Code

#190

Post by ChrisCinelli »

eindiran wrote: post #135
johngalt wrote: post #130

> Engineers who use Go are also especially strong. If you know why, please let me know. Because there is almost no reason to learn Go. Most shops want JS/Java/Python/C# etc... The primary reason to learn a language like Go is because you want to for it's own sake. It's not that you must learn Go in order to be good, or that knowing Go makes you better. Rather it's difficult to be bad and still have the desire/interes…

This is what Paul Graham calls the Python Paradox; namely that in 2004, when Python jobs were relatively more rare, you could find smarter Python engineers than Java engineers for any given project. "[I]f a company chooses to write its software in a comparatively esoteric language, they'll be able to hire better programmers, because they'll attract only those who cared enough to learn it. And for programmers the para…

I think that's exactly it. The problem is when these articles come out and everybody try to learn Go and use VS Code so they think can become smarter or at least being perceive as such :-P
Post reply on HN