IMO Alexander's design pattern concept is intelligently superior to the terms trivialization in the atrociously highly rated GoF book. GoF enumerates the tedious patches one needs to use on cumbersome languages like Java or C++ due to the languages primitive nature. The main advantage of GoF that now when you say "Factory pattern" everyone knows sort of concept they are speaking of.
However.
In the scope of Alexander's work GoF patterns are of equal complexity, as if giving names to typical architectural items like "door" or "room".
Alexander's work is on a higher level - discussing how to perceive the complex totality the combination and co-existence of such design features create. GoF book names door a door. Alexander's book discusses how to design houses and communities. Completely different scale.
In software engineering terms I think the closest book that is the best analogue to The Timeless Way of Building in terms of discussing higher level patterns, and how to combine them, is perhaps the classical Structure and Interpretation of Computer programs that since it uses such an elegant language, it can skip the tedium and start with expressing of higher level patterns, and in the end how to combine them into a whole complex system.