I find I greatly prefer to read non-professional writers in their own voice rather than the ideas regurgitated by an LLM. I promise I’m not trying to attack you or similar, just trying to give some advice.

It’s become a trope, but it’s true, if you feel the need to use an LLM, I’d rather you just post your outline/prompt. It’s smaller and easier to read.

LLM proofread? LLM suggestions? Sure, but always writing with your own words makes it infinitely more appealing, even if you aren’t the best writer.

I look back at many of my blog posts and cringe but it’s me, it’s clearly “me”. I’ve tried to use LLMs to mimic my “voice” but found them wanting and so I only use LLMs in communications to businesses/corporations, not individuals.

My, personal, line in the sand is any personal email, blog post, text message, discord/chat, etc will always be written by me. I think it comes down to respect for someone else’s time.

Perhaps I will be rolled over and lose this battle in the long term, but for now that’s where I’ll hold the line. And before someone says otherwise, I’m a _heavy_ LLM user, I’m a huge fan of them, but for communication and in things like blog posts I feel the need to be “me” and I think that makes for better reading, it improves the message I’m trying to convey which means more people will read it and/or consider it.

None of this speech is clear:

> Sentry's self-hosted RAM floor is the cost of a full suite. Design notes on an exception-only path: two containers, a DSN swap, and a dated RSS receipt.

This is the article's description. What is an exception-only path? I don't believe I've ever thought about designing one, and I don't understand its significant wrt the title whatsoever.

It's a really odd way to phrase a concept like "If you only care about logging errors, you can build 80% of Sentry for 20% of the engineering and infra costs."

> If you self-host on a small VPS and only need the next grouped exception, Sentry's RAM warning means the official install is a full suite. That suite is the undesired alternative.

This really reads like something a markov chain chatbot would write. Sentry's warning has nothing to do with installing a full suite. "That suite is the undesired alternative" is a really obtuse way to say bloated.

> A different job is narrower. When production throws, show a grouped issue with a stack you can read, and keep a crash loop from melting the box or the invoice. The rest of this note is that job.

A human would have written 'You don't need all of Sentry if you only need to log exceptions and stack traces.'

Well neither you or the LLM succeeded there. Tedious prose to read.