Visual Studio Code

• Go because it's easy and simple, facilitates collaboration , and also it's fast, scalable, powerful.
• Visual Studio Code because it has one of the most sophisticated Go language support plugins.
• Vim because it's Vim
• Git because it's Git
• Docker and Docker Compose because it's quick and easy to have reproducible builds/tests with them
• Arch Linux because Docker for Mac/Win is a disaster for the human nervous system, and Arch is the coolest Linux distro so far
• Stack Overflow because of Copy-Paste Driven Development
• JavaScript and Python when a something needs to be coded for yesterday
• PhpStorm because it saves me like 300 "Ctrl+F" key strokes a minute
• cURL because terminal all the way

Problem was wanting to save time and money on converting well-written C# code to Ubuntu. Solution was to use Mono and Visual Studio Code which allowed us to convert our application libraries straight across.

As developer at Applied Health Analytics we decided to create a React Native App. In terms of #IDE I'm a good fan of PhpStorm cause we have a lot of PHP in the backend, but I've definitely gave a try to Visual Studio Code and now is my primary JavaScript #IDE. I was impress how fast VS Code has become the No.1 @JavaScript Editor in the community.

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

Prettier not formatting code on save in Visual Studio Code? - I've come across the same issue and took me a long time googling around to find the issue.

It is actually a very simple fix. Add the below to your Visual Studio Code settings.json

"[javascript]": {
    "editor.formatOnSave": true
},
"[javascriptreact]": {
  "editor.formatOnSave": true
}

I use Visual Studio Code every day, it was very refreshing coming from Atom to get a lightweight, all i need setup right out of the box.

After working with Atom for around 2 years I switch to VSCode.

Here is why:

1. Color display of variables in code. This may now sound much, but it improve the display of scss variables and its a core feature.
2. Out of the box features.
3. Automation! VSCode suggests usefull things to you.
4. Integraded console. I love the console in VSCode. It is faster than my 'default' cmd on Windows. For Atom you would have to install a package, that doesn't work so well on Windows.
5. Output logging per Plugin.
6. Setup time. In VSCode I can set up my workspace in under 5 minutes. For Atom I need
7. Plugins work perfect out of the box. This is a mayor one for me. For example: In order to set up Editorconfig you have to adjust mutliple values and plugins to get it work. Plugin creators of Editorconfig for Atom are not to blame: They include a linter, that verifies whether the settings are correct or not.
8. Git implementation. VSCode ships with Git and even if the git packet of vscode doesn't look like much, theres a lot to it. For example you can watch changes inline.
9. Minimap and vertical scrollbar. This feature is much better implementet in VSCode and you don't need an extra plugin.
10. Auto completion. Sass mixins example: @include and you press CTRL+SPACE and VSCode shows you every Sass mixin.
11. Copy paths from open file tab. In VSCode you can copy the path of an file directly when you have it open. In atom you need to select 'show in tree view' and than copy the path or relative path.
12. Tree view. The tree view VSCode automaticly brings you to the current open file by default. This helps when working with components.
13. File search. The file search supports the asterisk so you can search for eg molecule-*.ts.
14. Tasks support. Tasks are integrated in VSCode so eg. for Typescript you can CTRL + SHIFT + B and select tsc: watch - tsconfig.ts.
15. Short waiting time. For example when deleting files or beautifying 20.000 lines of json (Atom hangs up).
16. More releases. Faster feature implementation. Active community.

Our whole DevOps stack consists of the following tools:

• GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
• Respectively Git as revision control system
• SourceTree as Git GUI
• Visual Studio Code as IDE
• CircleCI for continuous integration (automatize development process)
• Prettier / TSLint / ESLint as code linter
• SonarQube as quality gate
• Docker as container management (incl. Docker Compose for multi-container application management)
• VirtualBox for operating system simulation tests
• Kubernetes as cluster management for docker containers
• Heroku for deploying in test environments
• nginx as web server (preferably used as facade server in production environment)
• SSLMate (using OpenSSL) for certificate management
• Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
• PostgreSQL as preferred database system
• Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

• Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
• Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
• Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
• Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
• Scalability: All-in-one framework for distributed systems.
• Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.

Repost

Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku . However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

For a Visual Studio Code/Atom developer that works mostly with Node.js/TypeScript/Ruby/Go and wants to get rid of graphic-text-editors-IDE-like at once, which one is worthy of investing time to pick up?

I'm a total n00b on the subject, but I've read good things about Neovim's Lua support, and I wonder what would be the VIM response/approach for it?

I'm a MERN Stack individual developer. Visual Studio Code auto complete recently started to function poorly, especially with Node.js & Mongoose, and that's why I'm thinking to move from my comfort zone. Do you have any recommendations for me? I have a weak device, MacBook 2011