Strategic, not tactical The working methods of the innovative designer are, for the most part, not systematic; there is little or no evidence of the use of systematic methods of creative thinking, for example. The innovative designer seems to be too involved with the urgent necessity of problem solving to want, or to need, to stand back and consider their working methods. Their design approach is strategic, not tactical. Nigel Cross & Anita Clayburn Cross, Winning by Design: The Methods of Gordon Murray strategy
Cultural relevance More than ever, people are choosing how to spend their time based on the amount of attention they can garner—and you and I are no exception. Everyone is susceptible to this logic. But what I want to argue in this piece is that tech startup founders are particularly susceptible to this tendency. Working at and around startups for several years, I’ve noticed many founders prioritizing culture, visibility, and perception over product, customer development, and strategy. Maybe this is to be expected in a time where culture moves faster and is perceived as more important than ever. But I find it unusual that the tech industry seems unaware of a whole class of typical mistakes founders make in pursuit of cultural relevance. Toby Shorin, Building for the Culture subpixel.space culturestrategybusiness
Background textures of work An Article by Lucy Keer lucykeer.com One thing I've been enjoying about working as a technical writer is that the minute-by-minute texture of the work feels right. Something about formatting text, faffing about with SVGs, trying to rewrite a sentence more clearly... it's just enjoyable in itself, and I feel at home with it. ...Working as a programmer was very much not like that. There's something in the rough vicinity of professional dev work that I do like, which I could probably label as 'iterative hobbyist tinkering with websites'. I like working on something with a strong visual component, and I like to be inside of a fast feedback loop, and I'm mostly interested in just somehow bodging through until it works. I'm not very interested in either the computer-sciencey side of programming — data structures, algorithms — or the software-engineerey side of making things run reliably at scale in a maintainable way. So maybe it's not surprising that the minute-by-minute texture of professional programming was just... kind of bad. Occasional fun bits when I got into something, but the background experience was not fun. workproductivitymaking