I have always been drawn to connections that did not seem to belong to the same category at first: computer science and psychology, research and making, code and music, structure and the sudden eureka of noticing that two ideas have been talking to each other all along. I could often see the route from one to another, and then lose weeks trying to find a form sturdy enough to carry all of it.
That is the practical reason for Hearth & Code. I want to do research carefully, with sources that can be checked and conclusions that can be challenged, and I also want the work to feel alive enough that the next surprising connection, rabbit hole, or small build can pull me back to the desk with genuine curiosity.