Specializing deeply has costs and compounding returns. A reflection on what domain experience actually changes about how you work.
Standard proposal templates assume a standard project. GIS tenders have technical specifics that generic bid advice simply doesn’t account for.
Software ships continuously; documentation can’t be rewritten every sprint. Strategies for writing docs that survive the next release.
Increasingly, the people using GIS software aren’t cartographers — they’re planners, surveyors, field crews. Documentation has to meet them where they are.
Not all documentation does the same job. A practical map of the core document types, who each one serves, and the order to build them…
Most GIS documentation is written by engineers under deadline pressure — accurate, but unusable. Here’s what separates documentation people actually read from documentation that sits…
