I teach engineering and science, build software and games, and write science fiction. Those interests can look disconnected when reduced to job titles. In practice, they are tied together by the same question: how do we take a difficult idea and turn it into something understandable, useful, or compelling?
This site is where I intend to document that process. I think of it less as a traditional blog and more as a public lab notebook—a dated record of what I am trying, why I am trying it, what worked, what failed, and what changed my mind.
What belongs here
The subjects will vary because the work varies. Entries may include:
- build logs from software, games, electronics, robotics, and fabrication projects;
- clear explanations of scientific or engineering ideas I am learning or teaching;
- notes on writing hard science fiction without losing the human story;
- experiments with AI as a tool for learning and creating;
- observations from travel and the practical work of building a more international life.
Why make the process public?
Finished work hides most of the useful decisions. It rarely shows the abandoned approach, the mistaken assumption, or the small adjustment that finally made the project work. Those intermediate steps are often the part another person can learn from.
I help curious builders turn AI and STEM concepts into practical projects and stories.
That sentence is the closest thing this site has to a mission statement. It is broad enough to include engineering, software, teaching, fiction, and travel, but specific enough to provide a consistent point of view: understand the system, test the idea, and explain what was learned.
A record of movement
I do not expect every entry to be polished or definitive. Some will be tutorials. Some will be project notes. Others will simply document a question that I have not answered yet. Over time, the collection should become a visible record of work, curiosity, and deliberate change.
That is what this site is for.