This article discusses the concept that software structures are traversed as paths, arguing that the simplest explanation of software design is rarely a straight line because components’ meanings are intertwined and depend on shared context and history (like the MVC pattern).