Starting This Blog

I’ve started a blog.

I usually maintain business systems and develop small internal tools. Rather than building new services from scratch, I spend more time keeping existing systems running, lightening manual operations a bit, and investigating the root cause when inquiries come in by looking at logs and data.

My work centers on unglamorous things like sales management, inventory, billing, customer support, csv integrations, night batches, admin panels, and notification bots. I’m more interested in who looks at things when they break, whether it’s safe to rerun, and where procedures diverge from actual operations than in flashy technology choices.

I don’t plan to write only polished success stories here. Instead, I want to document what got me stuck, what in hindsight lacked design, exception handling that never made it into the manual, and the subtle discomfort that surfaced after introducing a small automation.

For example, I plan to write about things like:

what to look at when a night batch fails
how to handle the exceptions that happen every csv import
how to investigate false positives from notification bots
how much logging is enough for a small admin panel
why procedures drift away from actual operations

Lately I’ve been gradually exploring ai and llms. But rather than jumping into grand narratives, I plan to approach them as an extension of everyday operations and automation. I’m less interested in what ai can do and more in who maintains it after it’s introduced, and how far back we can roll when something goes wrong.

Rather than formal articles, these will probably be closer to personal technical notes for a while. I want this to be a place where, reading back later, I can understand what was troubling me at the time, what decisions I made, and where I cut corners.

Thank you for reading.