3 ms·
Lots of things work when your people and processes are good enough. We don't need seatbelts if we never crash. That can lead to problems with scaling your tea
by 01100011 8y ago
Lots of things work when your people and processes are good enough. We don't need seatbelts if we never crash. That can lead to problems with scaling your team if needed, however. At some point you might have to let a moron in, and stronger typing just might be the thing that prevents a catastrophic bug.
I did Python for embedded systems for a year. Python is so expressive and well equipped, but the lack of pre-execution type analysis leaves you vulnerable to severe defects unless your testing coverage is 100%. I would prefer Java over Python just for the safety the compilation step provides(and I don't care for Java). I love programming in Python, but system reliability trumps my personal desires in this case.
- hardwaresofton 8y agoI'm sure you know this already but you might want to check out: - https://docs.python.org/3/library/typing.html https://docs.python.org/3/library/typing.html - http://mypy-lang.org http://mypy-lang.org Also flake8 has also helped -- it's just a linter but using it in conjunction with the typing module and running that in a watch loop in another terminal window has done wonders for me.
- 01100011 8y agoAnd that's awesome, but if you're dealing with a large legacy codebase it will take a while to annotate your code. I love flake8. Properly tuned, it can be a great help. It saved my butt more than once.