undefined | Better HN

0 pointsgoodoldneon3y ago0 comments

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

0 comments

joshstrange3y 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.

presentation3y ago

Though why does it need to be in your editor vs some command line tools or something else?

danuker3y 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.

1 more reply

goodoldneonOP3y 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

roflyear3y ago

Yeah almost an anti pattern.

bastardoperator3y 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.

joshstrange3y 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.

2 more replies

j / k navigate · click thread line to collapse

0 pointsgoodoldneon3y ago0 comments

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.

0 comments

joshstrange3y ago

> You're deploying via VS Code? If so, that's a weird pattern.

presentation3y ago

Though why does it need to be in your editor vs some command line tools or something else?

danuker3y 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.

1 more reply

goodoldneonOP3y 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

roflyear3y ago

Yeah almost an anti pattern.

bastardoperator3y ago

joshstrange3y 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.

To jump in and call that "worst practice" is just lazy and condescending. On top of that, it's completely wrong.

2 more replies

j / k navigate · click thread line to collapse