#technicalcommunication — Public Fediverse posts

For the forseeable future, AI tools will continue to generate such incomplete and sometime hallucinated outputs that there will be a continuing need for a "human-in-the-loop" to not only use several LLMs to review each other's output but to fact-check the final output. Using one LLM alone results in mediocre quality. Using two LLMs results in (sometimes very) good quality. Use three LLMs with human verification for great/outstanding results.

"1,131 people across the documentation industry responded to the 2026 State of Docs survey — more than 2.5x the number of respondents last year. But the size of the sample matters less than what it represents: a genuine cross-section of the people who create, manage, evaluate, and depend on documentation.

Documentation’s role in purchase decisions is stable and strong, and the case that docs drive business value is well established. The shift this year is in what documentation is being asked to do, and who — and what — is consuming it.

AI has crossed the mainstream threshold for documentation, both in how docs get written and how they get consumed. Users are arriving through AI-powered search tools, coding assistants, and MCP servers. Documentation is becoming the data layer that feeds AI products, onboarding wizards, and developer tools. The teams investing in this shift are treating documentation as context infrastructure, not just a collection of pages.

But adoption has outrun governance, and the gap matters. Most teams are using AI without guidelines in place, and documentation carries a higher accuracy bar than most content. After all, one wrong instruction can break a user’s implementation and erode trust in the product.
(...)
Writers are spending less time drafting and more time fact-checking, validating, and building the context systems that make AI output worth refining."

https://www.stateofdocs.com/2026/introduction-and-demographics

#TechnicalWriting #TechnicalCommunication #SoftwareDocumentation #DocsAsProduct #AI #GenerativeAI

Today's Featured Links post links to articles about how scientists are going to transport antimatter, using AI for technical documentation, why your next TV shouldn't be smart, and more.

https://coredump3.blogspot.com/2026/03/featured-links-march-18-2026.html

#AI, #History, #Medical, #Politics, #Science, #Software, #Space, #TechnicalCommunication, #Technology

"I’ve used AI to accelerate all my work, and yet, I’m still busy as ever. This is what I wrote about in Changing the AI narrative from liberation to acceleration. This notion that AI will do our work while we focus on other things … uh, yeah, that big chunk of time where Gemini does my work for me while I have time to daydream about system design and content architecture — that chunk of time never seems to materialize on my calendar. My days (which are often meetingless, actually) are filled with an endless queue of doc requests, needed updates, release notes, new features to document, and more.

So maybe as we peer into the future, signs of how it will play out are already present. It’s a bit like watching children grow up — the personality traits visible in the toddler years turn out to be the same ones you see in the adult. Five years from now, we might look back and say, why didn’t we see what was so clearly right there?

What is the pattern of the present? Acceleration, being busier than ever, all while using AI more than ever. If I instead noticed the opposite, a kind of winding down of my own activity and involvement while AI gradually takes on more and more of the activity of my day, that would tell a different story. The paradox is that AI is taking on more activity, but it’s pulling me along with it. I’m an active collaborator, shaping conversations, providing context, evaluating outputs, running verification, deciding the approaches, and so on. AI augments and accelerates our work rather than replacing it. We have the most powerful tools available to us, more so than at any time previously. Is it any wonder that we’re now building skyscrapers instead of doghouses, and that those skyscrapers require a lot of work?"

https://idratherbewriting.com/blog/nobody-knows-two-years-from-now

#AI #GenerativeAI #Automation #Productivity #TechnicalWriting #TechnicalCommunication

"The people best positioned to configure AI agents like Claude Code aren't engineers. They're technical writers.

It's a bold claim, so let me back it up.

Here's a file that powers an AI agent:

AGENTS.md

# AGENTS.md — API Documentation Repository

## Workflow Rules

- Human review required for API reference changes
- Style guide compliance checked automatically via CI
- Maximum 3 AI revision cycles before human takeover

## Escalation

- Writer agent fails after 3 attempts → human writer takes over
- Reviewer agent flags accuracy concern → SME review required
Markdown syntax, structured headings, rules about workflows and handoffs. If you've written a README, a style guide, or onboarding documentation, this looks familiar because it that's effectively what it is. The files that configure AI agents are Markdown files with structured frontmatter. They're documentation.

The difference is the audience: instead of a human colleague, you're writing for an AI model that's highly knowledgeable but has zero institutional memory. The challenge is one technical communicators already navigate: deciding what to include, how to structure it, and what level of detail serves the reader.

So what kinds of files are involved?"

https://instructionmanuel.com/agent-configs-are-docs

#TechnicalWriting #AI #LLMs #AIAgents #AgenticAI #TechnicalCommunication #Markdown #README

"The people best positioned to configure AI agents like Claude Code aren't engineers. They're technical writers.

It's a bold claim, so let me back it up.

Here's a file that powers an AI agent:

AGENTS.md

# AGENTS.md — API Documentation Repository

## Workflow Rules

- Human review required for API reference changes
- Style guide compliance checked automatically via CI
- Maximum 3 AI revision cycles before human takeover

## Escalation

- Writer agent fails after 3 attempts → human writer takes over
- Reviewer agent flags accuracy concern → SME review required
Markdown syntax, structured headings, rules about workflows and handoffs. If you've written a README, a style guide, or onboarding documentation, this looks familiar because it that's effectively what it is. The files that configure AI agents are Markdown files with structured frontmatter. They're documentation.

The difference is the audience: instead of a human colleague, you're writing for an AI model that's highly knowledgeable but has zero institutional memory. The challenge is one technical communicators already navigate: deciding what to include, how to structure it, and what level of detail serves the reader.

So what kinds of files are involved?"

https://instructionmanuel.com/agent-configs-are-docs

#TechnicalWriting #AI #LLMs #AIAgents #AgenticAI #TechnicalCommunication #Markdown #README

"The people best positioned to configure AI agents like Claude Code aren't engineers. They're technical writers.

It's a bold claim, so let me back it up.

Here's a file that powers an AI agent:

AGENTS.md

# AGENTS.md — API Documentation Repository

## Workflow Rules

- Human review required for API reference changes
- Style guide compliance checked automatically via CI
- Maximum 3 AI revision cycles before human takeover

## Escalation

- Writer agent fails after 3 attempts → human writer takes over
- Reviewer agent flags accuracy concern → SME review required
Markdown syntax, structured headings, rules about workflows and handoffs. If you've written a README, a style guide, or onboarding documentation, this looks familiar because it that's effectively what it is. The files that configure AI agents are Markdown files with structured frontmatter. They're documentation.

