Long-term Approach to Software
In his essay Software That Lasts 200 Years, Dan Bricklin calls for an approach to software that takes into account long-term consequences. Bricklin compares software production to building projects - houses, bridges, roads - that are planned and built to last for a very long time. By contrast, “software has historically been built assuming that it will be replaced in the near future (remember the Y2K problem)”.
no comments yet
