Unit testing isn't enough. You need static typing too.

Comments

• beefsack@lemmy.world ⁨1⁩ ⁨year⁩ ago

  I remember my time doing Ruby.

  The Ruby community was really great at doing automated testing and it’s actually where I really cut my teeth on testing, but if you go back and look at the tests you’ll find heaps of them are testing and checking types for functions. It almost felt like people were building static typing using automated tests.

  Some people bang on about static typing getting in the way of agility, but the reality is that you either end up spending the time creating extra tests, or you end up cutting corners and creating unreliable software which you’ll spend a lot of time troubleshooting down the road.

  source

  • fubo@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Some inexperienced programmers hear “static typing” and think “Java”.

    source
  • gnus_migrate@programming.dev ⁨1⁩ ⁨year⁩ ago

    Also being able to prove the relationship between different parts of the code enables a lot of productivity tooling like IDEs. Simple things like renaming a class or a struct become chores at best in a statically typed language, whereas in dynamic languages there is an element of risk in refactorings like that.

    source
  • henfredemars@infosec.pub ⁨1⁩ ⁨year⁩ ago

    I really like the mix we have at work with Python. We type all methods, but no typing in the body unless the code is unclear. We treat it more like if it were a statically typed language with type inference. This gives the IDE loads of info to work with for refactoring and warnings. The reality of dynamic typing is more like an implementation detail.

    source
  • kool_newt@lemm.ee ⁨1⁩ ⁨year⁩ ago

    Check out Crystal, it’s like static typed Ruby.

    source

    • attn_dfct_dev@programming.dev ⁨1⁩ ⁨year⁩ ago

      Is there a static typed equivalent of Python? Not MyPy, but a static Pythonic language.

      source
• muhanga@programming.dev ⁨1⁩ ⁨year⁩ ago

  And also ther is a lot of cases where you really don’t need or want static typing. Static typing and type systems are great when they helping you but very bad when you are forced to fight them due to compiler problems or bad modeling.

  In the end it is all an engineering problem: which amount of your budget you need to spend on proving programm correctness. Cost/benefit and all of that.

  Static typing and unit tests don’t make your codebases great, safe and supportable. Thinking and understanding your usecases, decomplecting problems and some future planning wins.

  source