Discussion Locked

Should scripting be reserved for advanced technicians only?

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

One of our colleagues asked a pretty fair - and slightly controversial - question: "Why should I show my script to others?"

It's a common feeling. When you spend time crafting a script that works, it can feel personal - like your own toolset or shortcut. But keeping scripts to yourself can create risks: what if it breaks something, introduces a vulnerability, or duplicates what someone else already built?

Sharing scripts isn't just about oversight - it's about collaboration, transparency, and security. When others can review your work, they can spot potential issues, suggest improvements, and help keep everything aligned with company policies. In the long run, it makes the whole team stronger and the environment safer.

What do you think - should every script be open for review, or is there room for personal ownership?

4 replies

by birdmantd edited

Is that colleague's computer his own, personal computer or does the company own it? If he uses a company asset, then he doesn't own it and he shouldn't be able to decide who has access to it and the data contained on it.

by yolandasmith

I think it depends on the context. Not every script needs to be public or reviewed by everyone, but if it's part of a shared workflow or could impact production, then yeah it is safer to have a second set of eyes. Personal scripts for small tasks though? I do not think those always need to be open unless you’re asking for help.

by afzaalbhatti1244 edited

Interesting question! Scripting shouldn’t be limited to only advanced technicians — with the right guidance and tools, anyone can learn to automate simple tasks and improve efficiency. It’s all about accessibility and training, not restriction.

This discussion is closed to new replies.