What do you think is necessary to create good documentation? What documentation will you and your project lead need to create for your Vivero project – and what steps do you need to take to make this happen?

To create good documentation, I think that it’s necessary for the writer to not assume. I can see how this would be tedious work, especially for platforms we’re more used to or see as more simple. We make many assumptions based on what we’re used to, but knowing that someone is using a particular computer or a particular feature could lead to less frustration when results don’t match up.

For more confusing tools, like ArcGIS, I can definitely see this being helpful. I know that my project lead has had moments where she got something working years ago but couldn’t replicate it. I also feel like there is that impulse to do first rather than write all this out, but I can see how this method would ensure that someone knew what they were doing and that they could refer back to it some time in the future or for others. My project lead and I plan on making separate maps and then sharing them with one another. We will want to create documentation for the maps that we make. Documentation will let each of us explain what we did and why we did it. This is also conducive to helping the other learn.