Skip to content

Fix a broken mdash #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _posts/2025/03/2025-03-09-superintelligent-docs.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Now technical writers might need to do the same when it comes to documentation.

How do you define superintelligent docs? While various definitions could fit this bill, such as automated documentation that predicts topics based on user behavior or errors, or documentation that dynamically writes itself around the user's specific situation and needs, those imagined experiences are a bit too futuristic for me.

More realistically, superintelligent docs solve wicked problems. Wicked problems are so massive, gnarly, multifaceted, and hard to tackle — for example, they include variables that are constantly changing based on recurring feedback loops, etc. &mash; that they are beyong merely complicated problems; they are *complex problems*. Solving them seems beyond human capabilities.
More realistically, superintelligent docs solve wicked problems. Wicked problems are so massive, gnarly, multifaceted, and hard to tackle — for example, they include variables that are constantly changing based on recurring feedback loops, etc. — that they are beyong merely complicated problems; they are *complex problems*. Solving them seems beyond human capabilities.

## Wicked problems in the tech comm space

Expand Down