There's a risk vs productivity balance. Most people develop for systems which are connected to the internet and can be updated on demand, in that case it makes

There's a risk vs productivity balance. Most people develop for systems which are connected to the internet and can be updated on demand, in that case it makes sense to "shit out javascript" because we can go back and optimise and fix things later. That doesn't mean you can't use proper design patterns, but you shouldn't front-load work for something which is most likely going to be wrong for the customer when they see it regardless. The fact that we can iterate on something once it's released means that engineering in a software sense is different from any other discipline which we call engineering.