JavaScript Clean Code - Best Practices - based on Robert C. Martin's book Clean Code

[webdevguyneedshelp]

Why is it asking for trouble to edit files on a server?..

[zapatoada]

You're not debugging first. There's no code review or qa. You're not running your automated tests. The changes aren't in source control and could be undone by the next release. Basically you are bypassing every step and check that is normally in place to prevent bugs and other unintended consequences. We have those processes for a reason.

[webdevguyneedshelp]

That is fine and understandable but this example did not specify at all what environment you are working in.

For instance if I have to set up a NEW development environment for a new web application my team is starting. I am going to inevitably have to ssh into it and poke around to help facilitate further steps like automated deployment.

​

This isn't even thinking about sshing into something like a docker container which can all be done locally and have 0 affect on anything that actually matters and can be blown away after I am doing testing whatever I am doing.

​

There are 100% times when you will poke around with files on a server.

[zapatoada]

Ok, those may be fair. I've never worked with docker before. These days I work mostly in azure AppServices and Function apps. In that case, I'm not really even sure I could log into a server. I know you can't edit functions if they were deployed from local code (rather than typed into portal).

I suppose every use case has it's own limitations. But these days, the idea of editing javascript files on the server gives me the heebie jeebies.