Of all the positions I've worked, this is the first opportunity I've earned to put my knowledge to full practice. Being hired as a technical writer, one who makes a livable wage and is treated with respect, has been a trip. I don't know what else to call it. I've been in secretarial positions and client facing positions for so long, it's incredible to me that I don't have to interact with a customer base daily. In fact, I only talk to internal employees. 

I've gotten a wide array of responses to being a technical writer. Some ask why I'm there, if I'm busy at all, but most ask about what this job really consists of. It boggles my mind to realize how many employees interact with technical documentation every day, but don't make the connection of its importance to their every day tasks. To make it easier to explain, I simplify it into a joke, "If I do my job right, you won't have to answer questions from interns because the document will already answer all their questions" - it gets a few laughs, sometimes. 

It's a struggle with my students as well, many of them balk at me when I remind them that they'll never escape writing. They rebuke back, "well, I'm an engineer" or "I do math, I'll never have to do that" etc. I challenge them with my experience. I've worked with engineers, researchers, and as of late with a financial company. Writing never leaves the picture - no matter what industry. They're in part correct, it won't be a 5 paragraph essay or a cover letter. But they'll never be able to dodge reports, white papers, memos, emails, meeting notes etc.

The workplace is saturated with writing - and a wide variety of audiences to appeal to. In my last post I argued that rhetoric focused curriculum should be integrated into earlier schooling because it assists students in reading their environments and adaptation to situations much easier. It should also be taught through the lens of the professional workplace. But understanding the basics of technical writings, and applying knowledge of the audience as an advantage, communication can be improved in the workplace. 

Technical writing can benefit companies in several ways: 

• Reduce training time for interns and new employees 
• Make clear expectations for each role to reduce responsibility tensions
• Creates a paper trail of versions when software or procedures are updated 
• Ensures a simpler way to hold employees accountable - when documentation is not available, it can be easy to make mistakes
• Reduces workflow disruption - if someone is sick or out who completes a specific task daily, somebody can take over without delay because they have documentation to fall back on 
• Ensures a brighter future at the workplace by cultivating clearer communication 

If you've ever struggled through training, had trouble adjusting to a job because the information is overwhelming to understand verbally, or encounter too many methods of completing a task, your workplace may need a technical writer. If you'd like to talk more about this subject or have questions, please leave a comment or contact me. 

I presented this week about why I believe kids should code. Ideally, I wish I had the money to back some sort of scholarship fund, or nationwide initiative. Maybe one day I can make it work.

Ted Underwood's The Stone and the Shell post, "Where to Start with Text Mining" emphasized that textual analysis isn't new. Our, "wrinkled spongy protein" brain is already much better at analyzing literature than most computers.  It's the large scale text crunching that's new, and it's hard for us to imagine all the possibilities because we're not used to thinking like that. But in combo with computers, we can accomplish a lot.

My Old Sweethearts: On Digitization and the Future of the Print Record by Andrew Stafford concluded with the argument that DH exists because of the value we place on both the digital memory as well as the physical text. It is the existence and the situational exploration of both that provides validity.

After those readings and ideas stewed in my mind, seasoned by a whole week spent on basic coding introductions, I started to think about all the opportunities kids had to dive into the practice. Learning late has been such a curve, but they do this stuff early right? I learned that this was not the case.

After a bit of research I realized that the only kids who get to really dive into coding and digital manipulation/creativity are those who parent's pockets run deep. Cubetto is an educational robot and coding interface for children 3 and up. It's lowest offer is about $250, the most expensive is far over $300. Other toys like Fisher Price's Code-a-Pillar is about $40 which is cheaper, but still likely not the first choice for many parents.

When I looked at coding camps toted as havens for creative kids, these prices were even more jaw dropping. An ID camp offered at USF is no less than $900 a week not including food, overnight fees or any bonuses kids may be interested. Only incredibly well off families can afford these expenses and schools certainly do not support coding initiatives in elementary school.

I believe that the whim like brilliance in children would be even more beneficial when supplemented with coding and digital manipulation lessons. As scholars working in DH now, we have to think backwards almost. We're used to looking at text analysis and manipulation in a different way because we've had to integrate those tools and processes pretty damn late. But if we were to teach kids that value of dualism, the awesome human brain and the power of the computer mind would be an incredible thought revolution.

I believe teaching coding early, like we do and encourage with any other language, would enable applicable innovation and creativity within each child. Hybridized thinking processes may be the answer to so many of the problems we struggle to see.

Here is my PechaKucha and script on the topic.

I'm Behind on these reading responses which is regrettable because I have so much to rant about. So strap in, it's going to be a busy post.  

If you're reading this, I can nearly guarantee that you're at least interested in this stuff or another nerd searching for brain nuggets.  On the menu for this ledger? Data collection and girls.  

Since my first Isaac Asimov novel, I've been consistently obsessed with the power that technology grants to people. It's a god-like gift being able to transcend the physical into manipulatable space.  

I quickly learned that technology isn't like a superpower at all unless you've been diving into a technique for decades. Even then, your power might not be accepted or valued due to the social/rhetorical situation.  

Bethany Nowviskie had a quick article about this issue in regards to women being generally forgotten in data mining conferences and panels. The offenders? Fairly amicable. They took Bethany's advice into account and I hope to see a follow-up Tweet thread about these improvements.  

But the turnaround isn't always that quick, nor does offense result in response as often. In my own time in IT-related jobs I've noticed this. In the academic world, It's rampant. There are so many areas that cause surprise to people when they notice a woman among its ranks. I keep hoping that the older I get, the fewer these instances would occur but it's quite the opposite. Many of my friends and I have been passed over when promotions arise simply because we are seen as lesser.  

My previous post had a lot to do with transparency and I believe gender complaints/issues/tensions might benefit from increased transparency in the discussion. I should be able to say to my employer that I believe they passed me over due to gender, and I should not have to expect relentless backlash for saying so.  I joke around with my coworkers that I'm just a tech princess and I'll never be the hero, they'll laugh and then some sober up and look at me with such sorry faces. They know it's true and I hope they'll change that. Many of my coworkers have moved onto high paying jobs at Microsoft, Google and Reliaquest. One day, when they hold the authority to hire, I hope they'll think of me. 

But, as disappointing as clichés are, this, is so, so normal. I wonder how this will change as access to technology and technological education increases.