The difference is the audience: instead of a human colleague, you're writing for an AI model that's highly knowledgeable but has zero institutional memory. The challenge is one technical communicators already navigate: deciding what to include, how to structure it, and what level of detail serves the reader.

So what kinds of files are involved?"

https://instructionmanuel.com/agent-configs-are-docs

#TechnicalWriting #AI #LLMs #AIAgents #AgenticAI #TechnicalCommunication #Markdown #README

"The people best positioned to configure AI agents like Claude Code aren't engineers. They're technical writers.

It's a bold claim, so let me back it up.

Here's a file that powers an AI agent:

AGENTS.md

# AGENTS.md — API Documentation Repository

## Workflow Rules

- Human review required for API reference changes
- Style guide compliance checked automatically via CI
- Maximum 3 AI revision cycles before human takeover

## Escalation

- Writer agent fails after 3 attempts → human writer takes over
- Reviewer agent flags accuracy concern → SME review required
Markdown syntax, structured headings, rules about workflows and handoffs. If you've written a README, a style guide, or onboarding documentation, this looks familiar because it that's effectively what it is. The files that configure AI agents are Markdown files with structured frontmatter. They're documentation.

The difference is the audience: instead of a human colleague, you're writing for an AI model that's highly knowledgeable but has zero institutional memory. The challenge is one technical communicators already navigate: deciding what to include, how to structure it, and what level of detail serves the reader.

So what kinds of files are involved?"

https://instructionmanuel.com/agent-configs-are-docs

#TechnicalWriting #AI #LLMs #AIAgents #AgenticAI #TechnicalCommunication #Markdown #README

"The people best positioned to configure AI agents like Claude Code aren't engineers. They're technical writers.

It's a bold claim, so let me back it up.

Here's a file that powers an AI agent:

AGENTS.md

# AGENTS.md — API Documentation Repository

## Workflow Rules

- Human review required for API reference changes
- Style guide compliance checked automatically via CI
- Maximum 3 AI revision cycles before human takeover

## Escalation

- Writer agent fails after 3 attempts → human writer takes over
- Reviewer agent flags accuracy concern → SME review required
Markdown syntax, structured headings, rules about workflows and handoffs. If you've written a README, a style guide, or onboarding documentation, this looks familiar because it that's effectively what it is. The files that configure AI agents are Markdown files with structured frontmatter. They're documentation.

The difference is the audience: instead of a human colleague, you're writing for an AI model that's highly knowledgeable but has zero institutional memory. The challenge is one technical communicators already navigate: deciding what to include, how to structure it, and what level of detail serves the reader.

So what kinds of files are involved?"

https://instructionmanuel.com/agent-configs-are-docs

#TechnicalWriting #AI #LLMs #AIAgents #AgenticAI #TechnicalCommunication #Markdown #README

"In my post The Emerging Picture of a Changed Profession: Cyborg Technical Writers — Augmented, Not Replaced, by AI, I mentioned an upcoming presentation I'm giving to students and faculty. I argue that the future of the profession is the cyborg model, where machines augment our capabilities rather than replace us. In this post, I share notes about what skills a tech writer would need to learn to thrive in this world of augmentation.

If you have feedback about these skills, let me know. My intent here is to demonstrate what actual skills should be emphasized for those entering the profession, or for those currently in the profession who want to get ahead with AI. Note that the following sections are mostly bullet points, in the form of notes."

https://idratherbewriting.com/blog/10-principles-of-cyborg-technical-writer

#TechnicalWriting #TechnicalCommunication #SoftwareDocumentation #Documentation #AI #GenerativeAI #LLMs

Indeed, we can't allow autopilot to head into a whirlwind...

"We may be doing docs-as-code, but docs are not code. Docs run on people, and people are a messy tangle of goals, skills, and emotions. When docs hit the brain, they meet varying expectations, knowledge levels, reading abilities, and needs. None of this can be reproduced or simplified to a single pattern, but good docs use structure and words wisely to produce the best possible linguistic shape that can land safely on most people’s heads. Only humans can decide whether that message is getting across in the right way.

Getting there is a balancing act between business needs, user needs, and your own. That’s the diplomatic tension that forces all good tech writers to slow down and consider all points of view in the room as if they were in the middle of a spaghetti Western standoff. Slowing down is a deliberate, necessary act in all crafts, and tech writing is no exception. No matter how fast LLMs can churn out drafts, they don’t understand the tension in tech writing, to which we’re adding AI itself as an additional consumer of docs.
(...)
The quality of the docs I produce is still high, I was saying. That’s because I’m not letting LLMs take the steering wheel, and because I’m building new habits around them: setting up guardrails, automating what can be automated, and keeping my hands on the decisions that matter. I can do that because I know what good docs look like, and because I’ve been doing this long enough to feel when something’s off. That intuition came from years of wrestling with products and watching users struggle with pages I thought were clear. AI can help me write faster. It cannot replace the slow accumulation of judgment that tells me when to stop."

https://passo.uno/real-cost-of-documentation/

#TechnicalWriting #SoftwareDocumentation #AI #DocsAsCode #GenerativeAI #LLMs #SoftwareDevelopment #AISlop #Programming #TechnicalCommunication #Documentation

"Too often, API documentation writing is introduced as a series of rules or gut feeling about what seems obvious. Beginning writing, that’s a good approach. They’re easily understood and conform to. They’re rarely wrong. They’re far from complete, however.

API documentation writing is an art, not a science. As the artist, your influence is no less important than anyone else’s. But you’ll need to understand more in order to take the writing to a new level. You’ll need to know theory, the hows and whys, and to think like a programmer. The theory here is not only to connect with clients but also to present information in the most efficient way possible. It’s the last points that learning API documentation writing does not do well.

The following is a talk through. I talk about an element in conversational detail. I aim to discuss the important points, why an approach may be inappropriate, what the goals should be, and how to fix it. Along the way, I may make blunt statements. I do that for effect. By exposing the reason for the critique, we can get an understanding of the solution. We’ll look at this from the writer’s perspective."

https://robertdelwood.medium.com/improving-api-documentation-describing-one-parameter-at-a-time-cb53a89637a2?postPublishedType=initial

#TechnicalWriting #APIDocumentation #SoftwareDocumentation #SoftwareDevelopment #Programming #APIs #TechnicalCommunication

Architect Elevator Complete Collection by Gregor Hohpe is the featured bundle on Leanpub!

Own all three books in the Architect Elevator series for 900 pages of large-scale IT architecture! First, rethink the role of the architect, and then apply it to two major anchors of any IT strategy: cloud computing and platforms.

