Taking pride in ignorance First and foremost, concentrate on your strengths. Put yourself where your strengths can produce results. Second, work on improving your strengths. Third, discover where your intellectual arrogance is causing disabling ignorance and overcome it...First-rate engineers, for instance, tend to take pride in not knowing anything about people. Human resources professionals, by contrast, often pride themselves on their ignorance of elementary accounting or of quantitative methods altogether. But taking pride in such ignorance is self-defeating. Go to work on acquiring the skills and knowledge you need to fully realize your strengths. Peter F. Drucker, Managing Oneself ignorancearrogance
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