Interesting, but all developers complaining about slow compilation and lose of productivity on a slow computer. But somehow forget about the incremental builds. If your project is correctly structured, you have to build it only once. All future compilations are only on the modules you changed and modules that depend on the changed modules.
So, if you are working on a slow computer and really, really want to do the job, you always can setup your build environment properly and build fast.
Even if you are working on a module that all other modules use, you can create small test project that use this module and work with it, not building the whole project at all.
There is always solution, if you want to make it. And there is always an excuse, if you don't want to make it.
This is indeed true and it can work fine for a few hours. But in real world scenarios that doesn't easily hold. If you work on a specific branch all alone without being bothered, it works. When you have 15 people working on the same project and you need to rebase every couple of hours plus visual studio untrustworthiness that means you either need to keep track of other people changes and rebuild specific modules or rebuild the whole thing. Unit tests are again a good way around but the same problem applied ...rebuilding the test project takes time. I am not complaining but it's a issue I rather not worry about....than being ...oh my *** I need to rebuild again...and I just made coffee
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Interesting, but all developers complaining about slow compilation and lose of productivity on a slow computer. But somehow forget about the incremental builds. If your project is correctly structured, you have to build it only once. All future compilations are only on the modules you changed and modules that depend on the changed modules.
So, if you are working on a slow computer and really, really want to do the job, you always can setup your build environment properly and build fast.
Even if you are working on a module that all other modules use, you can create small test project that use this module and work with it, not building the whole project at all.
There is always solution, if you want to make it. And there is always an excuse, if you don't want to make it.
This is indeed true and it can work fine for a few hours. But in real world scenarios that doesn't easily hold. If you work on a specific branch all alone without being bothered, it works. When you have 15 people working on the same project and you need to rebase every couple of hours plus visual studio untrustworthiness that means you either need to keep track of other people changes and rebuild specific modules or rebuild the whole thing. Unit tests are again a good way around but the same problem applied ...rebuilding the test project takes time. I am not complaining but it's a issue I rather not worry about....than being ...oh my *** I need to rebuild again...and I just made coffee