StackShare

I chose WebStorm because its a mature and stable production that has every feature I could ask for in an IDE. It saves me time and catches mistakes. All my normal development tasks, including amazing VCS integration, can be done quickly from a single place. They continue to make updates and integrate popular tools and frameworks.

Some people might complain that WebStorm costs money, however it is a relatively cheap piece of software for the number of hours you use it. Definitely worth it!

All of JetBrains other products are equally as awesome and provide a common interface. I also use Goland, RubyMine, and CLion. I used PHPStorm for 7 years and loved it.

I work at the same company as you and I use WebStorm for 99% of my tasks. I also have RubyMine installed and use that when I have to tweak some backend code. I tried using RubyMine for JavaScript but was unhappy with how it felt and I believe that WebStorm is faster because it has less plugins and language extensions running. Summary: Buy and use WebStorm for primary development and keep VS Code around for when you have to touch Ruby.

When I switched to Visual Studio Code 12 months ago from PhpStorm I was in love, it was great. However after using VS Code for a year, I see myself switching back and forth between WebStorm and VS Code. The VS Code plugins are great however I notice Prettier, auto importing of components and linking to the definitions often break, and I have to restart VS Code multiple times a week and sometimes a day.

We use Ruby here so I do like that Visual Studio Code highlights that for me out of the box, with WebStorm I'd need to probably also install RubyMine and have 2 IDE's going at the same time.

Should I stick with Visual Studio Code, or switch to something else? #help

Customer.io Segment #Sendgrid Prior to using customer.io to automate our email campaigns, we had been using a combination of sendgrid and an engineer to manually set up campaigns in Rails. Since we had already been using segment to handle our data for other applications, integrating with customer.io took only a few minutes. Building automated email campaigns to connect and engage with our audience is a simple point and click, rules-based workflow. Importing html for emails from sendgrid to customer.io was a snap and the UX of the drag and drop editor is virtually the same as we had grown accustomed to with #sendgrid. I like that this platform has a powerful segmentation tool, which allows us to use relevant customer data such as website interaction behavior to help us craft personalized campaigns to connect with our users.

We used CircleCI in conjunction with GitHub to achieve an integrated version control system continuous integration setup. CircleCI automatically runs our builds in a clean Docker container or virtual machine on every commit allowing us to stay on stop of any regressions as they arise. Additionally the notification system keeps our team up to date when issues do arise so we can get them fixed quickly. It even integrates with Slack to further reduce the friction in staying up to date with the status of our builds. With the automated deployment system once a build passes we can have it automatically deployed to our production environment so we can make sure our users always have the latest and greatest features.

#StackDecisionsLaunch

We used CircleCI in conjunction with GitHub to achieve an integrated version control system continuous integration setup. CircleCI automatically runs our builds in a clean Docker container or virtual machine on every commit allowing us to stay on stop of any regressions as they arise. Additionally the notification system keeps our team up to date when issues do arise so we can get them fixed quickly. It even integrates with Slack to further reduce the friction in staying up to date with the status of our builds. With the automated deployment system once a build passes we can have it automatically deployed to our production environment so we can make sure our users always have the latest and greatest features.

#StackDecisionsLaunch

To view the HTTP headers of any URL all you need to do is run the following with cURL:

$ curl -I https://example.com

The response should look something like this:

HTTP/2 200
accept-ranges: bytes
cache-control: max-age=604800
...
x-cache: HIT
content-length: 1270

If your URL has query strings then you will need to add double quotes:

curl -I "https://example.com?query=string&foo=bar"