Not really a utility, but it meant that someone at the parks and rec department with virtually zero computer skills could let everyone know when things were closed due to rain and when they were open again.
Every so often Google docs prompts me to install their plugin. At this point I don't even remember what issue it caused, I just remember that it was so infuriating and that I decided I never wanted to deal with it again.
Communicate about it. Whether it's writing internal documentation, user documentation, discussing things with another developer, or just talking to a rubber duck, just forcing the concepts into sentences can really help you think about them. Several times I've been like "this code seems ok" but then when I had to think through it and explain what it does I thought "no, that's too embarrassing, I need to improve that."
A couple random thoughts:
You've freelanced before, you're not happy with your current job, so consider getting back into that, at least on the side.
3 seniors quitting in a year does sound a bit like a red flag. Hopefully you're keeping in contact with them? Maybe you can find out why they left and where they went (and whether you can come along).
It's often unnecessarily large and undocumented. Sorry.
Consider running your ideas by some higher-ups before you spend your weekends on them. If they're not interested, maybe they could help you figure out things to work on that would get traction. This might be one of those trite old things where you make the person belivee it's their own good idea, but even then they'll at least know you were the one to implement it.
Things like code quality guidelines and interview processes involve some subjectivity- they're commendable things to want to improve but it may not be as simple as "boom, now it's better."
Not everyone loves talking about software for the sake of software. Maybe connect over biking or frisbee or movies or something. Also, "software" is a vast, vast space of topics. If someone doesn't happen to be in the right frame of mind when you bring up some otherwise-interesting topic, you probably will get blank stares. If you do want to chat about software, find a way to ask people about something you know they're working on.
I do hate the getting-things-done-in-meetings approach. You could try short-circuiting them with emails like "Here's problem X, here's my solution Y, please email me thoughts otherwise I'll go ahead and implemnt it." (YMMV)
In the end, though, it does sound like you're looking to leave. So, keep a list of your accomplishments (even if nobody there appreciates them), the responsibilites you have, positive feedback you've gotten, and things you've learned. Brush up your resume and look around. If you're financially stable, maybe just bail and go back to freelancing. Or, if you're feeling gutsy, maybe apply for a Sr role at your current place- that might be a way to gain some recognition.
