Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Using Microsoft Word with Git

blog.martinfenner.org

Post reply on HN
Print view View original

131–136 of 136 posts

Re: Using Microsoft Word with Git

#131

Post by fredguth »

Icathian wrote: post #66
michihuber wrote: post #34

Earlier quoted context omitted.

I agree with this being about workflows, not documents, but isn't branching and merging a workflow and storytelling tool? It allows multiple people to work in parallel (and in private). When somebody sends a pull-request eventually, they are presenting a story of changes that they want to get into the document and people can discuss them and approve them individually. (Of course, git the tool isn't necessarily suitab…

I think the issue is that parallel workflow is a bridge too far for the current legal profession. They do sequential and they like it. A tool that makes the sequential workflow better will gain more ground than one that tries to change the process whole hog.

But the workflow only "looks" sequential, isn't it? In many stories told here a user may have inadvertently revert clauses to old versions and this can be missed. This happens because it is also an asynchronous work.

Re: Using Microsoft Word with Git

#132

Post by fredguth »

jimmygrapes wrote: post #70
Icathian wrote: post #66

Earlier quoted context omitted.

I think the issue is that parallel workflow is a bridge too far for the current legal profession. They do sequential and they like it. A tool that makes the sequential workflow better will gain more ground than one that tries to change the process whole hog.

I have worked on several hundred of these types of contract processes in the last few years, and you are absolutely correct: sequential is where it's at for these situations. I have, however, encountered a few situations where time was an issue so I had two or three different versions out to different parties at the same time, and then merged the proposed changes where possible and sent out alternate versions where t…

The anecdotes told here suggest that most think their work is sequential, while because a lot can happen asynchronously, hell situations happen all the time. Do you agree?

Re: Using Microsoft Word with Git

#133

Post by tatersolid »

brudgers wrote: post #80
atoav wrote: post #35

Earlier quoted context omitted.

As someone who is at the intersection of tech and arts one of the things I like about using git in projects is that it is very clear what is the latest official defintive final variant of a piece of data and you don't have to ask anybody to get it. When I worked as a VFX freelancer I was amazed at the number of hours (=money) burned by marketing agencies who didn't manage to give me the definitive variant for a simpl…

you should choose the defaults of your communication culture in such a way, that it works under the absolute worst conditions The defaults are sensible. Throw money at it and pay someone enough to sort things out and get it done, e.g. you as a freelancer get a data dump and ask the right question and the problem is solved. Sure it costs money. But everything costs money. Git works great among peers. But most organiza…

> And the boss doesn't have to give a shit about which draft is the latest because the boss is the boss.

As a boss myself I have to say: I totally give a shit. Salaries are my company’s #1 expense by a wide margin. I don’t want my staff spending their time manually merging docs received via email when there are much better solutions out there. I hire people because they are smart and can get shit done that makes money, not because I want servants.

This is the killer app for Office 365 and google docs: stop wasting time emailing shit around, one canonical version even outside of company walls.

Re: Using Microsoft Word with Git

#134

Post by tatersolid »

Timpy wrote: post #31
MarcScott wrote: post #28

I really don't understand how Word remains so popular. It was created at a time when few people had internet access, and was designed to produce printed documents. It was the perfect tool to write newsletters, flyers, articles, academic papers and manuscripts. The world has moved on though, and I fail to see Word's relevance today, other than the sheer number of people that are familiar with it. Word is expensive, pr…

In my opinion the issue is path dependency. Everybody in my generation grew up with Microsoft Office free on every installation of Windows, and teaching everyone new efficiency software is costly. It looks like Google is trying to win the next generation and Chromebooks are taking over the classroom. When today's youth grow up I wouldn't be surprised to Google Docs as the new standard.

> Microsoft Office free on every installation of Windows

Microsoft Office is quite useful, and probably good value for money. But it has never ever been free, and I’ve been buying it for work and home since Office 4.x on Windows 3.1 was the new hotness.

Re: Using Microsoft Word with Git

#135

Post by coffeeling »

GordonS wrote: post #103
CJefferson wrote: post #61

Earlier quoted context omitted.

I agree that word is bad, but I don't think we have a great replacement yet. Markdown -- standard markdown isn't expressive enough (no tables for example), there are lots of extensions but none which are "standard". LaTeX -- doesn't produce accessible documents, so is a non-starter in lots of areas (seriously, the PDFs it generates are some of the worst around when it comes to accessibility. Word's are amazing).

> I agree that word is bad If we put aside the Word file format, and maybe the ribbon, is Word bad though? I've been using it for decades, and have tried OpenOffice and LibreOffice too over the years - nothing comes close to Word. Markdown is not suitable for "normal" users, but as a developer, I've come to prefer markdown for technical documentation and such (especially where I want a history, diffs etc), but I stil…

> > I agree that word is bad

> If we put aside the Word file format, and maybe the ribbon, is Word bad though?

Is the ribbon bad, though, or are we just living through 2003 era UI shock for 13 years now?

I lambasted the ribbon as was fashionable back then, but actually using it in 2020?

It's good. Like, legit amazing UI design. Makes it easy to peck through menus and find what you want. Structures chords for power users, and importantly makes those chords visually discoverable. I've found a pile of good keyboard shortcuts just by starting to slowly press a chord on the ribbon.

It's great for mouse users. It's great for noobs just learning the ropes. It's great for keyboard users who already know their stuff. It's amazing at facilitating the learning process into knowing your stuff

It's been great for 17 years. Do we still have to pretend it sucks because we were used to a different way of doing things?

Re: Using Microsoft Word with Git

#136

Post by GordonS »

coffeeling wrote: post #135
GordonS wrote: post #103

Earlier quoted context omitted.

> I agree that word is bad If we put aside the Word file format, and maybe the ribbon, is Word bad though? I've been using it for decades, and have tried OpenOffice and LibreOffice too over the years - nothing comes close to Word. Markdown is not suitable for "normal" users, but as a developer, I've come to prefer markdown for technical documentation and such (especially where I want a history, diffs etc), but I stil…

> > I agree that word is bad > If we put aside the Word file format, and maybe the ribbon, is Word bad though? Is the ribbon bad, though, or are we just living through 2003 era UI shock for 13 years now? I lambasted the ribbon as was fashionable back then, but actually using it in 2020? It's good. Like, legit amazing UI design. Makes it easy to peck through menus and find what you want. Structures chords for power us…

I said that because I know the ribbon is still contraversial, and some people still don't like - personally, I've come to like it, if not love it as you have.
Post reply on HN