- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or # to comment.
When I worked on OpenStack for a few years, 80% of the bugs I fixed were type errors that could have been prevented by Python being staticly typed.
Yeah strong disagree with this meme. 15 years into my career and everything gets a data type.
The only engineers I know who still don’t like strong types are engineers who haven’t lost a weekend due to a stupid type issue. Once you have one or a few of those, you start to like types again.
I remember a javascript library where the was a function that returned, according to the documentation, “a color”. Did it return an object with 3 fields? Were those fields RGB or some other color scheme? Is it a string encoding a color? What format is that string? None of these questions could be answered without just running the code, and analyzing the object you got back.
This describes literally every python contract job I’ve ever had.
ASM doesn’t care about your variable types, because it doesn’t care about your variables. What’s a variable, anyway? There is only address space.
As long as your byte consists of 8 bits.
juniorest of memes
Like any newb, the nuance is lost.
Data types don’t matter, the interface matters.
Lately my approach to dev is “I don’t care about your language feautures, I’m going to treat it like lua and just stuff objects with data and write bare functions to process them”
Unless I need to engineer something complex, everything is dict[any:any].
Man, I love lua, but after switching to a different job on typescript I feel like lua could only benefit with a similar type system. So many bugs avoided just because I know for a fact what a function returns and expects.
