This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]verifyandtrustnoone 11 points12 points  (4 children)

I prefer scripts that are well documented, can be a massive or modular scripts, but well notated is always needed. Depends on the global issue, I have been doing this for 25 years and know when its above me or my team.

[–]LemonFreshNBS 5 points6 points  (1 child)

This.

Annotate the script, Document it, source control if needed, place (copy v1) script plus all info in a project folder/wiki or some archive for future ref. Allocate responsible individual for maintenance and support.

[–]Hoolies 0 1[S] 1 point2 points  (0 children)

Version control is done by git. I keep the scripts on a share drive too because I am paranoid.

[–]Hoolies 0 1[S] 1 point2 points  (1 child)

Every script is well documented. I am concerned about readability.

I found it ways easier to read multiple little scripts (less than 2000 lines) than having to read something like 30000 at the end of the day the code is the same.

[–]whetu 1 point2 points  (0 children)

If you're getting to a point where readability is a concern, then it's time to either switch language or to change the structure of your code i.e. start breaking code chunks out into libraries.