It's so annoying to see developers calling failing tests "flaky".
Last week I found a factory that assigned a random age to a user instance, so no wonder a test that used the age in some bit of logic failed sometimes. That's not a "flaky test", that's a bug in the factory.
Today I saw a date parser bug be called a "flaky test". It was written on the 21st of April and worked fine until it began to fail today, the 1st of May.
On iOS 17, how do I load an existing ringtone onto the phone? The online directions I’ve found use iTunes, which is not on current macOS, or recording a sound on the phone. I already have the sound on my computer. I can load the ringtone as a file, but it doesn’t show for phone or text tones. #lazyweb#apple
@khalidabuhakmeh How about: I can't loan my one car to two friends at the same time unless one of them is only going to look at it while the other friend actually gets to drive it.
It's cool that #Elixir's documentation now ships with a dedicated section on anti-patterns to avoid (including suggestions on how to refactor them), but I find it kinda disappointing that the very first one they're listing is the favorite fallacy of gatekeepers and other bad engineers everywhere, "you should not write comments, but code that is so self-explanatory that it doesn't need them". Ugh.
@hq1 I wouldn't worry too much about why I didn't write some code some other way. I certainly wouldn't spend time documenting things I didn't do. I would write a failing test, then I'd write the implementation that gets the failing test passing, done.
@hq1 For me "I need to comment about all the ways I didn't write this implementation" is not a valid argument for making the code all messy with comments that will eventually expire and become useless. Fortunately, we don't work together 😎
Another day, another native #Ruby gem that won't compile. I understand that there are some cases where you need to deal with external stuff via C, BUT so often native gems seem to be created because their devs felt that doing it in pure ruby provide performance that was too slow.
Ruby isn't a "high performance" language. If you want fast use C(++) or Rust or Go or any of the many "fast" options. Alternately, use your C skills to improve Ruby.
@soulcutter@masukomi Well, then how about fuck docker and all the kids who can't be bothered to learn how to configure their machines because they're too busy begging for money for writing a 3-line npm package? I mean, because that's what I wrote before I decided to tone it down a bit.