Link: https://leanpub.com/b/architectelevatorcollection

#SoftwareArchitecture #ComputerProgramming #DigitalTransformation #EnterpriseArchitecture #BusinessItAlignment #TechnicalCommunication

Architect Elevator Complete Collection by Gregor Hohpe is the featured bundle on Leanpub!

Own all three books in the Architect Elevator series for 900 pages of large-scale IT architecture! First, rethink the role of the architect, and then apply it to two major anchors of any IT strategy: cloud computing and platforms.

Link: https://leanpub.com/b/architectelevatorcollection

#SoftwareArchitecture #ComputerProgramming #DigitalTransformation #EnterpriseArchitecture #BusinessItAlignment #TechnicalCommunication

Architect Elevator Complete Collection by Gregor Hohpe is the featured bundle on Leanpub!

Own all three books in the Architect Elevator series for 900 pages of large-scale IT architecture! First, rethink the role of the architect, and then apply it to two major anchors of any IT strategy: cloud computing and platforms.

Link: https://leanpub.com/b/architectelevatorcollection

#SoftwareArchitecture #ComputerProgramming #DigitalTransformation #EnterpriseArchitecture #BusinessItAlignment #TechnicalCommunication

Architect Elevator Complete Collection by Gregor Hohpe is the featured bundle on Leanpub!

Own all three books in the Architect Elevator series for 900 pages of large-scale IT architecture! First, rethink the role of the architect, and then apply it to two major anchors of any IT strategy: cloud computing and platforms.

Link: https://leanpub.com/b/architectelevatorcollection

#SoftwareArchitecture #ComputerProgramming #DigitalTransformation #EnterpriseArchitecture #BusinessItAlignment #TechnicalCommunication

"Over the years, we’ve had the pleasure of hosting many exceptional speakers on the Nordic APIs stage. Our most memorable talks span architectural deep dives, anti-patterns, emerging trends, personal journeys, and hard-earned lessons on what it takes to build great API platforms.

To the audience, these presentations often look effortless. But the truth is, there’s a lot of preparation that goes on behind the scenes. This is especially true for the talks that resonate with the audience the most. So what separates an average tech talk from a standout one?

We checked in with a few of our most well-regarded speakers to pull the curtain back on their process, from originating an idea, all the way through to rehearsing it and nailing it with confidence on the day. The result is a set of practical tips for crafting tech talks that land. While the tips come from the API community and are geared toward tech talks, much of the wisdom applies to any public speaking engagement, whether you’re a first-time speaker or industry veteran.

And if reading these conference speaking tips leaves you inspired to take the stage yourself, we’d love to hear from you. Consider submitting a talk proposal for Platform Summit."

https://nordicapis.com/10-tips-on-giving-standout-talks-at-developer-conferences/

#DeveloperRelations #DeveloperExperience #DX #Presentations #TechnicalCommunication #APIs

"Over the years, we’ve had the pleasure of hosting many exceptional speakers on the Nordic APIs stage. Our most memorable talks span architectural deep dives, anti-patterns, emerging trends, personal journeys, and hard-earned lessons on what it takes to build great API platforms.

To the audience, these presentations often look effortless. But the truth is, there’s a lot of preparation that goes on behind the scenes. This is especially true for the talks that resonate with the audience the most. So what separates an average tech talk from a standout one?

We checked in with a few of our most well-regarded speakers to pull the curtain back on their process, from originating an idea, all the way through to rehearsing it and nailing it with confidence on the day. The result is a set of practical tips for crafting tech talks that land. While the tips come from the API community and are geared toward tech talks, much of the wisdom applies to any public speaking engagement, whether you’re a first-time speaker or industry veteran.

And if reading these conference speaking tips leaves you inspired to take the stage yourself, we’d love to hear from you. Consider submitting a talk proposal for Platform Summit."

https://nordicapis.com/10-tips-on-giving-standout-talks-at-developer-conferences/

#DeveloperRelations #DeveloperExperience #DX #Presentations #TechnicalCommunication #APIs

"Over the years, we’ve had the pleasure of hosting many exceptional speakers on the Nordic APIs stage. Our most memorable talks span architectural deep dives, anti-patterns, emerging trends, personal journeys, and hard-earned lessons on what it takes to build great API platforms.

To the audience, these presentations often look effortless. But the truth is, there’s a lot of preparation that goes on behind the scenes. This is especially true for the talks that resonate with the audience the most. So what separates an average tech talk from a standout one?

We checked in with a few of our most well-regarded speakers to pull the curtain back on their process, from originating an idea, all the way through to rehearsing it and nailing it with confidence on the day. The result is a set of practical tips for crafting tech talks that land. While the tips come from the API community and are geared toward tech talks, much of the wisdom applies to any public speaking engagement, whether you’re a first-time speaker or industry veteran.

And if reading these conference speaking tips leaves you inspired to take the stage yourself, we’d love to hear from you. Consider submitting a talk proposal for Platform Summit."

https://nordicapis.com/10-tips-on-giving-standout-talks-at-developer-conferences/

#DeveloperRelations #DeveloperExperience #DX #Presentations #TechnicalCommunication #APIs

"Over the years, we’ve had the pleasure of hosting many exceptional speakers on the Nordic APIs stage. Our most memorable talks span architectural deep dives, anti-patterns, emerging trends, personal journeys, and hard-earned lessons on what it takes to build great API platforms.

To the audience, these presentations often look effortless. But the truth is, there’s a lot of preparation that goes on behind the scenes. This is especially true for the talks that resonate with the audience the most. So what separates an average tech talk from a standout one?

We checked in with a few of our most well-regarded speakers to pull the curtain back on their process, from originating an idea, all the way through to rehearsing it and nailing it with confidence on the day. The result is a set of practical tips for crafting tech talks that land. While the tips come from the API community and are geared toward tech talks, much of the wisdom applies to any public speaking engagement, whether you’re a first-time speaker or industry veteran.

And if reading these conference speaking tips leaves you inspired to take the stage yourself, we’d love to hear from you. Consider submitting a talk proposal for Platform Summit."

https://nordicapis.com/10-tips-on-giving-standout-talks-at-developer-conferences/

#DeveloperRelations #DeveloperExperience #DX #Presentations #TechnicalCommunication #APIs

"Over the years, we’ve had the pleasure of hosting many exceptional speakers on the Nordic APIs stage. Our most memorable talks span architectural deep dives, anti-patterns, emerging trends, personal journeys, and hard-earned lessons on what it takes to build great API platforms.

