Back when not every question had an answer

I got my first real computer around 1982 as well, a Heathkit/Zenith Z-100. Thinking back, I'm amazed at the amount of high quality documentation that came with it. Full schematics, lengthy component level trouble shooting workflows, s-100 bus signaling documentation, component sources, multiple manuals for dos, 8086 and 8085 assembly, qbasic, cp/m, ande each compiler's docs took 2 or 3 3 ring binders.<p>One time we had trouble with it and had to take it to the dealer, who after discussing the problem with us showed us how he tracked down a poor solder joint and taught me (at 9 years old) how to use a wick to remove the solder and replace it.<p>There was also a local user group that drew 50-100 folks a month and always had 1-2 technical talks, and at least a dozen local bulletin boards that were frequented by well educated users and engineers.<p>My most recent computer came with a tiny brochure about how to power it on, and the user forums primarily contain copypasta about repairing disk permissions or resetting the SMC.<p>So, you know, there are plusses and minuses.

The problem shifted from "solution is hard to find" to "solutions are abound, but its hard to find the best". Github has lots of code, and its really difficult to tell what are the best solutions (and of course, there's the whole issue of marketing, where some stuff that show up highly on google or github searches aren't the best but rather the most highly marketed)

On the contrary I feel great pity for people who grow up only knowing an entirely searchable world. There was so much magic and excitement when things were unknown, secret, mysterious.<p>Specifically trying to solve the kind of problem discussed by the OP, yes it was frustrating as hell but it taught tenacity, resourcefulness, and was ultimately SO satisfying when you figured it out.<p>Now you just google and get pissed if the first result doesn't have a copy/paste answer to your problem.

This article reminds of me of Chris Goggans' closing editorial in Phrack 48 [1] where he made a similar point about how much things had changed with regards to being able to access and learn about computers:<p><pre><code> "In this day and age, you really don't have to do anything illegal to be a hacker. It is well within the reach of everyone to learn more, and use more powerful computers legally than any of us from the late 70's and early 80's ever dreamed. Way back then, it was ALL about learning how to use these crazy things called computers. There were hundreds of different types of systems, hundreds of different networks, and everyone was starting from ground zero. There were no public means of access; there were no books in stores or library shelves espousing arcane command syntaxes; there were no classes available to the layperson. We were locked out." </code></pre> [1] <a href="http://www.phrack.org/issues.html?issue=48&#38;id=2#article" rel="nofollow">http://www.phrack.org/issues.html?issue=48&#38;id=2#article</a>

I would say that finding solutions to problems on the internet is still far from moving beyond its infancy. We are very lucky, but there is much more to come.

I think the problem has transformed to "how best to state a problem to find the best solution"

Not to complain about the information richness of the modern Internet, but it's gradually becoming more difficult to find useful information, as more and more real content is pushed aside by advertising.<p>Nothing annoys me more than to click a search result link, only to be taken to one of those parasitic sites that pretends to have useful content through the simple device of including a lot of words with no relevance to its actual content. Inevitably such a site is ranked higher in the search results than one with real information.

Good information is still scarce. That is why self R&#38;D is the best method to collect quality data. Building a search engine has reay opened my eyes to this. There is a lot of bad data. Nowadays, I think the effort is more on understanding which data is valuable and trustworthy. Which simply takes more effort than findings things out by yourself. Reason why I don't search github for good python code, but rather read/view videos about python directly and learn how to write good code by myself.

If you find answers that easy, then you are asking the wrong questions. Every time I have asked a question on the internet about programming, it has never been answered and I had to figure it out myself. Nobody will be answering the real tough questions about programming on the internet.<p>I agree that the easy basic questions are all over the internet but once you get beyond fundamentals the answers are hard to find with that method.

You know, I had this same exact problem with TI-BASIC on the TI-99/4A. Try as I might to follow the documentation's examples, I couldn't open files. (Keep in mind these files were on tape!) 20 years on I never did figure it out…

You really don't have to go back that far. There was no Stack Overflow in my VB and C days (1995/1996). You bought a huge reference book.

&#62; Let me remind you young whippersnappers what looking for knowledge was like before the Internet<p>What, like, teenagers? Because practically everyone 25 or older, arguably everyone older than 20, knows what it was like to search for information without the web.