A Whole New Beginning

Starting a new site is more than a formatting project. It is a chance to decide what kind of trail I want my work to leave behind.

This blog began as a cleaner home for older posts, technical notes, and ideas that were scattered across previous attempts at writing online. Some of those pieces were rough. Some were overexcited. Some needed better structure. But underneath the dust there was a useful pattern: I kept coming back to the same kinds of questions.

How do software systems become more reliable? How can AI help us reason through complex engineering problems without replacing the need for judgment? What can chemistry, biochemistry, physics, and data teach each other when they are treated as connected fields instead of separate boxes?

Those are the kinds of questions I want this site to make room for.

A better site is not just a new container. It is a chance to organize the thinking inside it.

Why Move The Blog Here

GitHub Pages is a good fit for the kind of writing I want to do because it keeps the site close to the same habits that make software maintainable: version control, plain text, small improvements, and a structure that can evolve without becoming mysterious.

That matters to me. A professional blog should not feel like a scrapbook with a nicer font. It should show how someone thinks, how they learns, what they pay attention to, and how their interests connect over time.

For me, those interests sit in a few overlapping areas:

• Software engineering, automation, and practical tooling.
• AI systems, evaluation, and applied machine learning.
• Chemistry, materials, catalysis, and clean energy.
• Biochemistry and physics as ways of understanding complex systems.
• Professional process: checklists, reliability, communication, and learning.

The goal is not to sound like an expert in every room. The goal is to build a thoughtful public record of curiosity and progress.

What I Want This Site To Become

I want the posts here to do more than summarize interesting topics. A good technical post should make a useful connection, explain the background clearly, and leave the reader with a practical takeaway.

That means I want the site to have a few standards:

• Clear titles and descriptions.
• Sources where the claims need them.
• Diagrams or images when they make the idea easier to understand.
• Enough technical detail to be useful without turning every post into a textbook.
• A tone that sounds like a working engineer thinking in public, not a press release.

Some posts will be exploratory. Some will be more polished. Some will be about science, some about code, and some about the habits that make both easier to do well.

The Value Of Keeping Older Work

Refreshing older posts is a little uncomfortable because it shows the distance between where I was and where I am now. That is also the point.

Old writing captures the path. It shows what caught my attention, what I was trying to understand, and what questions kept coming back. Cleaning it up does not erase that. It makes the useful parts easier to revisit.

That is how I want to treat this site: not as a perfect archive, but as a living portfolio.

Moving Forward

This is the starting point for a more deliberate writing practice. I want this blog to become a place where software, AI, engineering, chemistry, biochemistry, and physics can sit at the same table.

The best ideas often show up at the boundaries between fields. This site is where I plan to keep looking for them.