128 karma · joined April 20, 2022
* Was overwhelmingly slower than mypy
* Had a few hundred more false positives. I gather from reading their philosophy afterward that this was on purpose. Rigid dogma > doing the right thing in the circumstance in their opinion.
* Did not find any actual bugs, whereas mypy identified 3 errors that lead to fixing real issues AND had fewer false positives, due to its better understanding of python code.
* Comically overweight with its typescript dependency.
My first impression of it was of a very low quality, over engineered project prioritizing noise over signal. Looking forward to trying out the astral typechecker as well.
1. Constantly complaining. This is like a high-visible fake proxy for "high quality".
2. Highly opinionated. In order to get your 3rd rate projects through you need to fight tooth and nail for whatever arbitrary set of things you are pushing.
Engineering prowess and the properties from the article are nowhere on the list. The vast majority of principal+ engineers and essentially all upper management I have worked with have these two traits. When you run into an exception it's a blast of fresh air and a wonder they got past senior engineering roles. As a disclaimer my sample size is 2 companies.
It causes so many entirely unnecessary issues. The conda developers are directly responsible for maybe a month of my wasted debugging time. At my last job one of our questions for helping debug client library issues was “are you using conda”. And if so we just would say we can’t help you. Luckily it was rare, but if conda was involved it was 100% conda fault somehow, and it was always a stupid decision they made that flew in the face of the rest of the python packaging community.
Data scientist python issues are often caused by them not taking the 1-3 days it takes to fully understand their tool chain. It’s genuinely quite difficult to fuck up if you take the time once to learn how it all works, where your putbon binaries are on your system etc. Maybe not the case 5 years ago. But today it’s pretty simple.
I would make the exact opposite claim. Since Covid and working from home the quality of my teams’ collaboration and decision making quality has gone through the roof. Quality of promotions has gone up significantly, you’re no longer rewarded for just being the loudest monkey in the room with an opinion. The only metric that has suffered in any measurable way is onboarding and mentoring young engineers who do not yet know how to learn. You have to be much more active and sensitive to their state. In general I look back at that era of my career as archaic. Everyone that wants to go back to that way of working seems dinosaurs who operate on their feelings rather than the data of how quality work is done.