> And we'll know it's correct when most of the sentences sort of sound correct?
Explain this in more detail?
This is like saying that we know code is correct (bug free) because most of the lines sort of look correct. It's not /inherently/ an untrue statement, but it doesn't match up with any sort of real world experience.
To know that something is correct in a useful sense, you need it to not only have no obvious inconsistencies and errors, you also need a way to exclude non-obvious inconsistencies and errors. What's the plan?
Explain this in more detail?
This is like saying that we know code is correct (bug free) because most of the lines sort of look correct. It's not /inherently/ an untrue statement, but it doesn't match up with any sort of real world experience.
To know that something is correct in a useful sense, you need it to not only have no obvious inconsistencies and errors, you also need a way to exclude non-obvious inconsistencies and errors. What's the plan?