How to hold back from interfering with students' inefficient-but-not-wrong work? I'm a new and junior group leader. I therefore work quite closely with my (also new) MSc students. 

I try to let them work and figure out things as independently as they can, but have my door open so they can ask me for help. When they do, it will often be about scripting. 

In these cases I sit with them and we work together for a little bit. That's when I see that students often work in ways that are clearly inefficient, but not objectively wrong. 

I don't want to interfere too much. This is a learning process and it takes time to learn from one's own mistakes. But I have to really force myself to not suggest they use keyboard shortcuts, a bigger editor window to see more code, more sensible file and variable names, use Dropbox instead of emailing, etc etc. 

I think it's important that I hold back: it would be annoying of me to point out every little thing, especially if, as I said, it's not actually wrong. Is there a good way to suggest solutions but not be unnerved if students don't use them?
What if you were to write up a list of "general development tips"?  Then you can share it with everybody once instead of constantly giving unsolicited advice.  

You can also then give it to future students and hopefully get them started off well from Day 1.