4 ms·
>you know how it works - you can see the algorithm right there in front of you. Seeing the algorithm in front of you doesn't mean you know how it works. It's g
by famouswaffles 3y ago
>you know how it works - you can see the algorithm right there in front of you.
Seeing the algorithm in front of you doesn't mean you know how it works. It's gibberish code. If you'd never learnt C or any other programming language in your life, i could show you the C Code for a popular application. You could inspect it all you like. You will still understand nothing. The best you can do is, "this code is running this application".
In the real world, you can just pick up a C book and start learning. In this instance, no one on earth has learnt C and there are no books on it.
and neural network calculations are not just one unvarying "algorithm"
- kybernetikos 3y agoKnowing the algorithm literally means that you could theoretically reproduce it yourself, step by step (absent practical worries about longevity). Each of the steps is simple and well understood. What to do at each step is simple and well understood. What more is there to understand?
- famouswaffles 3y agoBy that definition, i know COBOL too since i can look up programs coded in it. I can reproduce the program too by hand-typing it and running it elsewhere. Banks should hire me asap /s. I genuinely don't get what is so hard to understand here. You don't know the algorithm. You can see it. That's all. You don't suddenly understand information just because you can see and copy it. Would certainly be nice though.
- kybernetikos 3y agoWhat I'm trying to work out is what you mean by 'understand'. When it comes to an algorithm, what is it that you need to know beyond how to execute it in order to believe you understand it?
- famouswaffles 3y agoBeing able to make predictable changes directly to the algorithm would be a starter.