cross-posted from: https://piefed.jeena.net/post/33729
Rust:
2 days, most of it fighting the compiler.
I did a POC in Rust vs Python. Rust took longer to write, would be harder to maintain by our team, and with numba, the performance difference was small. So we went with Python.
If you are fighting the compiler you are probably trying to write unidiomatic code (maybe Python-like code?).
…and 5 min in chatgpt. Only you spend 3 days making it work because you never understood coding in the first place.
And honestly, even if you do understand coding, you’ll probably spend more time testing the code than it would’ve taken to write and test it yourself.
We had an applicant use AI in an interview, and they made the same mistake twice in 5 minutes, because that’s the code the model spat out. This was someone with several years of experience (I think they even ran a team for a couple years), so they certainly understood coding, they just trusted their tools too much. We even gave them a softball question, “How confident are you that your code is correct? What would you need to feel more confident?,” and their answer was, “I’m 100% confident that it’s correct” when they should have answered, “I’d need to write some unit tests.”
I love C and Assembly as much as the next guy, but implementation time to the optimal solution matters.
“Hardware cycles are cheap. Wetware cycles are expensive.”
- Paraphrased from something I once heard Jacob Kaplan-Moss say but don’t remember his exact wording at PyCon many moons ago.
Then why do Python people insist on having the programmer do so much stuff instead of letting a compiler do it?
Verifying that your different pieces of code actually work together. With a static type system and similar compiler features you can lighten the mental load a lot compared to languages like Python where you need to keep it all in your head.
And something between 1 and 300 minutes in Haskell.
