@chergert Rather, if they're strings they should be strings with as much context as possible, e.g. 2026-03-16 vs. "Mar 16"
Dates should always be represented with as much context as possible in transit & storage. Don't give me a date like "Mar 16" please
Being told my code is clean and well organized 💕
Rust compiler: Hey, this is a little off, but we can get it going if just give it a little nudge.
Clippy linting: Bro, what the FUCK is this?! Are you being serious right now? CLEAN THIS UP! NOW! This is some BULLSHIT!
@are0h I love it when clippy tells me to get my shit together. It's rarely wrong.
I said that I like 100% code coverage, but I also feel like you really shouldn't block anything on 100% code coverage. You end up with some very silly tests when you're trying to split the difference between 99.94% code coverage and 100% code coverage.
It's always funny to be reading through github issues and then spot a mutual from here doing something really complex and cool
Every time I'm in a programming mood and start feeling the itch to learn more and explore new things, I look at Go and find myself baffled. Not just by the language itself, but how adamantly the community defends poor choices. People will look you dead in the eye and say that there's no good justification for having enums
Having an in-depth code review requirement and having strict timelines for development leads to pain :(
I saw someone say runtime validation of types (from external sources) in JS is useless, but I'm kind of baffled by that opinion. How can you even trust your types if you don't check? That's how you end up with broken pages when something changes
Bully of Bullies, Inc