Programming

17759 readers

835 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

snowe

Ategon

[email protected]

"How types make hard problems easy" (or at least reduce cognitive load over time) (mayhul.com)

submitted 3 days ago by [email protected] to c/programming

12 comments fedilink hide all child comments

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

[–] [email protected] 17 points 3 days ago (1 children)

I can often implement 80% of a new feature without ever running the code.

I really love how they then go and invent their own TDD acronym to justify this. Types are proofs, and they replace a whole category of borderline superficial tests with useful assertions, but claiming that you implement a % of a feature when you haven’t once verified it is… a reason I regularly cuss at code and remain employable. Keep it up.

[–] [email protected] 16 points 3 days ago

They probably mean "not running" as "I've written the types and the static type checker is not giving an error"