[ReflectedImage]

"If typechecking would actually introduce bugs, it'd be better not doing it right?"

Correct if you misapply a tool to the wrong situation you get poor or negative results.

The right tools are unit testing, integration testing, uat and automated whole system testing.

[bombolo]

That seems to completely forget the fact that libraries exist, that A LOT of bugs can happen calling libraries, and that you're not really supposed to unit test libraries, they are supposed to have their own tests.

[ReflectedImage]

Unit tests test the parts of the library that are in use implicitly.

As does integration testing, user acceptance testing and whole system testing (QA engineers, frontend testing, etc.)

Nothing has been forgotten. Python isn't Java, nor should you develop your Python code as if it were Java. Python has it's own software development practices that take advantage of the language's strengths including dynamic typing.

It you don't know how to work with a dynamically typed language properly, that's on you. And I guarantee you will get poor results pretending it's a statically typed language.

[bombolo]

> It you don't know how to work with a dynamically typed language properly, that's on you. And I guarantee you will get poor results pretending it's a statically typed language.

Insulting me won't make you a better developer nor a better person :)

Getting started with type hints is not easy, but it can be done incrementally and it is worth it.

If you haven't used them, please learn before insulting people who are more experienced than you.

[ReflectedImage]

Using static typing in a dynamically typed language will always make you a poor software engineer who doesn't understand the tools they use nor the engineering trade-offs involved.

But sure continue to hammer in nails with a screwdriver, it's only your own time you are wasting.

And I've noticed you failed to provide any sources whatsoever for your nonsense.

[bombolo]

> And I've noticed you failed to provide any sources whatsoever for your nonsense.

As opposed to your 404 "peer reviewed paper"? :D

> Using static typing in a dynamically typed language will always make you a poor software engineer

Making broad statements about things you've never used yourself just makes you an arrogant guy on the internet who is quite likely to be a poor software engineer with a big ego.

[ReflectedImage]

I'm sure you could find it on Google Scholar. I'm not your personal googler.

My wages disagree with that statement. But hey, we can't all be 10x.

Did it ever occur to you to think about why people use scripting languages or what advantages they have over regular programming languages?

Of course not, you are used to statically typed languages and are blinded to the idea that there are other ways to develop software.

I'm guessing you did a search for sources to backup what you are saying and found out pretty quickly that they don't exist.

Static typing in Python is a practice based entirely in common ignorance not reality.