If you have a crazy idea and the peer reviewers find it worthwhile publishing, it'll make it into publication even if you don't have a GED.
Open Access is a completely orthogonal issue to this.
If you have a crazy idea and the peer reviewers find it worthwhile publishing, it'll make it into publication even if you don't have a GED.
Open Access is a completely orthogonal issue to this.
Often times, the knowledge guild is actually never put down on paper. You, sadly, need to be at a university where people are working on what you want to be able to do anything. Papers are just waypoints.
IMO, there is nothing wrong with companies making a profit from providing access to publicly funded research; the only problems are lack of competition and (IMO consequently) profit margins that society finds unjust.
The former, I think, is being settled. More and more new research is effectively open access. The latter, then, will follow.
And to your second point: there used to be companies that had university-like environments where short-time profits do not rule the day (AT&T, Xerox, Philips Natlab, Apple's ATG). Nowadays, Google and Microsoft Research still have similar groups.
Here's an example. When I did math research last summer at my university, I looked at 16 papers. It took a while to gather these even with my university account with which I obtained the articles for free. If I had to google every single article, it would have taken me much more time - at least double if not triple the time.
In a lot of HN conversations pertaining to computer science research, it appears to me that a lot of folks equate doing computer science research with publishing papers.
I suppose that if your job is to work as a researcher, or as a grad student, or as a professor, perhaps publishing papers is very important.
But in the context of doing research independently (as this subthread seems to be about), why should we care? Isn't the more fundamental point of computer science research to develop new software systems that either do something totally innovative, or improve upon previous systems in novel ways?
(1) What you're solving has already been solved
(2) You have a bug in your solution
(3) You can get feedback from the reviewers such that the system is ultimately improved (this happens more often than you think)
(4) You have actually shown that it works better or just deluded yourself into thinking it does (because you happen to have done a lot of work and are convinced that it was good work).
Submitting a paper for publication is essentially independent verification and validation from (hopefully, but not always) impartial people. If you can convince a committee of peers that what you do is the state of the art and you can show this on some public benchmark, then it's a very different proposition from beating some internal benchmark, which may or may not be well-constructed/biased/etc.
The downside is that you have to write a paper, go through the reviewing process etc (i.e. what a boss at most companies would consider a waste of time).
Now, if you're doing research in biology, then this is a bigger problem. Pubmed is great, especially when you get access to freely available papers, but open access is not the norm yet. The tide is turning though, and I think most (all?) NIH-funded research is supposed to be open access.
However, if you're doing research in biology, not having a PhD is not really the main issue -- you need a lab, money, equipment, mice etc. There's no AWS for biology, sadly, though in fairness it would be a need idea! :)