4 ms·

> These are developers that can make code work, but take Visual Studio away from them and they cease to be developers. Ha, during my brief stint at a windows-s

by s_kilk 11y ago

> These are developers that can make code work, but take Visual Studio away from them and they cease to be developers. Ha, during my brief stint at a windows-shop after graduating, I did meet a few who couldn't get their heads around the concept of having a build happen without someone clicking a green triangle button in VS.

UK-AL 11y ago
Considering the .NET stack has a heavy bias towards CI, that's hard to believe.
- s_kilk 11y ago
  It probably varies by geography, but the .Net scene I was in really didn't have a bias toward CI at all (or testing, or almost any decent development practices). I wont argue about it, our experiences differ, and that's cool :)
- dan_b 11y ago
  You'd be surprised. There's a lot of shops out there who have never heard of CI/CD/Automated Tests/etc.
- zo1 11y ago
  There is nothing inherent about the .Net stack that makes it biased or preferential-towards CI. Other than the fact that you can "do it" in a CI context, I can't think of anything else. Care to enlighten me? Bear in mind, a lot of .Net developers don't even know it's possible to compile their projects outside of Visual Studio. Msbuild, Nant, csc.exe, "what are those?"
  - UK-AL 11y ago
    The standard for .NET shops is TFS. When you create a TFS project you setup CI and automated builds. "Bear in mind, a lot of .Net developers don't even know it's possible to compile their projects outside of Visual Studio. Msbuild, Nant, csc.exe, "what are those?" There's probably plenty of java developers like that as well.
    - mrweasel 11y ago
      >The standard for .NET shops is TFS I've never seen Team Foundation Server in a .NET shop. It's either been SVN, Git or Perforce. That being said I think it's very individual, but many small companies won't pay for TFS, they barely want to pay for Visual Studio Professional/Enterprise edition
      - tsax 11y ago
        I've worked at a large financial company (everyone would recognize the name) and TFS was the main build system.
organsnyder 11y ago
Those sorts of developers exist on every platform. The trendy platforms are simply too new for non-adaptable developers to have yet made themselves visible.
raverbashing 11y ago
As someone who has done some stuff in Mono this is funny

by s_kilk 11y ago

UK-AL 11y ago

Considering the .NET stack has a heavy bias towards CI, that's hard to believe.

s_kilk 11y ago
It probably varies by geography, but the .Net scene I was in really didn't have a bias toward CI at all (or testing, or almost any decent development practices). I wont argue about it, our experiences differ, and that's cool :)
dan_b 11y ago
You'd be surprised. There's a lot of shops out there who have never heard of CI/CD/Automated Tests/etc.
zo1 11y ago
There is nothing inherent about the .Net stack that makes it biased or preferential-towards CI. Other than the fact that you can "do it" in a CI context, I can't think of anything else. Care to enlighten me? Bear in mind, a lot of .Net developers don't even know it's possible to compile their projects outside of Visual Studio. Msbuild, Nant, csc.exe, "what are those?"
- UK-AL 11y ago
  The standard for .NET shops is TFS. When you create a TFS project you setup CI and automated builds. "Bear in mind, a lot of .Net developers don't even know it's possible to compile their projects outside of Visual Studio. Msbuild, Nant, csc.exe, "what are those?" There's probably plenty of java developers like that as well.
  - mrweasel 11y ago
    >The standard for .NET shops is TFS I've never seen Team Foundation Server in a .NET shop. It's either been SVN, Git or Perforce. That being said I think it's very individual, but many small companies won't pay for TFS, they barely want to pay for Visual Studio Professional/Enterprise edition
    - tsax 11y ago
      I've worked at a large financial company (everyone would recognize the name) and TFS was the main build system.

organsnyder 11y ago

Those sorts of developers exist on every platform. The trendy platforms are simply too new for non-adaptable developers to have yet made themselves visible.

raverbashing 11y ago

As someone who has done some stuff in Mono this is funny