To the audience, these presentations often look effortless. But the truth is, there’s a lot of preparation that goes on behind the scenes. This is especially true for the talks that resonate with the audience the most. So what separates an average tech talk from a standout one?

We checked in with a few of our most well-regarded speakers to pull the curtain back on their process, from originating an idea, all the way through to rehearsing it and nailing it with confidence on the day. The result is a set of practical tips for crafting tech talks that land. While the tips come from the API community and are geared toward tech talks, much of the wisdom applies to any public speaking engagement, whether you’re a first-time speaker or industry veteran.

And if reading these conference speaking tips leaves you inspired to take the stage yourself, we’d love to hear from you. Consider submitting a talk proposal for Platform Summit."

https://nordicapis.com/10-tips-on-giving-standout-talks-at-developer-conferences/

#DeveloperRelations #DeveloperExperience #DX #Presentations #TechnicalCommunication #APIs

"Over the weekend, I spent about 10 hours working with Claude to manually validate 578 coding patterns across a range of languages and coding tasks for my Agent Skill Report. We had to deep dive into standard library docs, package-specific documentation, large enterprise docs, and personal blogs. My goal was to ensure that every API and configuration pattern I was using in a behavioral evaluation experiment reflected the current guidance from official sources. My learnings about agent docs access patterns were secondary to this project, but the results are a rich treasure trove of data that may inform how I use agents with docs in the future. As a technical writer who has worked on SaaS and developer docs for the last decade, honestly, my findings made me a little sad.
(...)
My high-level takeaway was this: I expected an agent to try to use docs like I do, and was very surprised when it didn’t.
(...)
Over the course of validating 578 patterns across 20 different skills, my agent and I built up a pretty comprehensive picture of what documentation access patterns actually work for agents, and which ones don’t. I had my agent keep a running reference doc of its learnings, and by the end of the project, the patterns were clear enough to categorize."

https://dacharycarey.com/2026/02/18/agent-friendly-docs/

#TechnicalWriting #TechnicalCommunication #AI #AIAgents #LLMs #Chatbots #AgenticAI #SoftwareDocumentation #APIs #Docs #Documentation

"When we write documentation, we often assume someone will read it top to bottom. Even when we skim, we start at the top, absorb context, build a mental model. And we infer stuff, like if you’re reading design system docs, you probably already know what a design system is.

AI agents don’t work like this. They retrieve the most relevant chunk based on semantic similarity and produce a response from that slice. If the definition is three paragraphs in and the agent retrieves paragraph one, it fills in the gaps.

That’s where hallucination creeps in. You’re absolutely right! Not because the model is careless, but because much of our documentation is structured for narrative flow, not retrieval. It was always fragile, humans were just good at compensating.

Writing for AI agents accidentally makes documentation more accessible. A screen reader user navigating by headings needs the same explicitness an AI agent needs. A new team member needs definitions that don’t assume prior knowledge. A developer working in a second language needs sentences that say exactly what they mean. Explicitness helps anyone who can’t rely on context to fill gaps.

Look at well-documented APIs. The ones that specify exactly what parameters do, what they return, what breaks. They’re used more, trusted more, cause fewer support tickets. Explicitness scales."

https://gerireid.com/blog/ai-is-accidently-making-documentation-accessible/

#TechnicalWriting #Acessibility #TechnicalCommunication #AI #SoftwareDocumentation #AIAgents #APIDocumentation #Markdown

"The secret of how tech writers develop trustworthy information is that they practice genuine care for the end-to-end experience, learn the product experience inside and out (even if they start as an outsider), and build context that you can’t just get from writing.

This is “earned” context through building trust across other teams and stakeholders and through shipping successful (and unsuccessful) products in different environments and working cultures.

Tech writers (or whatever they’re called these days) are paid to develop (and maintain) trustworthy information, not just move it around. Automation can help with maintaining trustworthy information but it’s not all that technical writers do.

Earning or developing context well also takes real skills and demands a certain kind of character.

Skills & traits for developing trustworthy information

- Asking the right questions in the right way in the right place and at the right time. It’s no accident that some of the best technical writers I’ve worked with used to work as journalists.
- Constantly tracking what you know and don’t know with intellectual humility and rigor (Stay tuned for my future “Assumption Tracker app!”)
- Facilitating discussions to help surface internal confusion, misalignments, and other kinds of conversation debt
- Evaluating the trustworthiness of information
- Evaluating what others know, what product language world they live in, and what they don’t know
- Intellectual humility, honesty, and rigor"

https://jessicacanepa.com/blog/developing-trustworthy-information/

#TechnicalWriting #SoftwareDocumentation #TechnicalCommunication #SoftwareDevelopment #APIDocumentation #Automation

💯 👉 "When you say "docs", you're careful to focus on the output, omitting the process. Perhaps you don't know how docs are produced. You've forgotten, or perhaps never knew, that docs are product truth; that without them, software becomes unusable, because software is never done, is never obvious, and is never simple. Producing those docs requires tech writers.

Tech writers go to great lengths to get the information they need. They write so that your audience can understand. They hunger for clarity and meaning and impact. They power through weeks full of deadlines, chasing product news, because without their reporting, most products wouldn't thrive; some wouldn't even exist. The documentation they produce is not a byproduct of development: it's the glue that ties the product together.

An LLM can't do all that, because it can't feel the pain of your users. It can't put itself into their shoes. It lacks the kind of empathy that's behind great help content. It does not, in fact, have any empathy at all, because it cannot care. You need folks who will care, because content is a hairy beast that can only be tamed by agents made of flesh and capable of emotions: humans." 👈 💯

https://passo.uno/reconsider/

#TechnicalWriting #AI #SoftwareDocumentation #TechnicalCommunication #GenerativeAI #LLMs #Docs #Documentation #SoftwareDevelopment

"This article examines several more common problems occurring in API documentation. They are easily prevented or have simple workarounds but the writer must be aware of them in the first place. These underscore the importance of:

- Writers being familiar with programming and development concepts, so that,
- Writers can think like developers. Only by thinking like a developer can writers then hone in on client’s nuances, customize the developer experience, and optimize the time in the documentation. The goal is an ironic one. We want documentation so good and clear that clients don’t even have to read it. You’ll see what I mean in a moment.

The striking thing about these is how simple they seem. So much so, they are often overlooked. Afterall, how much can be said about an offset value of a returned list, or sorting? As it turns out, plenty. Thinking like developer is encompassing. Enough information must be presented so that clients know ahead of time what the field or endpoint does, returns, what the behavior is, and what each parameter does. You have to anticipate questions and understand how clients think about things. The last thing we writers want for clients is to make them experiment with values and guess outcomes. That annoys them and wastes their time. It means we didn’t do our job.

