Reflections on Software Performance An Article by Nelson Elhage blog.nelhage.com Performance is a feature Performance changes how users use software Performance needs effort throughout a project’s lifecycle Architecture strongly impacts performance Performance isn’t just about hot spots Performant foundations simplify architecture …we underrate performance when designing and building software. We have become accustomed to casually giving up factors of two or ten or more with our choices of tools and libraries, without asking if the benefits are worth it. performancesoftware
v0.crap I couldn’t seem to convince my writers that I was genuinely ok working with a super rough first draft — i.e., that I’d harbor no hidden judgment about their intelligence, commitment, or excellence at their craft. So I came up with a new word. “Just give me a v0.crap.” (Pronounced “version zero dot crap”.) v.0.crap works because it’s attuned to the psychology of the situation. It’s punching through our innate desire not to “look bad”, plus years of corporate conditioning that tells us not to share less-than-polished work. It’s easier for people used to delivering exceptional work to feel they’ve exceeded the goal of “crap”; they can sit comfortably in “good enough for the current purpose.” Courtney Hohne, The monkey, the tiger beetle and the language of innovation blog.x.company Writing, Briefly qualityideaswritingmaking