Behind the work

I started with code. Over time, I became just as interested in the whole product: whether it makes sense, helps someone, and stays understandable for the next person who works on it.

That changed how I think about quality. A feature that works is only part of the job. I want it to feel simple to the person using it, and I want the code to make sense to the teammate who picks it up next.

Software is one way I try out ideas. DIY and 3D printing are another: model something, make it, and see what works. The Motorized Cyclo took almost a month of that.

I enjoy those rounds of testing: seeing an idea become real, finding what doesn’t work yet, and understanding it a bit better each time.

I’m working toward building my own startup. For me that means moving past my own implementation work and taking more responsibility for the product and the people building it.

I still want to stay close to the work: asking questions, trying unfamiliar things, and making choices with the next person in mind.