> Why there is a blog on a site that exists to give software away, and what is going to end up on it.
> Source: https://orochibraru.com/blog/this-is-where-i-rant · Site index: https://orochibraru.com/llms.txt

# This is where I rant

*9 September 2026*

I did not want a blog. Blogs are where good intentions go to die: three posts, a
"sorry for the long silence", then a dead domain. But I kept writing the same
paragraph into READMEs where nobody would ever read it, and a README is a bad
place to be angry.

So: this.

## What goes here

Mostly the things that annoy me enough to write them down.

- Software that was good and then had a funding round.
- Self-hosting problems that took me a weekend and should have taken an hour.
- Decisions I made in these projects that I would like to explain once,
  properly, instead of eleven times in issue threads.
- The occasional thing I got wrong, because that is more useful to you than the
  things I got right.

## What does not go here

No tutorials that exist already. No "10 tools you need in 2026". No engagement
bait, no newsletter, no popup asking whether I can interest you in my thoughts.
If a post is worth reading you will know within two paragraphs, and if it is
not, close the tab. I will never know and I would not mind.

## How it is written

I originally wrote this section saying it was Markdown files in the repo, no CMS, no database, nothing to log in to, and that a piece of software needing an account to publish a paragraph had already lost. That lasted about as long as you'd expect.

The problem was simple: inspiration doesn't wait for me to be at a laptop with the repo cloned, and editing a Markdown file through a git commit is exactly relaxed enough to kill an idea I had standing in a queue somewhere. So there's a CMS now, the same one that manages the projects and images on this site, and yes, it needs an account to publish a paragraph.

I'm not going to pretend that's not a reversal. It is one. The bar was never "no software," it was "nothing standing between having a thought and getting it down," and it turns out for me that bar is cleared by a login screen and a text box, not by a git workflow I'd resent using at 11pm.

That is the whole setup now. Still no newsletter, still no popup. Now let me go find something to be annoyed about.