News for hackers. Stuff that matters.
Re:TFS: A file system built for performance, space efficienc... by flukus on Sunday May 21, 2017 @08:04PM (#14390001)
The more you discourage checking in the harder merging becomes.
Re:TFS: A file system built for performance, space efficienc... by pjmlp on Monday May 22, 2017 @12:37AM (#14391030)
In some type of enterprise projects I am quite glad that merge never takes place.

I don't want to have a CI build that is green only a few days when all planets are aligned.

Re:TFS: A file system built for performance, space efficienc... by flukus on Monday May 22, 2017 @02:35AM (#14391427)
> In some type of enterprise projects I am quite glad that merge never takes place.

Surprise! Now you have 2 versions of an app to support, with twice the resource requirements.

Re:TFS: A file system built for performance, space efficienc... by pjmlp on Monday May 22, 2017 @02:50AM (#14391495)
No I don't.

I and everyone else on the team enjoys the fact that broken code produced by offshore developers that should have been fired in first place, never touches the official development repository.

Those developers will eventually produce something that passes the unit tests and gets merged, instead of borking the build for weeks.

Should the process done in another form with code reviews and such, yes but that isn't how many enterprise projects are managed.

Note that I am only referring to those that can't learn to code even if we ELI5 them.

There are others on the offshore teams that are highly skilled, but like us onsite, cannot do anything to change the rules of the game.