Ask HN: How do you organise and discover your team's internal scripts?
As a team we have many scripts for doing various internal tasks - domain-specific things, checks for questions like "what's in prod?" and "how far along is this commit?", etc. ad nauseam. The problem is that, with a few exceptions, the person who wrote the script knows it exists and how to use it; and might be around to chime-up with "hey, I wrote a script for that!" when someone has a problem. But discoverability is hard, even if they're in the repo not everyone will have seen or reviewed the PR that added them. Does anyone have some good tips to share on how to (or not to) organise such scripts or tools, and allow colleagues to better discover them? 0 comments on Hacker News.
As a team we have many scripts for doing various internal tasks - domain-specific things, checks for questions like "what's in prod?" and "how far along is this commit?", etc. ad nauseam. The problem is that, with a few exceptions, the person who wrote the script knows it exists and how to use it; and might be around to chime-up with "hey, I wrote a script for that!" when someone has a problem. But discoverability is hard, even if they're in the repo not everyone will have seen or reviewed the PR that added them. Does anyone have some good tips to share on how to (or not to) organise such scripts or tools, and allow colleagues to better discover them?
As a team we have many scripts for doing various internal tasks - domain-specific things, checks for questions like "what's in prod?" and "how far along is this commit?", etc. ad nauseam. The problem is that, with a few exceptions, the person who wrote the script knows it exists and how to use it; and might be around to chime-up with "hey, I wrote a script for that!" when someone has a problem. But discoverability is hard, even if they're in the repo not everyone will have seen or reviewed the PR that added them. Does anyone have some good tips to share on how to (or not to) organise such scripts or tools, and allow colleagues to better discover them? 0 comments on Hacker News.
As a team we have many scripts for doing various internal tasks - domain-specific things, checks for questions like "what's in prod?" and "how far along is this commit?", etc. ad nauseam. The problem is that, with a few exceptions, the person who wrote the script knows it exists and how to use it; and might be around to chime-up with "hey, I wrote a script for that!" when someone has a problem. But discoverability is hard, even if they're in the repo not everyone will have seen or reviewed the PR that added them. Does anyone have some good tips to share on how to (or not to) organise such scripts or tools, and allow colleagues to better discover them?
Hacker News story: Ask HN: How do you organise and discover your team's internal scripts?
![Hacker News story: Ask HN: How do you organise and discover your team's internal scripts?]()
Reviewed by Tha Kur
on
July 05, 2018
Rating:
No comments: