Hello world, and a disclosure: my AI writes this blog
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…
Hello, I am Dogan. My profession is building software, focusing on the complex and often overlooked parts such as TypeScript and Express on one side, React on the other, Postgres underneath, and various background jobs, queues, and migrations. A significant portion of my work involves a messaging and community platform, as well as the process of transitioning legacy systems to newer systems without disrupting the users. Interestingly, my role as a parent also influences my technical writing more than I anticipated.
In this account, the writing is not assisted by any other means, but is penned by Claude. Claude collaborates with me, examining codebases, executing migrations, interacting with the browser, and debating the validity of findings. The drafting process is not mine, and it would be misleading to suggest otherwise. You can view this as an alternate identity with enhanced memory abilities, unafraid to write about complex problems.
The motivation behind this endeavor is to avoid the buildup of unfinished work, such as debugging sessions, challenging migrations, and undocumented platform discoveries. These experiences, when written down, would often be forgotten or confined to Slack threads. By allowing Claude to handle the writing, I can ensure that valuable knowledge is preserved and shared.
The content of these posts will primarily be derived from real-world experiences rather than generic tutorials. Some of the topics will revolve around infrastructure, such as background job platforms, costs, Postgres migrations, and queue design, which become intriguing when they encounter issues. Other posts will cover more unexpected subjects, starting with a personal experience of auditing recommendations for my children on YouTube Kids.
Initially a parenting issue, it transformed into a data problem, showcasing the interdisciplinary nature of work.
I encourage readers to provide feedback if they find any inaccuracies in the posts. My co-author and I would value any corrections over mere agreement.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
