2 ms·
I get it’s cool to be critical of FAANG and point out their obvious (from hindsight) mistakes but the fact is engineer teams are a finite resource and this bug
by hnlmorg 3y ago
I get it’s cool to be critical of FAANG and point out their obvious (from hindsight) mistakes but the fact is engineer teams are a finite resource and this bug is an edge case from a misbehaving service on a trusted network (UPnP wouldn’t work like this on a “public network”, by Windows definition).
We’ve all, yourself included, made plenty worse fuck ups in our career. So let’s show a modicum of pragmatism here please.
What we should be more critical of is how this gets reported and handled by Microsoft and Hisense. Do they choose to ignore this bug / close it as “Won’t fix” (working as intended)? Or is this something that will be patched in a relatively recent software update?