51–60 of 121 posts
Earlier quoted context omitted.
You should consider using LaTeX.
That's cool, but lots of people require .doc. It's just easier to use a word variant.
Clever, very clever. As somebody who has worked full-time, over-time, and essentially in my sleep with Word files, PowerPoints, and highly sensitive bid documentation...yeah, I have to agree working in the cloud for this kind of stuff strikes me as career suicide. Maybe not in your turf, re: software development, but with respect to management, operations and marketing people, there should only be one person with the…
Or you could "Keep Calm and File > Make a copy..." of the Google Doc and share that instead of the original draft. The copy doesn't copy the version history.
I mean, I know how to really whip the donkey spit out of "Compare" and the available tools, but until you've seen just how sideways this stuff can go, there's always room for a professional pest...an expert Proposal Writer...there's so much learned in the trenches that we all have a certain cynicism built up, and that's the fuel that gets the junk in by deadline time.
I find it fascinating to see how much deleting and rewriting the author did on the first two sentences of his Atlantic article. You can see the idea getting rewritten in many ways. Is this a typical way to write a magazine article? I wouldn't have expected so much time revising the opening sentences before getting the rest of the article in place. (But there's probably a lot of variation between writers.)
Reminds me of the submission https://news.ycombinator.com/item?id=557191 where we could see pg's thought process in writing the Founders Visa essay. (the link no longer works)
Earlier quoted context omitted.
That's cool, but lots of people require .doc. It's just easier to use a word variant.
I try my best to break people of that awful habit. I also find that I'm usually happy enough dealing only with people who can manage to open a pdf (or any other non-proprietary format).
I had a friend tell me my CV should be in PDF and locked down to prevent recruiters and others from changing it to something other than the original. I know recruiters are fond of changing things up without informing you.
I broke out in to a cold sweat watching this as I remembered all the times I've inadvertently pasted sensitive stuff in to a document. It's still very cool though, I'll just need to remember to be careful when sharing documents.
I've tried to use a clipboard manager for years to help obviate this sort of issue. I'm currently using ClipMenu on OSX, which hits all the right needs for me. Anyone have a suggestion for Windows?
Earlier quoted context omitted.
I try my best to break people of that awful habit. I also find that I'm usually happy enough dealing only with people who can manage to open a pdf (or any other non-proprietary format).
Yes. I hate receiving documents in .docx or any other proprietary format, especially if I have not agreed to that format prior to receiving them. I like plain text if at all possible. I'll happily receive PDFs because I can view them under Linux/BSD, but others piss me off. People THINK MS Word is the de facto business standard. It isn't. Text and PDF are the standards. Never had issues with either. I had a friend te…
So will document retention specialists trying to foil laywers doing discovery.
So will hackers looking for sensitive information, and security specialists looking to avoid sharing sensitive information.
There probably really ought to be an "erase history" function.
I broke out in to a cold sweat watching this as I remembered all the times I've inadvertently pasted sensitive stuff in to a document. It's still very cool though, I'll just need to remember to be careful when sharing documents.
(make me want to go back and see whether I can see other peoples comments .... hmmm)
Interesting. Is this a side-effect of the old Google Wave design, which had collaborative documents where you could watch your collaborator type in realtime?
Operational transformations are used by both Google Wave (now Apache Wave) and Google Docs [1]. The basic idea is to avoid latency by making sure all edit operations commute, so patches can be applied out of order to get the same result. This is not so different from source control except that merge conflicts are handled differently. Differential synchronization [2] might be easier to implement, though. [1] http://en…
They would then be able to implement sharing without allowing access to the history.
Alternatively, and more easily, they could record the state when someone is given access to the document, and not allow access to operations received by the server before then unless they are granted a separate permission.