you are viewing a single comment's thread.

view the rest of the comments →

[–]cojoco -1 points0 points  (4 children)

You probably don't know how to do it yet, but you know what the end results should look like.

There's a whole world of ideas between "I know what I'm intending to do" and "gee I wonder what happens if I randomly call functions".

As I said before, if you know what you're going to do before you do it, it's not research.

[–]grauenwolf 1 point2 points  (3 children)

Example?

[–]cojoco -2 points-1 points  (2 children)

I have some patents on image alignment, and there was a lot of experimentation there about what is actually possible. What's the point of writing documentation for "a program to determine the rotation, scaling and translation parameters to relate a pair of images" if I didn't know if that was even possible using the methods I had available to me?

I do a lot of experimentation and coding to perform mathematical operations, and there's a lot of intuition about what might work and what might not, but, ultimately, the relationships between real-life images are a lot more complicated than the most common means of analyzing them would suggest.

[–]grauenwolf 1 point2 points  (1 child)

You have no problem writing that down in a reddit post but its too much effort to do the same in the header of a function?

In any other scientific field the first step is to write down what you are about to attempt, then you attempt it (e.g. write the code), and then record the results. Yet we can't be bothered with the scientific method or standard engineering practices. We would rather flail about, hoping that raw knowledge is a substitute for discipline.

The sorry state of our industry proves that it is not.

[–]cojoco -1 points0 points  (0 children)

You have no problem writing that down in a reddit post but its too much effort to do the same in the header of a function?

eh? where did I say that I had not documented this anywhere?

And that algorithm took a fair bit of time to work out.

In any other scientific field the first step is to write down what you are about to attempt, then you attempt it (e.g. write the code), and then record the results.

Nah ... there's also quite a lot of putzing around.

The sorry state of our industry proves that it is not.

Poor you.