3 ms·
Unless they're properly archived along with all their resources as well as only referencing other properly archived material, I'd be very cautious before saying
by IanCal 10y ago
Unless they're properly archived along with all their resources as well as only referencing other properly archived material, I'd be very cautious before saying they're better.
This can be done, but I suspect it is rare whereas it's the norm with a journal article.
- steventhedev 10y agoI think they serve different purposes, and the quality varies heavily across subfields. Academic research will produce a journal article as the primary output, whereas a blog post is typically a side effect of a practical project, and most will contain a link to the actual code. Ultimately, I think they're both good, but they do have different uses.
- IanCal 10y agoI'm still highly concerned about the loss of these things. I very regularly follow links to code that's just gone. The code for research definitely should not only exist in a related of post link. Archiving, for me, is a requirement if you think it should be used over more than a year or so.
- steventhedev 10y agoObviously, having a professional librarian working on archiving data, code, and articles is ideal. However, I've found that the public facing side of journals experience bit rot even faster than most of the older blogs. Of course, there are exceptions, and even the most public figures can decide to delete everything, code included (e.g. _why) Gwern has tackled link rot[0] in an exhaustive way, and may give you a starting point from where to continue. [0]: https://www.gwern.net/Archiving%20URLs https://www.gwern.net/Archiving%20URLs
- afandian 10y agoZenodo is a good example of this, as is Figshare. They allow the assignment of a DataCite DOI to some kind of digital asset (dataset, code, github repo etc) for citation https://zenodo.org/ https://zenodo.org/