Hey, I'm Rin.
I build full-stack web apps — mostly around maps and real-time data, the kind where there's too much on screen and it still has to feel instant. The frontend is where I'm strongest, but I tend to follow a problem wherever it leads, which is how I've ended up writing Rust solvers and Go backends too. What I actually like is the puzzle: working out why something's slow or tangled, and quietly making it not be.
Types should pull their weight
If a function's signature can lie to me, it will, and usually at 2am. So I try to make the types carry as much of the truth as they'll hold.
The bug's never where you think
I start on the frontend, but the actual problem is almost always a couple of layers down. I'd rather just go find it than sit there guessing.
Make the slow parts fast
The code I'm proudest of is usually some unglamorous tool nobody notices, that quietly turned a 30-second wait into basically nothing.