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.
Learn what excellence is, how to identify it...This is not a big reading assignment – excellence is scarce, lognormal, long-tailed. Acting on this knowledge is liberating, freeing oneself from vast piles of triviality, knock-offs, petty connoisseurship, over-publishing, and the short-sighted, trendy, greedy. Excellence is long-term knowledge, even forever knowledge.
Excellence, like good taste, is perhaps a universal quality. Analytical thinking is about the relationship between evidence and conclusions, and is fundamental to all empirical work, regardless of field, discipline, specialty. Thus it is possible at times to assess credibility of nonfiction work without being a content expert. Thinking eyes may well have an eye for excellence, regardless of field or discipline.