RU version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
23% Positive
Analyzed from 497 words in the discussion.
Trending Topics
#don#test#companies#testing#everything#broken#https#com#user#issues
Discussion (16 Comments)Read Original on HackerNews
Aren't they hiring supposedly top-tier talent and paying them top-dollar?
Surely they have a test suite and surely this would fail in that test suite.
I really don't understand how they end up doing such things.
A week ago Facebook's language translation broke. Results come back in the original language or a mix. How could no-one notice?
"Everything is broken" used to mean "all software is insecure because the inherent complexity of a modern software stack ensures it's beyond the abilities of the average developer to eliminate all attack vectors" [1].
Now it just means [2].
1: https://medium.com/message/everything-is-broken-81e5f33a24e1
2: https://www.youtube.com/watch?v=pndhO5DcSI0
I think they all got rid of QA, and developers don't have enough time to actually care about what they're building/fixing.
GitHub/Microsoft is incredible at this. The feature for selecting and closing multiple PRs was broken for weeks even after I and others reported it. I saw duplicate "A user you've blocked has contributed to this repository" warnings (two of them, one above the other) for weeks too before that was fixed.
I've stopped reporting issues as well, as it seems to have no effect on how quick it takes, so I don't think it's an issue of not being aware of them.
This is particularly annoying to me as I address everything in my repos quickly, but then the badge remains there making me think something new was opened, and then I keep clicking to find nothing. Or in one case I ignored something which was there because I thought it was bugging out as usual.
I don't know if I just got seriously grumpy over time/with experience, but everything user-facing just seems so crap nowadays, unless it's made by a smaller company who actually seem to care even a tiny bit.
I don't have any insider information here, but it's likely that the creator of this menu is long gone (it looks old!) and this feature is in maintenance mode. Someone--or a bot--just trying to keep the build green may have disabled the test without understanding that it was pointing to a real issue.
> Google typically has very, very thorough tests.
Yeah, sure sounds like they have figured out this whole testing thing perfectly well, if that's the case :)