API documentation is not technical writing. It’s API documentation writing. The key differences are the dependence on code and a deep understanding of development practices. There are countless nuances and subtleties — and each one matters to developers. How can it not? You’re writing to developers about development. It needs to be precise and it needs to speak their language."

https://robertdelwood.medium.com/more-common-api-documentation-errors-26f1a8ceaaec

#APIs #APIDocumentation #TechnicalWriting #Programming #SoftwareDevelopment #TechnicalCommunication

"Lint your docs like code: turn any style guide into enforceable rules with Vale and publish clear, consistent content every time.

Create consistent content that gives readers confidence with Vale, the open-source prose linter that helps you enforce your style guide automatically. Use battle-tested rules based on freely available, popular style guides, apply your brand’s terms with a custom vocabulary, and integrate Vale into your text editor, Git hooks, and CI pipeline. Catch typos and inclusive-language issues before they ship, and spend your energy on shaping ideas instead of fixing copy. Whether you’re a technical writer working in a docs-as-code environment, or a software engineer who occasionally writes, you’ll ship clean, consistent copy every time.

When you work on a content project, keeping things consistent can feel impossible. Typos slip through, people don’t follow style rules, and each contributor brings a slightly different voice. Vale helps you ensure consistency across your content.

You’ll start by catching typos as you learn how Vale works through hands-on examples. Then you’ll bring in community rules based on Google’s and Microsoft’s style guides. You’ll combine overlapping styles, adjust the rules to match your needs, and start shaping the experience you want readers to have. Then you’ll build your own rules from scratch and create a custom vocabulary to teach Vale to enforce your team’s voice and jargon. By the end, you’ll have a fully integrated, reusable style package that works in your editor, GitHub Actions, and your build systems. And while this book uses Markdown in its examples, you’ll be ready to apply everything you learned to reStructuredText, AsciiDoc, and even the comments in your source code.

Vale gives you a fast, reliable, and customizable way to keep your content consistent."

https://books.google.pt/books?id=nMabEQAAQBAJ

#TechnicalWriting #Vale #Markdown #DocsAsCode #StyleGuides #TechnicalCommunication

"Lint your docs like code: turn any style guide into enforceable rules with Vale and publish clear, consistent content every time.

Create consistent content that gives readers confidence with Vale, the open-source prose linter that helps you enforce your style guide automatically. Use battle-tested rules based on freely available, popular style guides, apply your brand’s terms with a custom vocabulary, and integrate Vale into your text editor, Git hooks, and CI pipeline. Catch typos and inclusive-language issues before they ship, and spend your energy on shaping ideas instead of fixing copy. Whether you’re a technical writer working in a docs-as-code environment, or a software engineer who occasionally writes, you’ll ship clean, consistent copy every time.

When you work on a content project, keeping things consistent can feel impossible. Typos slip through, people don’t follow style rules, and each contributor brings a slightly different voice. Vale helps you ensure consistency across your content.

You’ll start by catching typos as you learn how Vale works through hands-on examples. Then you’ll bring in community rules based on Google’s and Microsoft’s style guides. You’ll combine overlapping styles, adjust the rules to match your needs, and start shaping the experience you want readers to have. Then you’ll build your own rules from scratch and create a custom vocabulary to teach Vale to enforce your team’s voice and jargon. By the end, you’ll have a fully integrated, reusable style package that works in your editor, GitHub Actions, and your build systems. And while this book uses Markdown in its examples, you’ll be ready to apply everything you learned to reStructuredText, AsciiDoc, and even the comments in your source code.

Vale gives you a fast, reliable, and customizable way to keep your content consistent."

https://books.google.pt/books?id=nMabEQAAQBAJ

#TechnicalWriting #Vale #Markdown #DocsAsCode #StyleGuides #TechnicalCommunication

"Lint your docs like code: turn any style guide into enforceable rules with Vale and publish clear, consistent content every time.

Create consistent content that gives readers confidence with Vale, the open-source prose linter that helps you enforce your style guide automatically. Use battle-tested rules based on freely available, popular style guides, apply your brand’s terms with a custom vocabulary, and integrate Vale into your text editor, Git hooks, and CI pipeline. Catch typos and inclusive-language issues before they ship, and spend your energy on shaping ideas instead of fixing copy. Whether you’re a technical writer working in a docs-as-code environment, or a software engineer who occasionally writes, you’ll ship clean, consistent copy every time.

When you work on a content project, keeping things consistent can feel impossible. Typos slip through, people don’t follow style rules, and each contributor brings a slightly different voice. Vale helps you ensure consistency across your content.

You’ll start by catching typos as you learn how Vale works through hands-on examples. Then you’ll bring in community rules based on Google’s and Microsoft’s style guides. You’ll combine overlapping styles, adjust the rules to match your needs, and start shaping the experience you want readers to have. Then you’ll build your own rules from scratch and create a custom vocabulary to teach Vale to enforce your team’s voice and jargon. By the end, you’ll have a fully integrated, reusable style package that works in your editor, GitHub Actions, and your build systems. And while this book uses Markdown in its examples, you’ll be ready to apply everything you learned to reStructuredText, AsciiDoc, and even the comments in your source code.

Vale gives you a fast, reliable, and customizable way to keep your content consistent."

https://books.google.pt/books?id=nMabEQAAQBAJ

#TechnicalWriting #Vale #Markdown #DocsAsCode #StyleGuides #TechnicalCommunication

"Lint your docs like code: turn any style guide into enforceable rules with Vale and publish clear, consistent content every time.

Create consistent content that gives readers confidence with Vale, the open-source prose linter that helps you enforce your style guide automatically. Use battle-tested rules based on freely available, popular style guides, apply your brand’s terms with a custom vocabulary, and integrate Vale into your text editor, Git hooks, and CI pipeline. Catch typos and inclusive-language issues before they ship, and spend your energy on shaping ideas instead of fixing copy. Whether you’re a technical writer working in a docs-as-code environment, or a software engineer who occasionally writes, you’ll ship clean, consistent copy every time.

When you work on a content project, keeping things consistent can feel impossible. Typos slip through, people don’t follow style rules, and each contributor brings a slightly different voice. Vale helps you ensure consistency across your content.

