271–280 of 327 posts
> 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…
Ok I stopped reading when they started drawing graphs how well the people using certain editors fared better in their test as if the editor could have anything to do with it.
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.
Funny how people analyse data and draw conclusions without applying any statistical method. Yeah, maybe more people use VS Code, but I don't think it has anything to do with people's failure or success.
Unless the interviewer is a big fan of VSC and they favour other VSC users.
Earlier quoted context omitted.
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…
VSCode is only on the rise because alternatives are really bad. Meanwhile, it offers good defaults, and decent latency on modern hardware but for me it is just a glorified syntax highlighter. VSCode becoming so popular should not tell us it is a great product, but that most modern alternatives suck.
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…
Earlier quoted context omitted.
My most famous quote in my work Slack is: "git already has a luxurious client! it’s called git and has lots of shinies."
While I agree with this in most cases, visual merge is a huge deal.
Ok I stopped reading when they started drawing graphs how well the people using certain editors fared better in their test as if the editor could have anything to do with it.
They are just exploring the data they have acquired. May be they could have phrased that section differently.
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…
amen people look at me like I'm an old crazy dude because I don't use a git UI or eclipse, or intellij, or from sublime. Git already has plenty of quirks, adding another layer of unknown on top of it is a no-go