I'm a Content Architect and sometimes content developer working with several dozen (hundred? I have lost track) over-engineered aerospace and mil-std specifications. Technical Publications software has been a garbage fire since I entered the workplace (at least), and I hope that, at the end of my career, I can look back and say I helped some.
I wouldn't call this high tech. Most of the time I'm working with very primitive IT environments, trying to introduce little bits of technology as strategically as I can. Other times I'm trying to bring in tools for dealing with other data formats. Half of the day is just training people on stuff you dev types might take for granted (i.e., regex).
HN keeps me abreast of the latest movements of the content software stack. It's what clued me in to Asciidoc a few years back. For whatever reason HN seems to have built an insanely good commenter culture. How they've avoided brigading with such an open system I have no idea.
I wouldn't call this high tech. Most of the time I'm working with very primitive IT environments, trying to introduce little bits of technology as strategically as I can. Other times I'm trying to bring in tools for dealing with other data formats. Half of the day is just training people on stuff you dev types might take for granted (i.e., regex).
HN keeps me abreast of the latest movements of the content software stack. It's what clued me in to Asciidoc a few years back. For whatever reason HN seems to have built an insanely good commenter culture. How they've avoided brigading with such an open system I have no idea.