“cool”
“cool”
You’ll probably have to generate a lot of plots, graphs and figures. Choosing the right type of figure to explain the data is an important skill - maybe have a play with some of the examples from https://r-graph-gallery.com/
User: I’ve tried everything
Support: Have you tried <first step in documentation>?
Democracy works! You voted and they listened!
I volunteer as tribute!
overhead style showerhead
I don’t understand… Where should the water come from? Below? From the sides?
Did you remember to override .Equals and .GetHashCode?
One thing that worked for me in a similar situation was to enforce an “owner” tag or some kind of registry on everything.
Basically, if you set something up, change some configuration, whatever - put your email address on it.
Write a readme.md or wiki or guide too, but at the very minimum put your name down as the owner so that when someone comes along and wants to know if it’s safe to change/upgrade/delete, they can find you and ask. If someone leaves, you can do a quick search and get them to handover/write up anything they were responsible for.
It’s complicated. It’s sort of colony animal, like a slime mold or a portuguese man-o-war. Either way, you shouldn’t touch it.