You’ll start by catching typos as you learn how Vale works through hands-on examples. Then you’ll bring in community rules based on Google’s and Microsoft’s style guides. You’ll combine overlapping styles, adjust the rules to match your needs, and start shaping the experience you want readers to have. Then you’ll build your own rules from scratch and create a custom vocabulary to teach Vale to enforce your team’s voice and jargon. By the end, you’ll have a fully integrated, reusable style package that works in your editor, GitHub Actions, and your build systems. And while this book uses Markdown in its examples, you’ll be ready to apply everything you learned to reStructuredText, AsciiDoc, and even the comments in your source code.

Vale gives you a fast, reliable, and customizable way to keep your content consistent."

https://books.google.pt/books?id=nMabEQAAQBAJ

#TechnicalWriting #Vale #Markdown #DocsAsCode #StyleGuides #TechnicalCommunication

"Lint your docs like code: turn any style guide into enforceable rules with Vale and publish clear, consistent content every time.

Create consistent content that gives readers confidence with Vale, the open-source prose linter that helps you enforce your style guide automatically. Use battle-tested rules based on freely available, popular style guides, apply your brand’s terms with a custom vocabulary, and integrate Vale into your text editor, Git hooks, and CI pipeline. Catch typos and inclusive-language issues before they ship, and spend your energy on shaping ideas instead of fixing copy. Whether you’re a technical writer working in a docs-as-code environment, or a software engineer who occasionally writes, you’ll ship clean, consistent copy every time.

When you work on a content project, keeping things consistent can feel impossible. Typos slip through, people don’t follow style rules, and each contributor brings a slightly different voice. Vale helps you ensure consistency across your content.

You’ll start by catching typos as you learn how Vale works through hands-on examples. Then you’ll bring in community rules based on Google’s and Microsoft’s style guides. You’ll combine overlapping styles, adjust the rules to match your needs, and start shaping the experience you want readers to have. Then you’ll build your own rules from scratch and create a custom vocabulary to teach Vale to enforce your team’s voice and jargon. By the end, you’ll have a fully integrated, reusable style package that works in your editor, GitHub Actions, and your build systems. And while this book uses Markdown in its examples, you’ll be ready to apply everything you learned to reStructuredText, AsciiDoc, and even the comments in your source code.

Vale gives you a fast, reliable, and customizable way to keep your content consistent."

https://books.google.pt/books?id=nMabEQAAQBAJ

#TechnicalWriting #Vale #Markdown #DocsAsCode #StyleGuides #TechnicalCommunication

LoL. Have Big Tech companies finally realised that they're almost worthless without writers who can tell stories?

"Corporate America’s latest hot job is also one of the oldest in history: storyteller.

Some companies want a media relations manager by a slightly flashier name. Others need people to produce blogs, podcasts, case studies and more types of branded content to attract customers, investors and potential recruits. All seem to use the word differently than in its usual application to novelists, playwrights and raconteurs.

“As storytellers,” a Google job ad said last month, “we play an integral role in driving customer acquisition and long-term growth.”

The listing sought a customer storytelling manager to join the company’s Google Cloud storytelling team. One article the unit published this year was titled, “Lowe’s innovation: How Vertex AI helps create interactive shopping experiences.”

Microsoft’s security organization meanwhile is recruiting a senior director overseeing narrative and storytelling, described as part cybersecurity technologist, part communicator and part marketer. Compliance technology firm Vanta this month began hiring for a head of storytelling, offering a salary of up to $274,000. Productivity app Notion recently merged its communications, social media and influencer functions into one 10-person, so-called storytelling team."

https://www.wsj.com/articles/companies-are-desperately-seeking-storytellers-7b79f54e

#Google #BigTech #Storyteling #Microsoft #Writing #TechnicalCommunication

LoL. Have Big Tech companies finally realised that they're almost worthless without writers who can tell stories?

"Corporate America’s latest hot job is also one of the oldest in history: storyteller.

Some companies want a media relations manager by a slightly flashier name. Others need people to produce blogs, podcasts, case studies and more types of branded content to attract customers, investors and potential recruits. All seem to use the word differently than in its usual application to novelists, playwrights and raconteurs.

“As storytellers,” a Google job ad said last month, “we play an integral role in driving customer acquisition and long-term growth.”

The listing sought a customer storytelling manager to join the company’s Google Cloud storytelling team. One article the unit published this year was titled, “Lowe’s innovation: How Vertex AI helps create interactive shopping experiences.”

Microsoft’s security organization meanwhile is recruiting a senior director overseeing narrative and storytelling, described as part cybersecurity technologist, part communicator and part marketer. Compliance technology firm Vanta this month began hiring for a head of storytelling, offering a salary of up to $274,000. Productivity app Notion recently merged its communications, social media and influencer functions into one 10-person, so-called storytelling team."

https://www.wsj.com/articles/companies-are-desperately-seeking-storytellers-7b79f54e

#Google #BigTech #Storyteling #Microsoft #Writing #TechnicalCommunication

LoL. Have Big Tech companies finally realised that they're almost worthless without writers who can tell stories?

"Corporate America’s latest hot job is also one of the oldest in history: storyteller.

Some companies want a media relations manager by a slightly flashier name. Others need people to produce blogs, podcasts, case studies and more types of branded content to attract customers, investors and potential recruits. All seem to use the word differently than in its usual application to novelists, playwrights and raconteurs.

“As storytellers,” a Google job ad said last month, “we play an integral role in driving customer acquisition and long-term growth.”

The listing sought a customer storytelling manager to join the company’s Google Cloud storytelling team. One article the unit published this year was titled, “Lowe’s innovation: How Vertex AI helps create interactive shopping experiences.”

Microsoft’s security organization meanwhile is recruiting a senior director overseeing narrative and storytelling, described as part cybersecurity technologist, part communicator and part marketer. Compliance technology firm Vanta this month began hiring for a head of storytelling, offering a salary of up to $274,000. Productivity app Notion recently merged its communications, social media and influencer functions into one 10-person, so-called storytelling team."

https://www.wsj.com/articles/companies-are-desperately-seeking-storytellers-7b79f54e

#Google #BigTech #Storyteling #Microsoft #Writing #TechnicalCommunication

LoL. Have Big Tech companies finally realised that they're almost worthless without writers who can tell stories?

"Corporate America’s latest hot job is also one of the oldest in history: storyteller.

Some companies want a media relations manager by a slightly flashier name. Others need people to produce blogs, podcasts, case studies and more types of branded content to attract customers, investors and potential recruits. All seem to use the word differently than in its usual application to novelists, playwrights and raconteurs.

“As storytellers,” a Google job ad said last month, “we play an integral role in driving customer acquisition and long-term growth.”

