3 ms·

Not all of us have that luxury. Not everyone is on Git, and some employers have in-house version control that sends email notifications at the time of the commi

Not all of us have that luxury. Not everyone is on Git, and some employers have in-house version control that sends email notifications at the time of the commit. Yes, one can always schedule it with a script, but the advice still stands (I'm very much like the OP in that regard).

gbersac 7y ago
> some employers have in-house version control Why would anybody do that ?
- TeMPOraL 7y ago
  Not all programming work is done in hipster web companies following software development trends; there's a lot of employers out there who bought into proprietary VC systems a decade or more ago, and stick with them because of a combination of business needs, legacy requirements and the principle of "if it ain't broke, don't fix it". At one of my previous jobs we had to deal with a proprietary, combined version control and time reporting system that to us, developers, felt like utter garbage. Only later on I learned that it was used by our main customer because it facilitated workflows useful in a mid-to-large corp, and some of our pain points were in fact conflicts between "the developer way" and "the business at large way".
  - jolfdb 7y ago
    Why are you using the word "hipster" to describe industry-standard best-of-breed best-practice tools?
    - TeMPOraL 7y ago
      The word is used to describe companies which tend to be overrepresented in tech communities compared to industry baseline, not tools. As for "industry-standard tools", I find it hard to use this term in our industry. There's a diverse range of practices and recommendations. Git is popular in some subset of the industry (around web in particular), but I'm hesitant in calling it an industry-standard tool. I don't know if there are estimates around the size of it, but there's plenty of proprietary 'shadow' tooling and practices hiding under the surface.
- romwell 7y ago
  >Why would anybody do that ? Because they have good reasons to?[1][2][3] There really is more to version control than Git. [1]https://cacm.acm.org/magazines/2016/7/204032-why-google-stores-billions-of-lines-of-code-in-a-single-repository/fulltext https://cacm.acm.org/magazines/2016/7/204032-why-google-stor... [2]https://www.perforce.com/9-10-top-semiconductor-companies-use-perforce https://www.perforce.com/9-10-top-semiconductor-companies-us... [3]https://code.fb.com/core-data/scaling-mercurial-at-facebook/ https://code.fb.com/core-data/scaling-mercurial-at-facebook/

gbersac 7y ago

> some employers have in-house version control Why would anybody do that ?

TeMPOraL 7y ago
Not all programming work is done in hipster web companies following software development trends; there's a lot of employers out there who bought into proprietary VC systems a decade or more ago, and stick with them because of a combination of business needs, legacy requirements and the principle of "if it ain't broke, don't fix it". At one of my previous jobs we had to deal with a proprietary, combined version control and time reporting system that to us, developers, felt like utter garbage. Only later on I learned that it was used by our main customer because it facilitated workflows useful in a mid-to-large corp, and some of our pain points were in fact conflicts between "the developer way" and "the business at large way".
- jolfdb 7y ago
  Why are you using the word "hipster" to describe industry-standard best-of-breed best-practice tools?
  - TeMPOraL 7y ago
    The word is used to describe companies which tend to be overrepresented in tech communities compared to industry baseline, not tools. As for "industry-standard tools", I find it hard to use this term in our industry. There's a diverse range of practices and recommendations. Git is popular in some subset of the industry (around web in particular), but I'm hesitant in calling it an industry-standard tool. I don't know if there are estimates around the size of it, but there's plenty of proprietary 'shadow' tooling and practices hiding under the surface.
romwell 7y ago
>Why would anybody do that ? Because they have good reasons to?[1][2][3] There really is more to version control than Git. [1]https://cacm.acm.org/magazines/2016/7/204032-why-google-stores-billions-of-lines-of-code-in-a-single-repository/fulltext https://cacm.acm.org/magazines/2016/7/204032-why-google-stor... [2]https://www.perforce.com/9-10-top-semiconductor-companies-use-perforce https://www.perforce.com/9-10-top-semiconductor-companies-us... [3]https://code.fb.com/core-data/scaling-mercurial-at-facebook/ https://code.fb.com/core-data/scaling-mercurial-at-facebook/