|
|
|
|
|
by NAFV_P
4333 days ago
|
|
> Both of the statements in that link are just tautologies... I do not understand, and there are four statements, not two. > Right. And I'm saying that, in my experience teaching, it's better to teach CS and then let programming be something that kind of just falls out of that naturally, as opposed to focusing on programming itself. Where did I say that the focus should purely be on programming? |
|
If you'd be okay with teaching a CS course without programming, we might be talking past one another.
> I do not understand, and there are four statements, not two.
I'm confused. Maybe you posted the wrong link?
Here are the two comments from the linked post:
> If you cannot code, you cannot check that your ideas work out on a computer.
This is only true when it just reduces to "if you cannot code, you cannot code".
Taken literally, the statement is just blatantly false. You could use a computer to figure out properties of your algorithm or for designing an algorithm without actually implementing and running the algorithm; e.g. for getting closed forms of sums, or for finding/verifying the convergent behavior of a series which the algorithm relies on.
So the statement really is only true if it's a tautology.
> I don't see how that relates to my comment, I specifically referred to 'writing' an algorithm, as in implementing the algorithm in code, not devising the algorithm in the first place.
'writing' an algorithm = implement the algorithm in code
So, substituting into your original statement:
"I fail to see how you could implement the algorithm in code if you don't know how to code."
which is a tautology.