tor sparql queen ✅Apr 6, 2017
how do people get colleagues to be better about using/approaching git + GitHub? e.g. have two metadata colleagues who are trying to run scripts I wrote them, but don't ever pull down latest changes (with bug repairs after they report back) before rerunning, then blame the script (+ not the whole process).
Show threadDavid EagleApr 6, 2017

@cm_harlow Two things:

1. You may need to improve the way you're communicating that fixes are in place. They can't be expected to just _know_ you've published a new version.

2. If you're doing 1., it's just a matter of repetition. Every time they say "it's broken!" say "make sure you have the latest version. Go to Github."

Show threadtor sparql queen ✅Apr 6, 2017
@deagle i've been telling them via email, in person, tagging them in the issues / discussion on the PRs.
Show threadDavid EagleApr 6, 2017
@cm_harlow Depending on your organization and your comfort level it may be appropriate, after enough repetitions, to say "I can't help you until you've gotten the latest build. Please let me know you've done that before sending a question" - in some orgs this may be unacceptable, culturally.
Show threadDavid Eagle
@cm_harlow Also, can you solve a people/process problem with Technology? can you make your script check its version against Git and fail with an obvious error if it's outdated?
Apr 6, 2017 at 2:44pmWeb
Show threadtor sparql queen ✅Apr 6, 2017
@deagle huh, now that's an interesting idea!
Show threadtor sparql queen ✅Apr 6, 2017
@deagle i've been working hard on refactoring a lot of our scripts/code for existing tools to have unittests (most of what was handed to me didn't)
Show threadtor sparql queen ✅Apr 6, 2017
@deagle this seems like a good step in that way too
Show threadtor sparql queen ✅Apr 6, 2017
@deagle thanks man for this discussion, very helpful