Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

Nowdays it\'s goes to be very fancy to have grunt/gulp build phases who concaten

ID: 648208 • Letter: N

Question

Nowdays it's goes to be very fancy to have grunt/gulp build phases who concatenate and minify and organize javascript code.

And I agree that this is important for production.

But as a developer, I see inconvenience there:

additional step to run code (execute gulp/grunt command)
hard to navigate in one concatenated files (even worse if it's minified)
Build procedure take time, especially if your project quite big and pc not very powerfull
So, is it important to have all that steps for development mode anyway, or will be reasonable to make it a part of release process, and avoid using it during development?

Explanation / Answer

You need to do it from time to time in development to check that it works correctly and isn't adding any additional bugs.

It shouldn't be a step that you're using just in your release process, because that should be happening post-testing.

You shouldn't be doing it for every small change you make, but from time to time you should absolutely be checking your new code works correctly after it's been concatenated and minified.