Resume VS Tachi

I found this extremely bizarre, as I don't really think my resume could in any way be interpreted as a PM's resume, and assuming I wasn't lying I feel that it's pretty obvious I am a "hands on coder".

I think what happened is that the hiring manager already knew who they wanted for the job, but for legal and/or bureaucratic reasons they had to have a pretense of "trying to find the best candidate". I suspect that they never even looked at my resume, had some basic boilerplate rejection text that had some vague plausibility, and was just going to reject every candidate sent to them.

That's fine, but I really wish they had done this before I had to spend multiple hours trying to get a read on my personality. I think a lot of hiring managers are sociopaths.

[1] https://gitlab.com/tombert/Resume/-/blob/master/resume.pdf?r...

Résumé/CV: https://gitlab.com/tombert/Resume/-/blob/master/resume.pdf

I've spent the past two years or so working on Tachi (https://bokutachi.xyz/) (https://github.com/TNG-Dev/Tachi), which is a modular tool for tracking rhythm game scores.

Generally, everyone was using their own personal spreadsheets or ancient "just render everything" tables to analyse their scores and progress before this and I'm pretty happy with how it's turned out.

What I'm probably most proud of is that adding support for a new game is adding a new module for it - all of the other features automatically work with it. This turns a "each game needs to have its own full-site tracker" into a "each game needs a configuration for this one tracker", not unlike how LSP simplifies adding language support for editors!

Taught me almost everything I know about scaling a codebase, and despite being a niche tool it's picked up a lot of momentum (2k users, ~3m scores).