6 ms·

You're deploying via VS Code? If so, that's a weird pattern. I've been using VS Code for years to write JavaScript/TypeScript, Python, Go, Terraform, and CSS.

You're deploying via VS Code? If so, that's a weird pattern. I've been using VS Code for years to write JavaScript/TypeScript, Python, Go, Terraform, and CSS. My settings file is 60 lines, 42 of which are "for file extension X use autoformatter Y" configs. When I first switched to VS Code I was frustrated trying to make it conform to random expectations I had. Eventually I learned that it's easier to embrace VS Code's defaults for 99% of things. I just want an IDE that works well (nearly) out-of-the-box and VS Code gives me that

joshstrange 4y ago
> You're deploying via VS Code? If so, that's a weird pattern. I don't think it's a weird pattern, maybe a slightly legacy one but not out of the ordinary. I've seen this pattern used at multiple places (not implement by me). It makes sense if you have special use-cases where you need to use physical hardware and/or a local stack is too heavy or complicated to run.
- presentation 4y ago
  Though why does it need to be in your editor vs some command line tools or something else?
  - danuker 4y ago
    So you can deploy at a moment's notice. Why run a command instead of hitting a key combo? Or even deploy as soon as tests pass? Software should allow that. Especially software for writing other software.
    - Drew_ 4y ago
      Or just run a command with a key combo. Or setup your test script to run a command afterwards. This is what every IDE is doing in the background.
      - 6510 4y ago
        Then we tell the new upcoming developer that the hard part is setting up your tools. How long will this take? He asks. Oh, you answer: This will take decades! It's a wild, every man for himself kind of ride. You build a battle-royal out of abandon-ware plugins that each almost do what you want until your powerlevel finally rises to the point you just delete everything and use the terminal. The terminal is an emulator that mimics a physical device from 1941 you see, as its a physical device, there are no ever-tinkering developers bloating or [indeed] sunsetting your tools. You will finally be left alone, still in the dark but you get a cursor that no one can take away from you.
- goodoldneon 4y ago
  Sorry, “weird pattern” was a poor choice of words. I just meant that it’s an approach that isn’t common so it’s understandable that VS Code can’t handle it well. VS Code is best when it’s just an IDE. I even have to drop into the terminal for some Git stuff
roflyear 4y ago
Yeah almost an anti pattern.
- bastardoperator 4y ago
  No almost about it, it's an anti-pattern and I personally would consider it a "worst practice". If you're deploying from an IDE it means you lack visibility, feedback, and automation fundamentals. What I do like is developer ownership and being able to see a change all the way through to production but having a system of record without manual intervention is always preferred.
  - joshstrange 4y ago
    It's always so interesting to see people who have no concept of your stack/problem-space speak so confidently about what you must be doing wrong. I don't know if you've just chosen to assume the worst or don't care enough to think about it for more than a second but I've been very clear in all my comments that these are developer-specific machines we are deploying to. It's literally no different from running VMs on your local machine. There is full visibility and feedback, we aren't deploying to Prod or even QA, this is development where each developer has 2 or more boxes owned by them and only them. We also are working with specific custom hardware that our code runs on which is one reason we can't easily do this locally. To jump in and call that "worst practice" is just lazy and condescending. On top of that, it's completely wrong.
    - Drew_ 4y ago
      Your aversion to running shell commands is definitely not helping you and what you're describing definitely doesn't need an IDE to be done so it's not shocking that people are questioning how familiar you are with deploying code and/or leveraging shell programs.
      - joshstrange 4y ago
        I'm tiring of this thread. I never asked for or requested input on how we deploy code/manage our servers. I was asking questions about an IDE vs vscode and gave 1 example of trying to do the same thing in both of them. Had I known so many people would come out of the woodwork to tell me I'm doing it wrong without any idea of how our stack works I wouldn't have mentioned it. I have no aversion to running shell commands and you are being disingenuous by saying that. I have a problem with manually doing a step that I can automate. I write and run shell scripts all the time for one-off process but seeing the code I've actively writing in an environment that can run it is not one of those cases. In fact, anyone doing that manually is just being silly or obstinate. If you aren't automating something that you do 100's+ times a day then I question your skills.

joshstrange 4y ago

> You're deploying via VS Code? If so, that's a weird pattern. I don't think it's a weird pattern, maybe a slightly legacy one but not out of the ordinary. I've seen this pattern used at multiple places (not implement by me). It makes sense if you have special use-cases where you need to use physical hardware and/or a local stack is too heavy or complicated to run.

presentation 4y ago
Though why does it need to be in your editor vs some command line tools or something else?
- danuker 4y ago
  So you can deploy at a moment's notice. Why run a command instead of hitting a key combo? Or even deploy as soon as tests pass? Software should allow that. Especially software for writing other software.
  - Drew_ 4y ago
    Or just run a command with a key combo. Or setup your test script to run a command afterwards. This is what every IDE is doing in the background.
    - 6510 4y ago
      Then we tell the new upcoming developer that the hard part is setting up your tools. How long will this take? He asks. Oh, you answer: This will take decades! It's a wild, every man for himself kind of ride. You build a battle-royal out of abandon-ware plugins that each almost do what you want until your powerlevel finally rises to the point you just delete everything and use the terminal. The terminal is an emulator that mimics a physical device from 1941 you see, as its a physical device, there are no ever-tinkering developers bloating or [indeed] sunsetting your tools. You will finally be left alone, still in the dark but you get a cursor that no one can take away from you.
goodoldneon 4y ago
Sorry, “weird pattern” was a poor choice of words. I just meant that it’s an approach that isn’t common so it’s understandable that VS Code can’t handle it well. VS Code is best when it’s just an IDE. I even have to drop into the terminal for some Git stuff

roflyear 4y ago

Yeah almost an anti pattern.

bastardoperator 4y ago
No almost about it, it's an anti-pattern and I personally would consider it a "worst practice". If you're deploying from an IDE it means you lack visibility, feedback, and automation fundamentals. What I do like is developer ownership and being able to see a change all the way through to production but having a system of record without manual intervention is always preferred.
- joshstrange 4y ago
  It's always so interesting to see people who have no concept of your stack/problem-space speak so confidently about what you must be doing wrong. I don't know if you've just chosen to assume the worst or don't care enough to think about it for more than a second but I've been very clear in all my comments that these are developer-specific machines we are deploying to. It's literally no different from running VMs on your local machine. There is full visibility and feedback, we aren't deploying to Prod or even QA, this is development where each developer has 2 or more boxes owned by them and only them. We also are working with specific custom hardware that our code runs on which is one reason we can't easily do this locally. To jump in and call that "worst practice" is just lazy and condescending. On top of that, it's completely wrong.
  - Drew_ 4y ago
    Your aversion to running shell commands is definitely not helping you and what you're describing definitely doesn't need an IDE to be done so it's not shocking that people are questioning how familiar you are with deploying code and/or leveraging shell programs.
    - joshstrange 4y ago
      I'm tiring of this thread. I never asked for or requested input on how we deploy code/manage our servers. I was asking questions about an IDE vs vscode and gave 1 example of trying to do the same thing in both of them. Had I known so many people would come out of the woodwork to tell me I'm doing it wrong without any idea of how our stack works I wouldn't have mentioned it. I have no aversion to running shell commands and you are being disingenuous by saying that. I have a problem with manually doing a step that I can automate. I write and run shell scripts all the time for one-off process but seeing the code I've actively writing in an environment that can run it is not one of those cases. In fact, anyone doing that manually is just being silly or obstinate. If you aren't automating something that you do 100's+ times a day then I question your skills.