Hi, I'm Vitalii, and this is my blog.
I wanted a place to write about AI and developer tools: what I try and what actually works. I also wanted a home on the internet that is mine, not a profile on someone else's platform.
Testing AI tools is part of my job anyway, so I gave myself a small challenge: don't build the blog myself. Hand it to an AI coding agent and see how far it gets. I used Droid from Factory, right in my terminal.
From empty folder to live site
It took a few sessions. I described what I wanted, the agent did the work, and I mostly answered its questions and said yes or no.
What's under the hood, in one breath:
- Sanity for content. I write in its editor, and there's no database for me to look after.
- Astro for the site itself.
- Railway for hosting. Every push to GitHub deploys automatically.
- Cloudflare for the domain.
The design is based on Parley, a free Astro template I liked. The agent kept just the blog parts and adapted them.
The part I liked most
The boring infrastructure. Pointing a domain at a server, DNS records, HTTPS, deploys. The agent handled all of it from the command line. It created the DNS records in Cloudflare, connected the domain in Railway and checked that the certificate was issued. I didn't open a single dashboard for any of it.
Where it still needed me
Accounts and logins. An agent can't sign up for things or click "Allow" on my behalf. At one point connecting the GitHub repo kept failing with a cryptic "User does not have access to the repo". The agent tracked it down: my Railway account was only linked to Google, not GitHub. But I was the one who had to go and link them.
And taste. The first version of this very post read like a server log. I told the agent so, quite directly, and here we are.
How this post got here
The last step was connecting Sanity's MCP server, which lets the agent read and write content in my CMS. That is how this post was made: I shared what I wanted to say, the agent drafted it, and I reviewed it before it went live.
What's next
Posts about AI and developer tools: the ones I actually use, how I use them, and where they fall short. If that sounds useful, follow along via RSS.