←back to thread

On Building Git for Lawyers

(jordanbryan.substack.com)
164 points jpbryan | 2 comments | | HN request time: 0.57s | 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 #
becquerel ◴[] No.42139014[source]
We also live in the age of architecture. Should everyone who drives over a bridge or work in an office know how those things were constructed and how they are maintained? Should everyone be trained extensively on the infrastructure that gets water to their taps?
replies(1): >>42139457 #
consteval ◴[] No.42139457[source]
No, but if you directly use those things for your job, you probably should. For example, if you're a home inspector, you should have decent knowledge about plumbing. Even though you're not a plumber.

If you don't have at least some knowledge, you probably won't be a very good inspector. If you have more knowledge, then you'd be better.

If you require document versioning, you should know, at least a bit, how to use a Version Control Software. You don't need to know the internals, but enough to use it.

replies(2): >>42140512 #>>42159894 #
1. bigfatkitten ◴[] No.42159894[source]
You probably use a cellphone in the course of your work. How much do you know about building and operating a 5G RAN? How about modem and RF front end design?

I assume that if you're not a cellular network engineer, the answer would be "very little".

replies(1): >>42228909 #
2. consteval ◴[] No.42228909[source]
No, I know the basics of how the telephony network works and how wireless phones calls are made. I don't know specific technologies like what makes 5G different from 4G, but I don't need to.

I know that radio waves are sent by towers to me phone and back to create a connection. That's why I can't use my phone in an underground parking garage.

I know what a phone number is and why we need them. I know why international calls are more expensive.

That's basic knowledge about the tool that I have, and which I will utilize in my day to day life.

When I say "you need to have knowledge of computers", I don't mean "write an algorithm an operating system might use for scheduling running processes", okay? I mean, do you know what the internet is? Do you know what an email is? Do you know what shutdown/reboot means? Do you know what a program is? Do you know how to see what is running on your computer?

I don't understand why everyone is fighting me on this. To me this is pretty simple. If you're using a thing and that thing is integral to your job, you should have a high-level idea of how to fucking use it. Why am I blowing up people's minds with this?