GosuCoder (@gosucoder) 's Twitter Profile
GosuCoder

@gosucoder

Programmer that Loves to Share Things on YouTube especially about AI and new technology!

ID: 898600278584426496

calendar_today18-08-2017 17:39:36

383 Tweet

622 Followers

31 Following

GosuCoder (@gosucoder) 's Twitter Profile Photo
GosuCoder
@gosucoder

3 months ago

Before watching I’m going to guess. 1. Merging/conflicts 2. PRs chaining off another 3. No dependency file locking, Perforce had this many years ago 4. Large binary files, it’s better now but in Perforce back in the day I could control how many revisions to keep of large binary

Before watching I’m going to guess. 1. Merging/conflicts 2. PRs chaining off another 3. No dependency file locking, Perforce had this many years ago 4. Large binary files, it’s better now but in Perforce back in the day I could control how many revisions to keep of large binary