4 ms·

> Presentation Final Final [2].pdf Alexey - please make sure to use 'Copy of Presentation Final Final [2] (Matt's version) (Copy).pdf' going forward. Presentat

> Presentation Final Final [2].pdf Alexey - please make sure to use 'Copy of Presentation Final Final [2] (Matt's version) (Copy).pdf' going forward. Presentation Final Final [2].pdf is out of date. Thx.

C1sc0cat 6y ago
ROTFL - I think a lot of younger workers especially in the marketing side might have a rude shock if they had to face an ISO 9000 / BS5750 Audit. Joking aside WFH makes these sort of problems even worse I have considered suggesting we make all documents source controlled and use git to handle check in and out.
- rorykoehler 6y ago
  You don't you collaborative tools like drive or office365?
  - C1sc0cat 6y ago
    Doesn't solve the "Copy of Presentation Final Final [2] (Matt's version) (Copy).pdf" problem though. And trying to get people to use office 365's scs is going to be hard and if all your technical docs are in git makes sense to use on scs
    - rorykoehler 6y ago
      How doesn't it solve that problem? It's 100% solved it where I work.
palsir 6y ago
And there are solutions to this. From what I understand (which isn't very much), the SolidWorks (a 3d CAD tool) team has their own version control system, called PDM, which works with the Microsoft office suite. next is organizations getting over the hurdle of educating people how to use version control. Also - I think the current generation of office stores everything in XML, which can then be processed through git, svn, etc.
- slaymaker1907 6y ago
  It is XML, but it is compressed into a zip file.
- hemogloben 6y ago
  I thought this about Eagle's[1] project storage switching to XML; I figured it would allow us to store projects and libraries in git and easily branch / merge changes etc. It was a nightmare. XML does not work well in git.[2] I even thought I could resolve some of the issues by sorting elements so they'd be in a consistent order, but none of the elements had guuids or anything to allow me to do that. 1: http://dangerousprototypes.com/blog/2010/10/14/eagle-open-xml-format-for-schematics-pcbs/ http://dangerousprototypes.com/blog/2010/10/14/eagle-open-xm... 2: https://blog.joepairman.com/2016/11/26/xml-in-git-mercurial-watch-out-for-merges/ https://blog.joepairman.com/2016/11/26/xml-in-git-mercurial-...
  - palsir 6y ago
    Ah, good to know. I have had that thought in the back of my head for a little while with my own eagle projects, thanks for making the mistake for me!

C1sc0cat 6y ago

ROTFL - I think a lot of younger workers especially in the marketing side might have a rude shock if they had to face an ISO 9000 / BS5750 Audit. Joking aside WFH makes these sort of problems even worse I have considered suggesting we make all documents source controlled and use git to handle check in and out.

rorykoehler 6y ago
You don't you collaborative tools like drive or office365?
- C1sc0cat 6y ago
  Doesn't solve the "Copy of Presentation Final Final [2] (Matt's version) (Copy).pdf" problem though. And trying to get people to use office 365's scs is going to be hard and if all your technical docs are in git makes sense to use on scs
  - rorykoehler 6y ago
    How doesn't it solve that problem? It's 100% solved it where I work.

palsir 6y ago

And there are solutions to this. From what I understand (which isn't very much), the SolidWorks (a 3d CAD tool) team has their own version control system, called PDM, which works with the Microsoft office suite. next is organizations getting over the hurdle of educating people how to use version control. Also - I think the current generation of office stores everything in XML, which can then be processed through git, svn, etc.

slaymaker1907 6y ago
It is XML, but it is compressed into a zip file.
hemogloben 6y ago
I thought this about Eagle's[1] project storage switching to XML; I figured it would allow us to store projects and libraries in git and easily branch / merge changes etc. It was a nightmare. XML does not work well in git.[2] I even thought I could resolve some of the issues by sorting elements so they'd be in a consistent order, but none of the elements had guuids or anything to allow me to do that. 1: http://dangerousprototypes.com/blog/2010/10/14/eagle-open-xml-format-for-schematics-pcbs/ http://dangerousprototypes.com/blog/2010/10/14/eagle-open-xm... 2: https://blog.joepairman.com/2016/11/26/xml-in-git-mercurial-watch-out-for-merges/ https://blog.joepairman.com/2016/11/26/xml-in-git-mercurial-...
- palsir 6y ago
  Ah, good to know. I have had that thought in the back of my head for a little while with my own eagle projects, thanks for making the mistake for me!