Hackathons have a throwaway-project culture. When my strain analysis (research) tool won 3rd place at Make OHI/O, I decided to break that pattern.

During the actual 24-hour competition, I pushed beyond the usual expectation. I built a working app with full test coverage and deployed it live. But after everyone packed up and went home? That's when the real work began.

I challenged myself to transform this quick hack into production-grade software. I built CI/CD pipelines that automatically test and deploy. I published Docker images that run on both AMD64 (Intel) and ARM64 (Apple M1/M2) architectures. I wrote the kind of documentation I always wish existed when I explore new projects.

What emerged isn't just a tool for analyzing material deformation - it's my personal blueprint for sustainable software development. Every automation pipeline, every README, every test represents a best practice I've learned and implemented over the years.

The repo stands as proof that hackathon projects don't need to die after demo day. I'd love your thoughts on what I've built and what I could improve next.