Kevin R. Kuhl

The Boring Internet is a wonderful post by Terry Godier about what’s dying and what remains as the internet changes.

Paul Olson is a software engineer with a background in platform engineering and observability, and is working on an engineer’s history of web architecture.

While I’ve been looking for my next professional thing, I’ve been working on a community organization side project.

My love of RSS is something I’m not shy about.

Markdown is pretty cool.

Automations are great.

Here’s a really nice piece from Drew Bruenig about why you should write.

Writing about AI was hard.

In my previous post, I explained the theory behind the Publish on your Own Site, Syndicate Elsewhere (POSSE) script I’ve been working on for this blog.

I like the IndieWeb; it’s an idea and emerging set of standards for how to build independent websites that can talk to one another.

Over at This is important, Sarah Moir has an excellent discussion of AI strategy for technical writers and documentation teams.

Google just announced Code Wiki.

I’ve been posting a lot about technical writing recently, but I also like thinking about the Internet.

In a recent post, I covered various knowledge resources and docs-sites, including a brief discussion about knowledge bases.

Following a discussion on LinkedIn about why more technical writers should blog, I’ve joined a new project: the tech writing webring, started by Casey Smith.

As a technical writer, you will contribute to different kinds of documentation projects.

A couple of my more recent posts have been “link blogs”, but what am I doing when I do that and why put the effort in at all?

Great post from CT Smith at docsgoblin.com: At a previous role, WE WANT DOCS LIKE STRIPE was directed at me, with full eye contact during a meeting, by a leadership team that refused to give me any money for tooling or development resources.

My TV watching habits have changed pretty dramatically with the times.

One of the things that has surprised me most in my career was the extent to which you may need to advocate for your skills and the utility of your profession within a changing workplace.

If you’ve been interested in understanding the world of Bluesky and AT Proto, Kuba Suder has been writing excellent blog posts.

This document is a blueprint of my technical writing process.

This guide bridges the gap between raw API schemas and non-technical warehouse administrators.

Targeted at business stakeholders and admins, this guide demystifies the OAuth handshake to overcome security anxiety.

A vendor-agnostic architectural guide for IT administrators connecting cloud apps to on-premises hardware.

Here’s an excellent post on “reasoning” and “chain of thought” models by Drew Bruenig: What We Mean When We say “Think”.

This is a question I’ve been asking myself lately.

Docs (GitHub) is an open source alternative to Notion/Google Docs being built by the French and German governments (with the Netherlands being onboarded).

There’s a lot of great insights in this talk with Meredith Whittaker at SXSW.

This is a quick post inspired by a situation that someone posted about on r/TechnicalWriting.

I feel like technical writers are kind of a difficult creature to understand.

One of my goals for 2025 is to remove my dependency on social media.

One of the main reasons people use social media is to stay connected to the flow of information within their community.

I’ve been thinking about how generative AI impacts the ways people find, retrieve, and access information.

Welcome to my blog!