Technical writer focused on development tools, databases, and APIs. Manual tester. Freelance reporter, editor, and reviewer. Currently working as an analyst/PM.
Join our Director of Integration Technologies Janice Karin as she discusses the regulatory environment in 2021 and predictions for 2022 at the @ehealthDC Policies and Technology to Connect Healthcare Data: What Lies Ahead webinar on Dec 8 at 1pm. Register: https://t.co/2on3ilDNlj
@SingleSourcing @lizfraley @tcdojo I should be on there but I don't remember getting any recent emails. Ping if you don't see me and I'll sign up again.
@espirian I once wrote the only negative review of a very popular program. It was a long review that explained why I was unhappy in detail (and praised those few things I liked). I ended up in a long, fruitful dialogue with the developers with whom I ended up having a great relationship.
Just attended Healthy Language is Plain Language #webinar by @marsinthestars for @MadPow - thanks for an interesting take on writing for healthcare (and for answering my questions!)
What are folks currently using as a presentation layer/host for their online documentation? Is it part of the normal corporate website mechanism or separate? Inquiring minds want to know what industry standard is at the moment #techcomm
As a participant, I get frustrated when I feel the trainer doesn't know the material or how to communicate it or is ill prepared for questions or tries to pretend omniscience. It drives me bonkers when the material is poorly written or poorly organized or falsely advertised.
"So today I ask: what makes for a great training participant (and when we find ourselves as participants instead of trainers, what behaviors and attitudes should we bring)?" https://t.co/7hzczRDVHt #Training#AdultLearning#Learning
@espirian Posts should be as long as they need to be to say what you want to say - no longer and no shorter. Artificial limits in either direction is less than ideal IMO. Many people artificially cut things short, stating their thesis but not supporting it with subsequent content.
This is interesting. I like the basic idea, but I'm not sure I quite buy that it can rolled up into a reasonable, repeatably accurate formula. I have to think about this some more.
@espirian Many used to pay, but it's like the switch that happened with technical content a while ago - a lot of even larger publishers (mostly online) expect people to be paid by their companies then use the articles to promote their companies rather than be freelancers looking to publish
I must have background noise to focus, usually music or TV (but not something I want to watch that I haven't seen before). I won't really notice it's there once I get going but I will notice its lack. I used to abruptly stop when the stack ran out on the record player.
How do you like to work? In complete silence? 🤫 Or surrounded by coffee-shop hustle and bustle? ☕️ Maybe you like working along to music? 🎻
It turns out that silence isn't always preferable for those of us who employ deep concentration in our work https://t.co/OXrWcBp68N
"Our tech writing team ... helped test my API by playing the role of external user and asking product questions before we’d started putting down code, let alone hit market." - yes, and testing that it works as expected once built, and that the doc matches the actual behavior