Programmer Humor

32581 readers

779 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

[email protected]

188

Before and after programming (piefed.jeena.net)

submitted 5 hours ago by [email protected] to c/[email protected]

45 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] riskable 4 points 1 hour ago (1 children)

without type safety your code is no longer predictable or maintainable

This sounds like someone who's never worked on a large Python project with multiple developers. I've been doing this for almost two decades and we never encounter bugs because of mismatched types.

For reference, the most common bugs we encounter are related to exception handling. Either the code captured the exception and didn't do the right thing (whatever that is) in specific situations or it didn't capture the exception in the right place so it bubbles up waaaaay too high up the chain and we end up with super annoying troubleshooting where it's difficult to reproduce or difficult to track down.

Also, testing is completely orthogonal to types.

[–] [email protected] 3 points 1 hour ago

This sounds like someone who's never worked on a large Python project with multiple developers. I've been doing this for almost two decades and we never encounter bugs because of mismatched types.

Have you worked on major projects in other languages in that time period to be able to compare and contrast?

The last two python projects I had to work on didn't have bugs because of type issues, but it was much harder to come into the codebase and understand what was going on given that you didn't have type information in many many places which forced you to go back and comb through the code instead.