I use AI to help me write. I also use it to help me code. I wrote about that last week. This post is the other side. The part I do not say as much about. The LLM often sounds confident. Whether the answer is right, half right, or completely made up, it usually comes out the same. Same tone, same formatting, same "here you go" energy. That is the trap. Not that the LLM is bad. The trap is that it does not know when it does not know, and neither do you, until something breaks. Two kinds of "I do not know" There is a difference between these two situations: I know the topic. I use the LLM to draft, to format, to skip the typing. I am the source of truth. The LLM is a faster pen. I do not know the topic. I use the LLM to learn, to summarise, to answer. The LLM is my only source of truth. The first case is what I wrote about in the "I use AI to write" post. The risk is small there. If the draft is wrong, I can tell, because I already know the answer. The...
I use AI to write my blog posts. Most people probably assume that already, but I want to say it clearly anyway. The ideas and experience come from me. I think about what I want to say, then I get the AI to draft it. After that I read it and fix the parts that do not sound like me. It is a tool. I still decide what goes on the blog. I still review everything before it goes out. The AI just helps me write faster. I think this is fine. I do not want to pretend I am doing something I am not. So here it is: I use AI to write my blog posts.
I just finished a redesign of this site, so it feels like a good time to write down how I actually keep it running. The short version: I do not open a code editor very often. I talk to an AI in a Telegram chat, and it edits the files, runs the build, and tells me what to commit. This post is for anyone who has been curious about agentic AI but has not set one up yet. I am not going to cover the theory. I will show what my day to day looks like, what works, and what I would skip. Where this started I did not start with the blog. I started with small offline web apps for myself. A calculator for splitting rent. A page to track my car maintenance. Little things that took me an hour each and saved me from opening a spreadsheet. The point was to ship something useful, fast. After a while I started using the same setup to publish things I cared about. Notes from a course I was doing. Opinions I wanted to write down. That is when I dusted off this old blog. The redesign I just posted about...
I gave this site a visual refresh. These are the main changes. The background I drew a grass field in SVG and set it as the background wallpaper. It sits behind everything, fixed in place, with a gentle sway. In dark mode it dims so the text stays readable. I want the site to feel calm, like writing outdoors. The design I stopped using Simple.css and wrote my own stylesheet from scratch. The layout is simple: a centered column for reading, a clean header, and not much else. Every color and spacing value comes from a small set of variables at the top of the file, so changing the whole look is just a few lines. The site now uses Inter, a typeface designed for screens and long reading. It also has dark mode that follows your device setting automatically. Other small changes Tags are now small pill shapes instead of rectangles Post summaries on the homepage are longer and do not cut off mid-sentence Code blocks look nicer with a card-style background I added Prettier so the code stays formatted What did not change Eleventy still builds the site. GoatCounter still tracks visits without cookies. The RSS feed is...
First blog post. Hello World!
← All tags
