5 karma · joined November 5, 2021
Just because it's been asked before doesn't mean that the people answering it are the same etc etc
Or was that a lie.
TDD only catches assumed known failure modes.
I can't find the name of it, sorry.
I fully support what you're doing. I am not fussed with someone's back stories about how their great grandmother's auntie's friend had her hair dyed when walking her dog to pick cherries... Blah blah... Just want the recipe and method
But unfortunately... Advert revenues are a thing.
This site is almost as bad as Reddit, go with the status quo and polish each others ego or you're downvoted or flagged.
Your comment is kind of meaningless drivel with abstruse language.
But it's wrapped up in such complicated rhetoric that no one questions it (perhaps less cares...)
I shouldn't berate it though. It pays the bills..
Much better off just going in to industry. People praise PhDs too much. No one at work knows of mine. It's not on my CV either.
What is awful is when someone with a PhD in, say, biology uses this as leverage in a completely unrelated field (data science). Malicious ambiguity...
You're not an authority on something just because you have a PhD, certainly not an authority on everything. This is, damagingly, how many behave... You're barely scratching the surface at that level. It warrants a lifetime of work to get anywhere near the level of respect some put up on them. I guess that speaks volumes to the general level of insight into education by most..
If you want performance, or to apply more rigorous (read: enterprisey) development practices, you really are better off looking elsewhere.
However, you can get a Data Science python developer to front their code behind an API with minimal ceremony.
Type safety does not exist in Python. Type hinting does not solve this problem, neither does Pydantic. These are bandaids for huge shortcomings of using the wrong tool for the job.
It's always a matter of choosing the least worst solution with Python, and additionally patching over shortcomings of the language with afterthought-tooling.
I believe we are limited by our own experience, a lot of software is built upon the idea that problems are solved through procedural steps rather than a series of transformations.
This does not lend itself to thinking in a way that aligns nicely with functional programming.
Future generations will naturally think in ways unfathomable to you and I, and this will cause a shift in the fundamental approaches to software development.
At some point you have to admit to yourself that it's the wrong tool for the job, when is this going to be?
Dependency/environment management is poor as well given how popular the language is. I believe it's popularity is similar to that of PHP in the past; flooded with carefree users.
I would strongly advise against using python for anything other than PoC/experimental endeavours.
It's a scripting language, and should be used as such.