As someone who did IT 30 years ago, this isn’t really true. Manuals weren’t very good for direct troubleshooting except that they provided insight into how the device or software works. In my experience problems were mostly solved by people who knew what they were doing, with occasional reference to the old guy who had seen all the weird obscure shit no one else even knew was possible.
There was no manual for the windows registry for example, so when I needed it to not shit the bed on a new motherboard I had to dig into it myself and figure out that if I blew out the PCI bus enumeration windows would realize that it’s gone and rebuild it with the new IDs and such for the new hardware on boot instead of looking for old IDs and eating itself when it couldn’t find them.
30 years ago you would have checked the manual or read the documentation, not much different just a little faster these days
I was doing IT 30 years ago.
Back then you’d post a question on USENET and get an answer back from the guy who wrote the program you were asking about.
30 years ago, manuals were worth the read.
As someone who did IT 30 years ago, this isn’t really true. Manuals weren’t very good for direct troubleshooting except that they provided insight into how the device or software works. In my experience problems were mostly solved by people who knew what they were doing, with occasional reference to the old guy who had seen all the weird obscure shit no one else even knew was possible.
There was no manual for the windows registry for example, so when I needed it to not shit the bed on a new motherboard I had to dig into it myself and figure out that if I blew out the PCI bus enumeration windows would realize that it’s gone and rebuild it with the new IDs and such for the new hardware on boot instead of looking for old IDs and eating itself when it couldn’t find them.