The listing sought a customer storytelling manager to join the company’s Google Cloud storytelling team. One article the unit published this year was titled, “Lowe’s innovation: How Vertex AI helps create interactive shopping experiences.”

Microsoft’s security organization meanwhile is recruiting a senior director overseeing narrative and storytelling, described as part cybersecurity technologist, part communicator and part marketer. Compliance technology firm Vanta this month began hiring for a head of storytelling, offering a salary of up to $274,000. Productivity app Notion recently merged its communications, social media and influencer functions into one 10-person, so-called storytelling team."

https://www.wsj.com/articles/companies-are-desperately-seeking-storytellers-7b79f54e

#Google #BigTech #Storyteling #Microsoft #Writing #TechnicalCommunication

LoL. Have Big Tech companies finally realised that they're almost worthless without writers who can tell stories?

"Corporate America’s latest hot job is also one of the oldest in history: storyteller.

Some companies want a media relations manager by a slightly flashier name. Others need people to produce blogs, podcasts, case studies and more types of branded content to attract customers, investors and potential recruits. All seem to use the word differently than in its usual application to novelists, playwrights and raconteurs.

“As storytellers,” a Google job ad said last month, “we play an integral role in driving customer acquisition and long-term growth.”

The listing sought a customer storytelling manager to join the company’s Google Cloud storytelling team. One article the unit published this year was titled, “Lowe’s innovation: How Vertex AI helps create interactive shopping experiences.”

Microsoft’s security organization meanwhile is recruiting a senior director overseeing narrative and storytelling, described as part cybersecurity technologist, part communicator and part marketer. Compliance technology firm Vanta this month began hiring for a head of storytelling, offering a salary of up to $274,000. Productivity app Notion recently merged its communications, social media and influencer functions into one 10-person, so-called storytelling team."

https://www.wsj.com/articles/companies-are-desperately-seeking-storytellers-7b79f54e

#Google #BigTech #Storyteling #Microsoft #Writing #TechnicalCommunication

"AI tools are moving the floor up. There’s more being expected of writers and I worry that junior roles, just like they are in engineering, are going away.

The basis of the craft is changing. Being a good writer, whatever the field, takes time and training. It’s a field of instruction, pedagogy, information stewardship. It’s part marketing, education, support, and engineering. By definition, it is different from being an engineer, but now that market is demanding both roles in one. This is a new, demanding environment and market.

I think we need to think very differently about what a technical writer role is and pivot accordingly. I’ve seen many people writing about AI tools, and yes, that’s great. But there is a huge opportunity for us to think bigger about this role and at a top level: What does a full stack docs strategy (and yes here are some AI tools to help build that). What does it mean to help build a unified data model for APIs? What information architectures do different docs portals need and how can we implement front-ends to maximize that structure for the best-in-class user experiences (leverage AI accordingly)? DocsX (docs experience) now has to be considered a full stack problem. So let’s get to it."

https://medium.com/@anandi.silva.knuppel/the-engineering-of-the-technical-writer-89092b609cf0

#TechnicalWriting #AI #GenerativeAI #TechnicalCommunication #DocumentationEngineer #DocsX #FullStack #SoftwareDocumentation

"AI tools are moving the floor up. There’s more being expected of writers and I worry that junior roles, just like they are in engineering, are going away.

The basis of the craft is changing. Being a good writer, whatever the field, takes time and training. It’s a field of instruction, pedagogy, information stewardship. It’s part marketing, education, support, and engineering. By definition, it is different from being an engineer, but now that market is demanding both roles in one. This is a new, demanding environment and market.

I think we need to think very differently about what a technical writer role is and pivot accordingly. I’ve seen many people writing about AI tools, and yes, that’s great. But there is a huge opportunity for us to think bigger about this role and at a top level: What does a full stack docs strategy (and yes here are some AI tools to help build that). What does it mean to help build a unified data model for APIs? What information architectures do different docs portals need and how can we implement front-ends to maximize that structure for the best-in-class user experiences (leverage AI accordingly)? DocsX (docs experience) now has to be considered a full stack problem. So let’s get to it."

https://medium.com/@anandi.silva.knuppel/the-engineering-of-the-technical-writer-89092b609cf0

#TechnicalWriting #AI #GenerativeAI #TechnicalCommunication #DocumentationEngineer #DocsX #FullStack #SoftwareDocumentation

"AI tools are moving the floor up. There’s more being expected of writers and I worry that junior roles, just like they are in engineering, are going away.

The basis of the craft is changing. Being a good writer, whatever the field, takes time and training. It’s a field of instruction, pedagogy, information stewardship. It’s part marketing, education, support, and engineering. By definition, it is different from being an engineer, but now that market is demanding both roles in one. This is a new, demanding environment and market.

I think we need to think very differently about what a technical writer role is and pivot accordingly. I’ve seen many people writing about AI tools, and yes, that’s great. But there is a huge opportunity for us to think bigger about this role and at a top level: What does a full stack docs strategy (and yes here are some AI tools to help build that). What does it mean to help build a unified data model for APIs? What information architectures do different docs portals need and how can we implement front-ends to maximize that structure for the best-in-class user experiences (leverage AI accordingly)? DocsX (docs experience) now has to be considered a full stack problem. So let’s get to it."

https://medium.com/@anandi.silva.knuppel/the-engineering-of-the-technical-writer-89092b609cf0

#TechnicalWriting #AI #GenerativeAI #TechnicalCommunication #DocumentationEngineer #DocsX #FullStack #SoftwareDocumentation

"AI tools are moving the floor up. There’s more being expected of writers and I worry that junior roles, just like they are in engineering, are going away.

The basis of the craft is changing. Being a good writer, whatever the field, takes time and training. It’s a field of instruction, pedagogy, information stewardship. It’s part marketing, education, support, and engineering. By definition, it is different from being an engineer, but now that market is demanding both roles in one. This is a new, demanding environment and market.

I think we need to think very differently about what a technical writer role is and pivot accordingly. I’ve seen many people writing about AI tools, and yes, that’s great. But there is a huge opportunity for us to think bigger about this role and at a top level: What does a full stack docs strategy (and yes here are some AI tools to help build that). What does it mean to help build a unified data model for APIs? What information architectures do different docs portals need and how can we implement front-ends to maximize that structure for the best-in-class user experiences (leverage AI accordingly)? DocsX (docs experience) now has to be considered a full stack problem. So let’s get to it."

https://medium.com/@anandi.silva.knuppel/the-engineering-of-the-technical-writer-89092b609cf0

#TechnicalWriting #AI #GenerativeAI #TechnicalCommunication #DocumentationEngineer #DocsX #FullStack #SoftwareDocumentation

