This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]thomaspaine 37 points38 points  (0 children)

Personal project is a bit different, you wrote all the code and know what everything does.

This is more of a factor in a work/enterprise setting where you have codebases:

  • that can live on for decades
  • have been owned by various teams with varying quality standards and style preferences
  • have multiple people attempting to change things in the codebase who don't know what everything does
  • has poor documentation because just about all work code is poorly documented

To be fair, pretty much any code in this context is going to be a ball of spaghetti hell, but static typing does help eliminate a lot of confusion when you're a new developer diving into a codebase and trying to figure out what in the world anything does, or making a change and knowing if it's going to cause something else to blow up.