4 ms·
Maybe the author just independently came up with this, thought it was cool, and wanted to share? I don't know if "please do a thorough literature review before
by stavros 2y ago
Maybe the author just independently came up with this, thought it was cool, and wanted to share?
I don't know if "please do a thorough literature review before showing me things" is the right sentiment here.
- rkangel 2y ago> Maybe the author just independently came up with this, thought it was cool, and wanted to share? Except that the title ("A New Way to Store Knowledge") is leaning heavily on NEW.
- rakoo 2y agoI'm not sure the paper-like presentation of the article shows that the author was in pure discovery mode, eager to share something new and interesting. My message is an echo to earlier comments of earlier posts that talked about a similar point: nothing is ever new, everything has already been done before. If we tell ourselves we're engineers, we should be studying what came before in order to prove that the new thing is indeed better. That being said, recutils is the standard method of recording data in GNU, and ndb is the standard method of configuring stuff in Plan 9, a system that any proponent of UNIX mindset should know about. I'm not exactly talking about obscure stuff here.
- chipdart 2y ago> I'm not sure the paper-like presentation of the article shows that the author was in pure discovery mode, eager to share something new and interesting. If the author was following a paper-like presentation, the author somehow skipped the section listing relevant prior work. This is something every single journal enforces, as researching prior work is the very first step any author does when they come up with something.
- vineyardmike 2y agoConsidering the article has a “prior art” section, I assume a literature review would be appropriate. My confidence is shaken considering the sparse “prior art” section links to Apple M1 as an example of “fast file systems”.
- tambourine_man 2y agoYeah, this is really weird.
- breck 2y agoIt wasn't clear why I mentioned M1. I updated that. Thank you. https://github.com/breck7/breckyunits.com/commit/61792237c0b81cebecfbcdf2ca38e06f03deb1cb https://github.com/breck7/breckyunits.com/commit/61792237c0b... A number of things have to best fast for this system to be enjoyable to use (at scale) and before the M1 no personal machine I ever tried came close.
- chipdart 2y ago> Maybe the author just independently came up with this, thought it was cool, and wanted to share? That's perfectly fine, but that's besides the whole point. The point is that between coming up with something and implementing it, there should be a step to check if anyone already did something similar. The whole point of researching prior work is to a) don't waste time reinventing the wheel, b) leverage prior work to improve your own ideas, c) make better use of your time by doing meaningful contributions instead of taking a risk on whether you're ripping off someone else's work. That's the absolute basic standard on scientific publishing, for example. If you pick up any paper at all, you'll notice that right after the introduction and summary you get a bibliographical review listing any relevant work that your peers already contributed. When anyone submits a paper, the reviewers can and outright do reject your submission if it fails to adequately contextualize the paper with regards to prior art and related work. One of the points is to ensure the author is not wasting everyone's time with a novel approach to the wheel. More importantly, if an author fails to know what's already there, how can they tell their idea is any good?