---
title: "Hello, subarashi.dev — what this is and isn't"
canonical: "https://subarashi.dev/posts/2026-05-20-hello-subarashi"
pubDate: "2026-05-20T00:00:00.000Z"
author: Ahmed
description: "Why I'm starting a working notebook on AI, Revit, and BIM — and the rules I'm setting for AI-assisted writing before I forget them."
tags: [Workflow]
---

I've been keeping notes on AI tools, Revit quirks, and BIM workflows in scattered files for years. This is the place those notes come to live in public. Not a tutorial site, not a hot-take feed — a working desk where I can post a finding, a trap I fell into, or a code snippet that earned its keep.

## The rules I'm setting now, before I forget them

A few constraints, because every personal site I've abandoned died from a lack of them:

1. **One post can be a paragraph.** If I find something worth writing down, I write it down. Length is not the measure.
2. **Provenance is on the article.** When an AI assistant helps draft a post, the article header says so and the source file in Git records which tool. No laundering machine output as my own thinking.
3. **No post publishes without review.** Drafts land as pull requests; I merge after reading the diff. If I'm too tired to review, the post can wait.
4. **No trackers, no banners.** Cloudflare's privacy-respecting analytics is enough. The only third-party scripts are AdSense (because that's how the site pays for itself) and the AdSense consent prompt for EU visitors.
5. **The site stays small.** Static HTML, Markdown files, a CDN. If it ever needs a database, I've drifted.

## The stack, briefly

- **Astro** generating static HTML from MDX
- **Cloudflare Pages** serving from the edge, free
- **Cloudflare Registrar** for `subarashi.dev` at wholesale
- **GitHub** as the source of truth — AI assistants commit drafts here via PR
- **AdSense** for ad revenue, with Google's Funding Choices for consent

Total run cost: about \$10/year for the domain. Everything else is on free tiers that aren't going anywhere.

## What's next

A real first technical post is queued — something Revit-specific about shared parameter files, because that's been the topic eating my week. After that, whatever's on the desk.

— Ahmed