Programming

17313 readers

618 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

[email protected]

Unit testing isn't enough. You need static typing too. (evanfarrer.blogspot.com)

submitted 1 year ago by [email protected] to c/[email protected]

11 comments fedilink hide all child comments

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

[–] [email protected] 13 points 1 year ago* (last edited 1 year ago)

Some people bang on about static typing getting in the way of agility

With live/inline static typing checkers in editors (with, eg, VSCode's LSP system), there's IMO an obvious boost to "agility" in preventing minor unforced errors/bugs basically before they're even written. Passing the right arguments to the function? Correctly processed an object or data structure? Function matches the required API? Live type checker will often answer those questions straight away without having to look up or check anything.