>no one should be debugging

He literally said those exact words out loud from the audience during a job talk.

And yeah, the total aim and the reason why he might just blurt that out is because a lot of the frustration and esprit de corps of programming is held up in writing software that's more a guess about behavior than something provably correct. Perhaps we all ought to be writing provably correct software and never debugging as a result. We don't. But perhaps we ought to. We don't.

Is control via natural language a doomed effort? Perhaps, but I'd be cautious rather than confident about predicting that.

▲ godelski 5 hours ago | parent [-]

  > He literally said those exact words out loud from the audience during a job talk.

Yes, I even provided the source...

Unfortunately despite being able to provide a summary I'm unable to actually read it for you. You'll actually need to read the whole thing and interpret it. You have a big leg up with my summary but being literate or not is up to you. As for me, I'm not going to argue with someone who chooses not to read

▲ selridge 2 hours ago | parent [-]

I sincerely doubt you produced the source where he asked that question in the middle of someone else’s job talk.

Which is what I was referring to. I read what you wrote, pal. Did you read what I wrote?

	▲	godelski an hour ago \| parent [-]
		`> I sincerely doubt you produced the source` Either I did or didn't. What is not in question is that I provided a source. `> I read what you wrote, pal.` Forgive me for not believing you. I linked a source and you made speculations about what was in it. If you can't bother to read that then why should I believe you read anything else? Reading requires more than saying the words aloud in your head. At least if you want to read above a 3rd grade level. Yes, I'm being mean, but if you don't have the patience to actually read the comment you're responding to you then you shouldn't expect anyone to have the patience to respond to your rude behavior with kindness.