Remove visualstudio
article thumbnail

A Minimal Development Environment: Part One

Leading Agile

Most developers today rely on integrated development environments (IDEs) that require a fairly hefty desktop or laptop computer to run, like Microsoft VisualStudio, JetBrains IntelliJ IDEA and the family of language-specific IDEs based on it, Eclipse and numerous IDEs based on it, and so forth. configuration complexity. compatibility issues.

article thumbnail

Software Developers Always Want to Go Faster

Leading Agile

They do all their work inside of VisualStudio or VSCode. If you always use (for instance) resharper in VisualStudio, then you’ll want to get the keystrokes under your fingers so that you don’t have to think about them consciously while you’re working. They work on this application over a long period of time.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Sometimes Less is More

Leading Agile

Here’s a screenshot from a Microsoft blog post dating from 2014, giving a preview of VisualStudio 2015 and Blend. The point isn’t to pick on VisualStudio, but only to illustrate how a typical modern IDE looks when it has several panels open. ” Consider: NET development with VisualStudio on Microsoft Windows.

article thumbnail

A Self-Contained Local Access Point for Workshops

Leading Agile

Configure Nexus for Nuget Packages and VisualStudio. Out of the box, Sonatype Nexus isn’t set up for NPM repositories. See Configuring Nexus as a npm repo in the Sonatype Nexus help docs. Out of the box, Sonatype Nexus isn’t set up for Nuget repositories. See Virtual Nuget Repositories in the Sonatype Nexus help docs.

article thumbnail

A Minimal Development Environment: Part Two

Leading Agile

For some languages, the developer workflow in the minimal environment is actually better than that with a full-featured IDE; notably Scala, Ruby, and COBOL; NET developer experience is comparable to using VSCode; better than using VisualStudio in my opinion. For the most part, the Vim plugins available are not well documented or supported.