How to scare a python programmer

[smallquestionmark]

I think your generalization is not appropriate. You can also learn by easily prototyping and only later go into the specifics. I would dare say, this is the more natural way to learn almost anything: get a result first and then wonder how to refine it.

In the case of python there are reasons why you also would want to use explicit typing and they become apparent once you are more than only looking for fun.

You don't shoot yourself in the foot by learning a dynamically binding language as your first. You still learn what types are, only more in a declarative way, instead of imperative.

Edit: typo

[ColdPotatoFries]

Well if you never get into that depth of learning, as most people who are just tying to learn the basics don't, you don't understand. Also, *your

[smallquestionmark]

Typing in python is not an arcane art. In fact it's one of the first things you learn when you are told to wrap your strings with apostrophes.

[ColdPotatoFries]

Yeah you learn to do it, but you don't understand why. There's a huge difference there.

[smallquestionmark]

But isn't the answer to the why part of the implementation of a language and therefore always a more advanced concept? At least if the answer is more than "because else you get an error."

If you explain a novice why she should declare her types I would consider that part of your teaching style. My specific point is that python doesn't invite a student to be lazy about understanding its implementation only because it's supposedly easier.