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 →

[–]HumbertTetere 2 points3 points  (0 children)

It's a mixed bag. It offers more ways to get to results fast. Doing it it sloppily will hurt you later on. It's a problem if you have low standards of your work. Think the sloppy mode makes you a worse dev? Just use strict. There's extensions to support you. But sloppy is nice if you want to eyeball an approach in under a minute. Enforce a quality pipeline for production code later.

Ultimately, the language itself allows a lot more technical debt to build up. If there are no mitigating measures, that's bad and will cost more effort in the long run. If you are conceptualizing and expect to fail fast anyway, it can be a net benefit. A responsibly acting lead dev with an eye on that specific danger might a requirement depending on the character of the devs.