Hacker News new | past | comments | ask | show | jobs | submit login

> At some point you will understand that you will never have absolute and complete axioms from which to build everything on [1], and you have to work with what you have.

To have hardware that displays blue, and code that manipulates blue, you must have a very clear and unambiguous definition of what blue means. Notice I did not say correct, only clear and unambiguous. Your whole point seems to be that words mean what a native speaker of the language understands them to mean, which is useful in linguistics and in the editing or dictionaries, but the context of this discussion is the representation of some concept in symbols that a computer can process, which is a different thing. Indeed, it's possible that the difference between code and 'vibes' will have to be in some way addressed by those very definitions of knowledge and intelligence, so I think these are relevant questions that can't be hand-waved away.






I feel a little blue. Does your code understand that? Can the code function properly in civilization without that understanding?

Da ba di da ba dah, my friend.

The code will function, in the sense of executing, whether the underlying concepts are sufficiently well-understood or not. Considering the ramifications of that statement might lead you to seeing why people want to understand what they're building before they build it.

I gave you the benefit of the doubt that you were asking questions in good faith, but I'm not sure that's true anymore, so good luck.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: