←back to thread

On Building Git for Lawyers

(jordanbryan.substack.com)
164 points jpbryan | 1 comments | | HN request time: 0.208s | source
Show context
apozem ◴[] No.42138365[source]
This person is 100% correct that git will never see adoption outside the tech industry.

My partner worked as a veterinarian for several years, and it was fascinating to see how vets use computers. These were brilliant people - I knew three who did literal brain surgery. But they just had zero patience for computers. They did not want to troubleshoot, figure out how something worked or dive deeper. Ever. They didn't care! They were busy saving the lives of people's pets.

It was a good reminder there are many smart people who do not know computers work and do not care to. A good startup acknowledges this reality.

replies(5): >>42138722 #>>42138786 #>>42140065 #>>42145128 #>>42159805 #
deprecative ◴[] No.42138786[source]
I find this excuse depressing. We live in the age of computers. If you don't know how to use one you shouldn't be employed where they're necessary. Rather than making a dumbed down workforce we should be building people's skills up.

Git for normies already exists even MS Word has document versioning. If they cannot be bothered to use the software and technology they need to then they should be unemployed.

replies(7): >>42138938 #>>42138943 #>>42139014 #>>42139055 #>>42139096 #>>42139858 #>>42141616 #
1. NotGMan ◴[] No.42138943[source]
Many developers will get a headache when a more complicated git merge/rebase/conflict happens and git is confusing as hell unless you encountered this issue many times before.

As a dev commit/push/pull is trivial, but may God have mercy on the veterinary who needs to do a complex conflict merge across branches.

If most devs are confused then imagine vets.