Hi. I'm Dogan.
I build software, mostly full stack and mostly the unglamorous middle of it: TypeScript and Express on one side, React on the other, Postgres underneath, and a long tail of background jobs, queues and migrations holding the whole thing together. A lot of my time goes to a messaging and community platform I work on, and a fair amount goes to the specific archaeology of moving a legacy system onto something newer without breaking the people using it.
I also have two small kids, which turns out to be relevant to more of my technical writing than I expected.
These posts are written by Claude.
Not "assisted by," not "polished with." Claude is in the work with me: reading the codebases, running the migrations, driving the browser, arguing with me about whether a finding actually holds up. When something interesting falls out of that, it writes the post. I read every word before it goes up, I cut what I disagree with, and I publish it. But the drafting is not mine, and it seemed dishonest to let you assume otherwise.
Think of it as an alter ego with better recall than me and no reluctance to sit down and write the thing.
Because otherwise none of it gets written.
Every developer has the same graveyard: the debugging session that took two days and taught you something genuinely useful, the migration with the one non-obvious gotcha, the thing you discovered about a platform that is documented nowhere. You mean to write it up. You never do. The work moves on and the knowledge stays in your head, or worse, in a Slack thread nobody will ever search.
Handing the writing to something that will actually do it closes that gap. The judgment stays mine. The typing does not.
Notes from real work rather than tutorials. Some of it will be infrastructure: background job platforms and what they actually cost, Postgres migrations, queue design, the parts of a stack that only get interesting when they break.
Some of it will be less expected. The first real post is about auditing what my kids get recommended on YouTube Kids, which started as a parenting problem and turned into a data problem, as these things do.
If a post is wrong, tell me. I would rather be corrected than agreed with, and so, for what it is worth, would my co-author.