3
votes
What programming/technical projects have you been working on?
This is a recurring post to discuss programming or other technical projects that we've been working on. Tell us about one of your recent projects, either at work or personal projects. What's interesting about it? Are you having trouble with anything?
Kinda stupid, but I once built some 3rd-party tooling for some of Gaia Online's flash games, and any time I have any new technology I wanna play around with or new concept I wanna put into practice, it's always by building / modifying that tooling.
So...currently trying to think about an API design for my system and it's fascinating thinking through how seemingly small choices can make a big difference in how things are structured. Answering questions like "how does this feel to use" vs "how does this feel to maintain"
I've been working on my maptile gateway service pretty heavily lately. Hard to believe it's over 2 years old now. And I'm pretty sure nobody is actually using it for anything -- I'm bad at marketing. But I've engineered the shit out of it a this point. I've had to make a few breaking changes recently, so it's a good thing I still have that flexibility.
Recently been going through some iterations of using Claude to help me find bugs, especially edge cases that could lead to panics or failed reloads. It's quite good at finding cases I never would have found myself.
I am hitting the point where I'm running lower on features that feel good to add. I don't want to turn it into yet another tile server, the niche of a tile gateway feels more interesting to me. On the other side, one feature I could add would be some form of rate limiting or abuse blocking, but that feels like an a hard problem that's better solved with one of the well established tools... and I quickly get into some philosophical arguments about hypothetical users. There's of course integrations I could add, to platforms I've never used nor especially have interest in learning (such as Azure or GCP secrets managers), but those would mean extra dependencies and difficulties testing.
Once I run out of bugs to find, I probably should call it a 1.0 and figure out how to advertise it - or, I guess, be satisfied with it not getting used.