Podchaser Logo
Home
justSayIT, Technical Writers‘ LAUGH

justSayITBeth

justSayIT, Technical Writers‘ LAUGH

Claimed
A monthly Comedy, Education and Technology podcast
Good podcast? Give it some love!
justSayIT, Technical Writers‘ LAUGH

justSayITBeth

justSayIT, Technical Writers‘ LAUGH

Claimed
Episodes
justSayIT, Technical Writers‘ LAUGH

justSayITBeth

justSayIT, Technical Writers‘ LAUGH

Claimed
A monthly Comedy, Education and Technology podcast
Good podcast? Give it some love!
Rate Podcast

Episodes of justSayIT, Technical Writers‘ LAUGH

Mark All
Search Episodes...
All of us, especially technical writers, need to consider artificial intelligence and its affects on our jobs. This is my final podcast episode. Thank-you for listening!
Today, technical content is blended into the "customer experience or journey". This may seem adventurous; it's really not! Why do Technical Writers need to apply a spirit of adventure into documentation?
Chaos is described as a state of utter confusion or disorder. We may not be chaos-proof but we can be chaos-ready—especially important for technical writers! 
There's something about elevators that brings up a tool that's useful for anyone, especially for technical writers trying to get ahead in their careers.
Whether at work or play, your digital footprint is a reality of life: curate and cultivate it. Discover why technical writers should use the three Rs of digital citizenship.
How do you deal with flakes and laggards? What are the ramifications of technology innovation adoption on the documentation technical writers produce?
What do spud guns and chicken cannons have to do with the "Tyranny of the Urgent" and how can technical writers mitigate the chaos?
In a competitive workplace, many have merit, but few succeed. Understanding the myth of meritocracy is key to success. What must tech-writers leave behind?
A clip from EP-5, a personal remembrance; my mother, also called Elizabeth, became Queen for a day!
We recognize the world's deadliest creatures but what about those found in the technical writing world—they make you want to spit! 
Excessive idle talk or chatter is called palaver, yet it can appear in writing. How can Technical Writers avoid it?
The simplest way of gaining goodwill and making people feel special is by remembering their name, and yet how many of us do it? Technical Writers apply names in the documentation we write but do we use names wisely? 
Mired in a web of complacency, it's much easier to accept things as they are or do it the way we've always done it because it's comfortable. How can technical writers avoid delivering documentation in the same old way?
Almost every partnership, group or team has one dominant personality that must be "boss". Yet the most prevalent and destructive type of leadership, especially in the workplace, are ineffectual bosses that avoid meaningful involvement with thei
Bogged down with “gum” work? It affects your ability to learn, do more promotable work, and to demonstrate your full potential. 
Following reason or emotion in decision-making is described as two horses pulling us in opposite directions. How does this impact leadership and teamwork?
Empathy, it’s the oil of relationships that keeps them running smoothly and a critical skill for business. How do we exercise it?
Popularized by Alfred Hitchcock, the master of suspense in horror films, could this plot device be used in technical writing?
There’s much to be learned from puzzles and their "unpuzzling". They can relieve stress and even increase our IQ. How do they affect technical writing?
Myths in technical writing? Let’s bust three common ones. Technology is rapidly changing our profession, yet we must keep our sanity, meet these myths head-on and kick them to the curb!
How can we be careful with words yet provoke thought with wild words? Context is everything!
How does the honour system work when part of a team? What is the language of trust and how can we use it well?
It’s a lot to swallow but if nature can automate the many reflexes used in swallowing then why are technical writers so slow to apply automation to documentation? 
From a different angle, let’s look at three familiar models that we use as standards to either imitate or compare.
What does the Rebus Principle and ancient Incas Khipus have to do with changes to technical writing? Aren’t writing basics and tools much the same?
Rate

Join Podchaser to...

  • Rate podcasts and episodes
  • Follow podcasts and creators
  • Create podcast and episode lists
  • & much more

Unlock more with Podchaser Pro

  • Audience Insights
  • Contact Information
  • Demographics
  • Charts
  • Sponsor History
  • and More!
Pro Features