I work in the GLAM sectorindustrysector , where longevity is a major concern . Museums , libraries , digital archives , and so on . We are the sort of folks who get involved with the Wayback Machine and the ArchiveItit . org projects . I fully agree that using source control is crucial , not only for code , but for content as well where possible . Working in a museum brings on its own slew of concerns . It ' s like , our institution is tasked with the preservation of cultural artifacts . To us as software developers , that also means our code should strive to survive the test of time . Plus , nonprofits can ' t compete with the high salaries $ 90 k offered to software developers in the private sector . On the one hand , it means that the field tends to attract developers who care about the museum ' s mission . On the other hand , it means that most institutions are shortstaffed , or suffer high turnover . To mitigate that , we have to create systems that can live for a long time without maintenance , and that can be understood relatively quickly . Writing readable code , documentation , proper version control , etc . I think longevity is the one topic software developers in the GLAM sector should be bringing to the wider web development world . We ' ve been dealing with it for decades . Future legacy software doesn ' t have to be bad !