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.
{ r, g, b}, hex code, rgb encoded in some stupid format, types are just helpful. I don’t know why people don’t like them. 30 seconds of creating a class for your type saves you hours of debugging later
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.
{ r, g, b}, hex code, rgb encoded in some stupid format, types are just helpful. I don’t know why people don’t like them. 30 seconds of creating a class for your type saves you hours of debugging later
This describes literally every python contract job I’ve ever had.