I 100% agree with your points. No type checking = no serious job. I have learned enough from Ansible to not ever touch that kind of stuff again. There has bee

I 100% agree with your points. No type checking = no serious job. I have learned enough from Ansible to not ever touch that kind of stuff again. There has been a time that Python was a fringe language, only known by some hardcore nerds. I thought Joel Spolsky had once mentioned that having Python on your resume was a signal of a quality developer, someone who went off the beaten path. Times have changed. Python is now the MS Excel for developers. It shines for quick and dirty data mangling. Unfortunately, that is how a seizable portion of people approach software engineering. My theory is that for some having to do abstract thinking and perform a dry analysis beforehand is an impediment. They can only discover what they want while banging out something. They fix the runtime errors they could catch, and slap some more features on top. Types imply a kind of foresight, and that is what some people really have difficulty with. EDIT: Might sound negative, so I admit that the quick feedback cycle you can get from an interpreter language like php/python is a feature in itself.