[consteval]

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.

[ulbu]

a home inspector inspects homes. a veterinarian inspects animals. she does not inspect computers.

you could restrict their software movements to the bare essentials for their work and they’d be happier for it. hell, i’m sure most would be happier with no gui if the interface provided them with only what they need. and most need just a place to create a document, type it in, commit the document, view it, and relay it to storage or another user. then a browser to look things up.

but we live in the age of general-purpose computing where people need to use general programs thoroughly unadapted for their specialized jobs, forcing the user to coordinate multiple contexts, which should really be coordinated by the machine. most jobs could be done with nano and sendmail. add an form input field editor and selector and it’s golden. if something else is needed, it should be one command away.

it’s not for them to inspect computers. it’s for devs and enterprises to create software systems such that the tech-naive user would have no need to ever touch anything outside of what they need.

[consteval]

A veterinarian should also be able to inspect their tools, to some extent. I expect a homebuilder to at least kind of understand how a hammer works.

A computer is a tool. I don't expect them to know everything, but I do expect them to know a little.

[Teever]

Exactly.

Ive started realizing that specialists who lack general skills like computer knowledge o the ability to learn things outside of their domain as needed are themselves tools.

If you can't understand things outside of a very narrow slice of specialization you're just a tool to be used by generalists.

[bigfatkitten]

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".

[consteval]

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?