I don’t have a problem with llm-generated/assisted software, but I can’t handle LLM-generated blog posts. I read enough LLM output everyday already.
I understand, and I also don't like to read AI slop.
But the goal of using an LLM here was to provide an article where I can express my own thoughts, reflections, and building notes while making the speech clearer, easier to read, and more structured, as I am not a professional writer.
Anyway, I understand the frustration.
Thanks for letting me know, and have a good day !
> 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.'
joshstrange · · focus · HN ↗
nonmaskable · · focus · HN ↗
But the goal of using an LLM here was to provide an article where I can express my own thoughts, reflections, and building notes while making the speech clearer, easier to read, and more structured, as I am not a professional writer.
Anyway, I understand the frustration. Thanks for letting me know, and have a good day !
nateb2022 · · focus · HN ↗
> 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.'
nonmaskable · · focus · HN ↗
What I was trying to say is that if you only want grouped exceptions and a stack you can read, Sentry's default self-host is the wrong machine.
Their docs ask for almost 16 GB RAM.
And I just wanted a tool that runs on my VPS while keeping the official Sentry SDK (which is quite good).