My Anti-Resumé An Article by Monica Byrne monicacatherine.com A couple years ago I was having dinner with a playwright, Bekah Brunstetter, and her director David Shmidt Chapman. We talked about how rejection is just part of the landscape for all beginning artists, no matter how talented or hardworking they might be or how successful they might appear. David said he’d love to publish his “anti-résumé” someday—a list of all the things he didn’t get. Spreadsheet Portfolios for UX Designers workfailure
Trees and graphs Show image 0 Show image 1 A tree is a kind of graph, but a graph can be considerably more complex than a tree. I have reason to believe, which for brevity’s sake I will treat elsewhere, that the most complex class of processes and structures we humans can consciously prescribe, reduces mathematically to a tree. A tree has a top, bottom, left and right. Its branches fan out from the trunk and they don’t intersect with one another. They are discrete, contiguous, identifiable objects which persist across time. Trees are Things. Software and websites, however, reduce to arbitrarily more complex structures: they are graphs. A graph has no meaningful orientation whatsoever. No sequence, no obvious start or end—at least none that we can intuit. It is better considered not as one Thing, but as a federation of Things, like the brain or a fungus network, or perhaps a composite artifact left behind from an ongoing process, like an ant colony or human city. Dorian Taylor, On the "Building" of Software and Websites A City Is Not a Tree networksthinkingmath