|
Ape Fist posted:I'm one of 2 people in my office using VSCode and I will DIE before I change. Good luck fresh meat.
|
#
?
Jan 26, 2018 03:30
|
|
|
|
| # ? May 10, 2024 00:38 |
|
|
Ape Fist posted:I'm one of 2 people in my office using VSCode and I will DIE before I change. We're IntelliJ, but we're actually looking forward to using VSCode for pair-programming was VSCode Live is available. I'm hoping Jetbrains has this in store for IntelliJ very soon.
|
|
#
?
Jan 26, 2018 03:42
|
|
|
Dr. Poz posted:This assumes any health complications are handled within a time frame that doesn't cause a company to let you go causing you a loss in coverage. What you call a "sweet deal" is really a gamble for a lot of people. We still have COBRA (for now  )Rubellavator posted:I just got done marking a junior devs PR as needs work for the 4th time in a week. Everybody keeps talking about how it's the most comments they've ever seen on a PR (40). The very best is when you have two senior developers arguing with each other in your coffee review. ChickenWing posted:Same with intellij I'm not sure I want to know how imports could cause terrible PRs.
|
|
#
?
Jan 26, 2018 04:00
|
|
|
Volmarias posted:I'm not sure I want to know how imports could cause terrible PRs. It's like when a PR changes 1 line of code and 2000 lines of whitespace
|
|
#
?
Jan 26, 2018 04:11
|
|
|
Volmarias posted:The very best is when you have two senior developers arguing with each other in your coffee review. Way back when, I worked on a machine that was going to be competitive with Keurigs. We're building the very first one, so there's no mass production on the "k-cups" yet and every single one is a precious resource. So I'd be testing the firmware changes and had to capture a bunch of other data about the mechanisms and flavor. I was drinking a lot of coffee. By 2 PM I'd be wired to the gills and utterly useless at my nominal job.
|
|
#
?
Jan 26, 2018 04:36
|
|
|
Sedro posted:It's like when a PR changes 1 line of code and 2000 lines of whitespace Or when you get the OK from your VP to implement Checkstyle on a codebase for which it previously didn't exist. Now suddenly everyone comes to you because they just looked at git blame instead of the log to see who was really responsible.
|
|
#
?
Jan 26, 2018 04:40
|
|
|
Volmarias posted:The very best is when you have two senior developers arguing with each other in your coffee review. The standout junior devs have coffee delivered from all over the world each week and always offer you a sample.
|
|
#
?
Jan 26, 2018 04:42
|
|
|
JawnV6 posted:Way back when, I worked on a machine that was going to be competitive with Keurigs. We're building the very first one, so there's no mass production on the "k-cups" yet and every single one is a precious resource. So I'd be testing the firmware changes and had to capture a bunch of other data about the mechanisms and flavor. ...decaf is a thing...
|
|
#
?
Jan 26, 2018 05:25
|
|
|
Sedro posted:It's like when a PR changes 1 line of code and 2000 lines of whitespace ?w=1 on the files url tells githhub to ignore whitespace changes 
|
|
#
?
Jan 26, 2018 05:35
|
|
|
geeves posted:The standout junior devs have coffee delivered from all over the world each week and always offer you a sample. I made a typo and I'm glad I did. Sedro posted:It's like when a PR changes 1 line of code and 2000 lines of whitespace Yeah, I get that, but at some point you have to just rip the band-aid, especially if it's just imports. Fix all the files in the codebase and commit it and tell everyone to not be a gently caress up in future commits.
|
|
#
?
Jan 26, 2018 06:02
|
|
|
geeves posted:Or when you get the OK from your VP to implement Checkstyle on a codebase for which it previously didn't exist. See, I don't get this. When I blame a file, I find the line I'm interested and take a look at all the changes in that revision as a whole. If the first set of changes is just whitespace or formatting, I just run blame backwards from that commit. It's really no big deal. Much more annoying is how SVN flat out doesn't understand UTF-16. It thinks that a text file encoded in UTF-16 is actually a binary file, and so blame just outright doesn't work. This is when I get to pretend to be a computer and run something very much like a manual binary search.
|
|
#
?
Jan 26, 2018 06:08
|
|
|
Silently rewriting recently merged code someone else wrote has to be one of the more poorly mannered things I could imagine happening amongst developers and yet here we are.
|
|
#
?
Jan 26, 2018 07:15
|
|
|
I agree to a point, you could tell them at PR time you are not happy with how it looks and ask them to change it if they want your approval mark. This gives everyone an opportunity to learn. On the other hand, the code you write in a project is not yours to have feelings for. It is code in a project that you happened to have touched last and someone else decided to build on that which is a good thing. There is little room for feelings to be hurt in the coding workplace when it comes to code.
|
|
#
?
Jan 26, 2018 08:55
|
|
|
geeves posted:Or when you get the OK from your VP to implement Checkstyle on a codebase for which it previously didn't exist. The honest-to-god solution prettier.js uses is the apply style fixes to the entire git history. My solution is to autolint any file I touch as part of a fix. If you come to me with git blame, at least I will be aware of the file. If nobody has touched a file in a really long time, it shall remain as untouched as Tutankhamun's tomb.
|
|
#
?
Jan 26, 2018 14:17
|
|
|
Keetron posted:I agree to a point, you could tell them at PR time you are not happy with how it looks and ask them to change it if they want your approval mark. This gives everyone an opportunity to learn. On the other hand, the code you write in a project is not yours to have feelings for. It is code in a project that you happened to have touched last and someone else decided to build on that which is a good thing. There is little room for feelings to be hurt in the coding workplace when it comes to code. Sure, but you can make the effort anyway. I like this article (parts 1, 2) about how to act like a decent human adult when doing code reviews. You should at least get team buy-in about fixing styles, etc.
|
|
#
?
Jan 26, 2018 15:00
|
|
|
Keetron posted:I agree to a point, you could tell them at PR time you are not happy with how it looks and ask them to change it if they want your approval mark. This gives everyone an opportunity to learn. On the other hand, the code you write in a project is not yours to have feelings for. It is code in a project that you happened to have touched last and someone else decided to build on that which is a good thing. There is little room for feelings to be hurt in the coding workplace when it comes to code. That’s what PRs are for. “Check your ego” is great advice in an environment where everyone respects one another and some semblance of etiquette is followed. In this particular case I would also wager that this sort of thing is entirely about the rewriter having feelings of ownership or property around a project.
|
|
#
?
Jan 26, 2018 15:39
|
|
|
Maluco Marinero posted:If that’s 4 swings and misses, isn’t it about time to pair it rather than keep them flailing? He's fully capable, he's done tickets of the same level of effort without needing a pair. I feel like he was maybe being lazy and trying to find the boundaries of what qualifies as acceptable work. #1 was a redesign because of some bad requirements (not his fault), and that he needed to finish testing (his fault), #2 was explaining to him that he needed to test his client-side validation (part of the redesign) and also add back-end validation, #3 was telling him he needed to test his back-end validation and also that some of his logic could be reduced. #4 was really sitting down with him and explaining to him how that logic reduction worked, that's on me.
|
|
#
?
Jan 26, 2018 15:48
|
|
|
Ape Fist posted:I'm one of 2 people in my office using VSCode and I will DIE before I change. This is the true way. I myself will carry you through the gates of Valhalla. You shall ride eternal. Shiny, and chrome.
|
|
#
?
Jan 26, 2018 16:32
|
|
|
Skandranon posted:This is the true way. I myself will carry you through the gates of Valhalla. You shall ride eternal. Shiny, and chrome. I really like VSCode a ton, my office just switched to it and I’m a big fan. Of course I was using NetBeans before so maybe that’s the reason?
|
|
#
?
Jan 26, 2018 17:21
|
|
|
I've converted someone in the office to VSCode. The Grand Crusade begins.
|
|
#
?
Jan 26, 2018 18:25
|
|
|
I use intellij, why should I switch?
|
|
#
?
Jan 26, 2018 18:44
|
|
|
Keetron posted:I use intellij, why should I switch? I don't use intellij so I'm not really qualified to tell you why you should. All I know is that the plugins are pretty fuckin' great and the soon-to-be released pair programming support is going to be huge.
|
|
#
?
Jan 26, 2018 18:51
|
|
|
Keetron posted:I use intellij, why should I switch? I went from Webstorm to VSCode, really happy I did #1 Speed - VSCode is just so much faster. #2 It can do everything I did in webstorm
|
|
#
?
Jan 26, 2018 19:25
|
|
|
I switched to Code a few months ago from Sublime with a bunch of extensions / preferences accumulated over the years. I was at a conference and a co worker suggested I try it and have loved it since. Still use PHPStorm fairly often for larger PHP projects especially if I'm trying to familiarize myself with a new codebase. And plenty of vim use still but mostly just for quick edits and things. But yeah Code is real nice.
|
|
#
?
Jan 26, 2018 19:33
|
|
|
Okay what's better about VSCode for, say, C# editing than full-on Visual Studio?
|
|
#
?
Jan 26, 2018 19:42
|
|
|
Rocko Bonaparte posted:Okay what's better about VSCode for, say, C# editing than full-on Visual Studio? Nothing? But it's sure as gently caress better about editing Powershell, Javascript, Python, HTML, CSS, and XML than Visual Studio.
|
|
#
?
Jan 26, 2018 19:47
|
|
|
Rocko Bonaparte posted:Okay what's better about VSCode for, say, C# editing than full-on Visual Studio? It's not better than C# than Visual Studio, but it is much thinner. And free. If you are already paying for Visual Studio, you probably want the additional features it brings for C++ and C# development. For web development, most of those things are useless. As a free, cross platform alternative though, it's pretty good for C# development.
|
|
#
?
Jan 26, 2018 20:11
|
|
|
Skandranon posted:It's not better than C# than Visual Studio, but it is much thinner. And free. If you are already paying for Visual Studio, you probably want the additional features it brings for C++ and C# development. For web development, most of those things are useless. On Windows I still use Visual Studio for C# and C++ (mostly because of ReSharper). Code is a good replacement for Sublime. It's pretty much the only Electron app that doesn't perform like poo poo. Code is fantastic for F# (Linux and Windows), and similar to Sublime can be easily configured with Ansible. At my last job (Windows full stack devs) a few people used Sublime and most of those switched to Code for PoSh & JavaScript, but afaik everyone still used Visual Studio for C#.
|
|
#
?
Jan 26, 2018 20:28
|
|
|
I use full-fat Visual Studio for our C# stuff, VS Code is for everything else; Terraform, Packer, Ruby, Python, Go, Node, Powershell.
|
|
#
?
Jan 26, 2018 20:30
|
|
|
Boss just told me we don't have any way to test 1/3 of our feature set and won't for months (I make front ends and middle ware for embedded devices/sensors etc and they're not willing to free up one of the prototypes for a few days or give me access to the test data). I was told to just "work fast and loose and break things" Kill me now. So now I'm hooking up a stubbed out bit stream parser that is sending faked data that may or may not bear any resemblance to the real data. Also "our customers are our alpha testers."
|
|
#
?
Jan 26, 2018 21:05
|
|
|
LLSix posted:I was told to just "work fast and loose and break things" Kill me now.
|
|
#
?
Jan 26, 2018 22:27
|
|
|
LLSix posted:Also "our customers are our alpha testers." Yikes
|
|
#
?
Jan 26, 2018 22:50
|
|
|
Don't forget about : https://marketplace.visualstudio.com/items?itemName=humao.rest-client Once I installed that, an hour later I uninstalled and purged my memory of that awful, bloated, nagware, piece-of-poo poo software: PostMan.
|
|
#
?
Jan 27, 2018 01:08
|
|
|
PostMan is awful?
|
|
#
?
Jan 27, 2018 16:06
|
|
|
Yes.
|
|
#
?
Jan 27, 2018 16:14
|
|
|
It's ok, we've mostly migrated to using Newman at my place. That way at least I get to mention that Newman in Seinfeld was a US Post Office worker and everyone's eyes light up and it brightens my cold, soulless day of corporate wage slavery.
|
|
#
?
Jan 27, 2018 16:31
|
|
|
LLSix posted:Boss just told me we don't have any way to test 1/3 of our feature set and won't for months (I make front ends and middle ware for embedded devices/sensors etc and they're not willing to free up one of the prototypes for a few days or give me access to the test data). I was told to just "work fast and loose and break things" Kill me now. Well, hey, if your boss wants to waste your time on building things you'll almost certainly have to rebuild later, on a much tighter timeline, with an angry customer screaming in his ear...
|
|
#
?
Jan 27, 2018 16:50
|
|
|
At that point, quality will be improved... The customers will be beta testers instead!
|
|
#
?
Jan 27, 2018 17:16
|
|
|
Ither posted:PostMan is awful? I guess enough people need the bloated feature set, and are willing to pay for the 'enterprise' version, to support a 30+ person company, but I just wanted a way to make HTTP requests and save them for later. I don't know how many hours of my life I lost fighting the over-engineered Postman UI, but I'm happy the pain is behind me. The beauty of the VS extension I posted is that the HTTP requests are just simple text files (or multiple per file) that can be read by anyone and committed to VCS, etc. Postman makes this intentionally annoying to do to push users to storing their HTTP call config in the  It's the classic case of a free, useful tool becoming productized and extended to the degree where it now misses the original point.
|
|
#
?
Jan 27, 2018 21:11
|
|
|
|
| # ? May 10, 2024 00:38 |
|
|
B-Nasty posted:It's the classic case of a free, useful tool becoming productized and extended to the degree where it now misses the original point. That's the point at which I stopped using it too. I don't want to loving sign in or create an account to test some JSON - i know you can skip it but its a ridiculous bump in the road of Run Tool -> Test things.
|
|
#
?
Jan 27, 2018 21:55
|
|