[edghf]

I'm a writer and editor. I've done marketing and financial writing, and the job I'm starting in two weeks will require me to do technical writing. I've also started learning to code, because I'm interested in it and because it's an important part of how important systems in the world work.

There are common attitude problems on both sides of the the technical/non-technical fence. From the non-technical side, there's a sense of unfairness, that people with the interest to pursue technical subjects are guaranteed 80k/year jobs right out of college, that they are stuck-up and dismiss the ideas and opinions of people with fewer credentials, etc. Like most stereotypes almost none of that is true. My coder friends are some of the most generous, respectful people I've ever met. It's much harder even for someone trained in CS to get a job than it looks from outside. HN is largely technical--you know that there are reasons for how technical people behave even when it might seem strange to outsiders.

The most common mistake I see technical people make about non-technical people is in the area of algorithms and specifications. To but it simply: in a lot of disciplines, there aren't any. The common misunderstanding is that there are formulas you can use, or rules you can follow, to get the result you want in non-technical disciplines. There are huge numbers of artifacts in the world that aren't empirically measurable. Take a pair of jeans and say, "Is this OPTIMAL?" The question is as nearly meaningless as makes no difference. Look at a wedding bouquet, or a corporate event, or a logo. The people who make these things are constantly making choices informed by their education, experience and perception, but those choices aren't based on data that's easily quantified. At best, you start to notice patterns that work and patterns that don't work, which is something that I think can also be said about software development.