![\"photo](\"http:\/\/redmonk.com\/kfitzpatrick\/files\/2021\/07\/Green-and-blue-lights-scaled-e1625515716757-1024x604.jpg\")
<\/p>\n<\/p>\n
A few weeks ago I had the chance to sit down with Andy Stevens, Technical Content Manager at Linode, to film a RedMonk Conversation<\/a> video on Documenting the Alternative Cloud<\/a>. If you are interested in tech comm and\/or documentation, I recommend checking out that video (and\/or its transcript<\/a>), where we cover topics like docs-as-code, documentation sprawl, and tips for delivering better technical documentation.<\/p>\n During our conversation, however, Andy and I covered so many tech writing topics that we ended up with some additional segments that might prove useful to anyone hiring, managing, or considering finding a gig as a technical writer or documentarian. You can find these excerpts (and links to their transcripts) below. They are ordered according to where they fell in our initial conversation, but can be viewed individually or in any order.<\/p>\n A discussion of the organization and responsibilities of the six-person docs team at Linode (including the types of documentation it produces), where the team is located in the larger org structure, and some of the professional backgrounds of team members.<\/p>\n Read the transcript of this video here<\/a>.<\/p>\nOrganizing the Docs Team at Linode<\/h1>\n