A computer old enough to invite curiosity
Born in the latter part of the 1990s, I grew up as computers were becoming a ubiquitous part of ordinary life. My first desktop was an Intel Pentium III system. It was not just something I used; it became something I could nurture, upgrade, troubleshoot, and gradually understand.
I extended that computer for as long as I could. Each change made the relationship between hardware, software, and performance a little more concrete. Eventually its lifespan could no longer be extended, but by then the important lesson had already arrived: technology was not a sealed object. It had parts, causes, limits, and clues.
Failure became the subject
That curiosity became a seventh-grade science-fair investigation into floppy-disk failure. I wanted to know what caused disks to stop working and whether failure could be studied rather than simply accepted.
The project earned third place. More important than the placement was the habit it established: begin with a system that behaves unexpectedly, isolate what can be observed, and turn uncertainty into a question that can be investigated.
Inspect the failure. Understand the system. Learn by trying to repair it.
From using technology to understanding it
The early interest was not only in what electronics could do. I wanted to understand how they worked and what made a broken system repairable. That moved the story toward circuits, semiconductor devices, signals, logic, and eventually software.
The tools changed from desktop hardware and magnetic media to production equipment, live data feeds, embedded sensors, local models, clinical workflows, and simulations. The underlying impulse did not: find the state that matters, understand the failure, and build something that helps the next person see it more clearly.