"AI tools are moving the floor up. There’s more being expected of writers and I worry that junior roles, just like they are in engineering, are going away.

The basis of the craft is changing. Being a good writer, whatever the field, takes time and training. It’s a field of instruction, pedagogy, information stewardship. It’s part marketing, education, support, and engineering. By definition, it is different from being an engineer, but now that market is demanding both roles in one. This is a new, demanding environment and market.

I think we need to think very differently about what a technical writer role is and pivot accordingly. I’ve seen many people writing about AI tools, and yes, that’s great. But there is a huge opportunity for us to think bigger about this role and at a top level: What does a full stack docs strategy (and yes here are some AI tools to help build that). What does it mean to help build a unified data model for APIs? What information architectures do different docs portals need and how can we implement front-ends to maximize that structure for the best-in-class user experiences (leverage AI accordingly)? DocsX (docs experience) now has to be considered a full stack problem. So let’s get to it."

https://medium.com/@anandi.silva.knuppel/the-engineering-of-the-technical-writer-89092b609cf0

#TechnicalWriting #AI #GenerativeAI #TechnicalCommunication #DocumentationEngineer #DocsX #FullStack #SoftwareDocumentation

"Over the past few months, I’ve been talking with folks about how they find information and learn about a product. ChatGPT and Claude and Gemini (or at least Google’s “AI overview”) are consistently mentioned as one of the main methods people use. Even if the output isn’t that reliable, visiting an AI tool is still a key part of the information-finding flow.

AI tools are used for all sorts of information-finding flows:

- Answering basic questions about how to accomplish a task.
- Decipher the potential root cause of an error message and provide next steps for resolution.
- Provide solutions to intricate application design questions.
- Suggest syntax for code, a formula, or a SQL statement.

You need an AI strategy for your documentation to enable customers using AI to be more successful when using your product to accomplish their goals.

The components of an effective AI strategy include the following:

- Develop: Partner with teams building AI into your product.
- Discover: Evaluate and improve your content and content strategy.
- Measure: Measure how people use AI to interact with your documentation.
- Adapt: Explore use cases for AI in your documentation practice."

https://thisisimportant.net/posts/ai-strategy-for-documentation/

#AI #GenerativeAI #Chatbots #AIAgents #TechnicalWriting #TechnicalCommunication #SoftwareDocumentation #ContentStrategy

Designing Complex Systems: Enterprise, Heavy Data, and AI https://leanpub.com/designingcomplexsystems by Gideon Adeyemi is the featured book on the Leanpub homepage! https://leanpub.com #ComputerProgramming #GraphDesign #Graphics #Software #TechnicalCommunication

Find it on Leanpub!

Designing Complex Systems: Enterprise, Heavy Data, and AI https://leanpub.com/designingcomplexsystems by Gideon Adeyemi is the featured book on the Leanpub homepage! https://leanpub.com #ComputerProgramming #GraphDesign #Graphics #Software #TechnicalCommunication

Find it on Leanpub!

Designing Complex Systems: Enterprise, Heavy Data, and AI https://leanpub.com/designingcomplexsystems by Gideon Adeyemi is the featured book on the Leanpub homepage! https://leanpub.com #ComputerProgramming #GraphDesign #Graphics #Software #TechnicalCommunication

Find it on Leanpub!

Designing Complex Systems: Enterprise, Heavy Data, and AI https://leanpub.com/designingcomplexsystems by Gideon Adeyemi is the featured book on the Leanpub homepage! https://leanpub.com #ComputerProgramming #GraphDesign #Graphics #Software #TechnicalCommunication

Find it on Leanpub!

"The success of any AI initiative in technical communication depends on how responsibly it is applied. The workflows described so far – drafting, revision, and quality assurance – can all deliver real benefits, but only when guided by principles that protect clarity, accuracy, and accountability. Without those guardrails, AI becomes another source of noise rather than a tool for improvement.

The first principle is clarity. AI should never obscure meaning or introduce unnecessary complexity. Writers must always verify that generated or revised content still serves its audience and that explanations remain specific and concrete. A perfectly grammatical sentence that confuses readers is not an improvement.

The second principle is accuracy. AI systems cannot verify facts or interpret technical details with the precision of a subject matter expert. Any information produced or edited by a model must be checked against source materials and validated through established review channels. This step is not optional.

The third principle is accountability. Human writers and editors remain responsible for the content they publish, regardless of how it was created. That responsibility extends to ethical and legal considerations such as data privacy, bias mitigation, and compliance with organizational standards. Every AI-driven workflow should include clear documentation of how the system was used and who approved the results.

The final principle is transparency. Teams should share their AI practices openly within their organizations. This builds trust with stakeholders and prevents misuse born of misunderstanding. When people know what AI is doing and why, they are more likely to support its use.

Responsible adoption is what separates innovation from recklessness. The goal is not to prove that AI can write or edit, but to show that humans can use it wisely."

https://www.tcworld.info/e-magazine/technical-writing/why-ai-wont-replace-tech-writers-but-will-reshape-their-work

#AI #GenerativeAI #TechnicalWriting #TechnicalCommunication

Yep, DITA XML is still rocking in the technical communication world and technical writers need to have at least some familiarity with the topic.

https://learningdita.com/pluginfile.php/1/tool_certificate/issues/1762964073/6088999983MC.pdf

#DITA #DITAXML #TechnicalWriting #TechnicalCommunication #StructuredWriting

This week's Featured Links post links to articles about how Putin outsmarted the oil sanctions, how Charlie Angus is still haunted by the Edmund Fitzgerald sinking, how the Florentine diamond resurfaced after 100 years in hiding, and more.

https://coredump3.blogspot.com/2025/11/featured-links-november-11-2025.html

#GoogleDocs, #History, #Medical, #MicrosoftWord, #Movies #TV, #Politics, #SFF, #Software, #TechnicalCommunication, #Vision

Jetzt muss ich leider das Politische mit der Arbeit mischen. Bin wieder auf der #tekomjahrestagung und gleich der erste Vortrag war so gut, dass ich jetzt schon wieder fahren könnte. Bleibe trotzdem bis Donnerstag. ☺️

#tekom #tcworld #technicalcommunication

Jetzt muss ich leider das Politische mit der Arbeit mischen. Bin wieder auf der #tekomjahrestagung und gleich der erste Vortrag war so gut, dass ich jetzt schon wieder fahren könnte. Bleibe trotzdem bis Donnerstag. ☺️

#tekom #tcworld #technicalcommunication