A place to think in public


Most software starts as a private question: Could this work? The interesting part comes next—the experiments, tradeoffs, wrong turns, and small decisions that turn an idea into something useful.

I am starting this blog to keep a public record of that work.

Why now

My career has been a search for opportunities to help people solve real-world problems with mathematics. I started by using partial differential equations to simulate biological processes in a sewage treatment plant, then moved into forecasting supply and demand for supermarkets and big online platforms(Alibaba). Over the past three years, I have focused on providing AI-powered marketing solutions to clients around the world—and we have achieved some exciting results.

With our help, customers have spent less on marketing campaigns while generating more sales and conversions. We have helped them find more relevant audiences and respond faster to changes in social media trends.

But I have also learned that running a business is far more complex than marketing alone. From my position as a service provider, I could see many more problems than I was able to fix. That led me to a new question: Why not step into the kinds of businesses my customers are building and learn to solve those problems from the inside?

That question feels especially timely because AI is changing what a single person can build. But the tools are only part of the story. The harder questions are still human ones: What is worth making? Which shortcuts are helpful, and which create hidden costs? Where should automation stop and judgment begin?

Those questions are easier to answer through practice than prediction. I want a place to document what I learn while building: not just polished outcomes, but the reasoning that shaped them.

What I will write about

You can expect a mix of:

  • first-hand lessons from learning to run a business;
  • field notes from building software with AI;
  • clear explanations of tools, workflows, and technical ideas;
  • product decisions, including what did not work and why; and
  • occasional reflections on learning, creativity, and making things on the internet.

Some posts will be practical. Others will be more exploratory. All of them will aim to be specific enough to be useful.

A working notebook

The web is full of confident conclusions. I am more interested in showing how conclusions change when they meet real constraints.

So this blog will be a working notebook rather than a highlight reel. I will update ideas when experience proves them incomplete, and I will favor honest details over tidy narratives. If a post helps someone make a better decision—or ask a sharper question—it has done its job.

Thanks for reading. If these themes overlap with what you are building, you can find me on X or explore my work on GitHub.

Join the discussion

Questions, corrections, and thoughtful disagreements are welcome.