Max Kreminskithe real value of publishing papers as a software person is that even if your code bitrots in two years, even if your company goes bankrupt in six months, you can still burn a record of what you did into the noosphere for your next-generation mindkin
the true audience of a paper is an enthusiastic undergrad in a country you’ve never been to working on something no one around them cares about twenty years after you’ve already left the field
Not a Spring Onion@maxkreminski
Actually, that computer vision/contour detection algorithm paper (that I tried to reimplement) was also written by a German 30 years ago.
Actually, that computer vision/contour detection algorithm paper (that I tried to reimplement) was also written by a German 30 years ago.
Peter Brett@wakame @maxkreminski Hang on *precisely* which computer vision/contour detection algorithm?
Thanks to my perfectly organized system (I lied, took me a while):
Zamperoni, Piero (1981):
"A note on the computation of the enclosed area for contour-coded binary objects"
(Okay, that's more than 40 years, but I re-implemented it in 2017, so... still closer to 40. 
)
@wakame @maxkreminski Hah, I was wondering whether it was the same German ridge detection algorithm that I had to reimplement in 2010–2012 for my PhD research. Apparently not!
The #ImageProcessing literature is full of papers that give you half of the mathematics you need (incorrectly) and then some pretty pictures of what you might get if you spend 6 months figuring out how to implement it from scratch.
The paper I mentioned contained a list of numbers that (incorrectly, IIRC) described half of the algorithm
Publishing raw data, source code and similar essential artifacts should be a requiremnt for publication...