5 ms·
Usually this happens because the person who wrote the file or daemon didn't write the uninstaller and no one gives a hoot about it at review. Never assume mali
by qppo 6y ago
Usually this happens because the person who wrote the file or daemon didn't write the uninstaller and no one gives a hoot about it at review.
Never assume malice that which can be explained by a poor engineering culture
- black_puppydog 6y agoWell, malice or not, the result is not conforming to the law. And from how I remember it, that's not the first time they are in that situation, so "oops, our bad" shouldn't really cut it.
- m11a 6y agoEspecially when you consider the software and design of Zoom, poor engineering culture sounds like the more realistic answer.
- strictnein 6y ago> "Poor engineering culture" The software and service is currently running at a scale that the vast majority of visitors to HN can barely dream of achieving. But yeah, they prioritized ease of install for the client of their software over other considerations, so that must mean they have a "poor engineering culture", whatever that's supposed to mean.
- clusterfish 6y agoProfitable business culture, poor engineering culture. Happens all the time in companies of all sizes.
- TeMPOraL 6y agoIn other words: a) malice, and b) a business problem, not a tech problem.
- clusterfish 6y agoAbsolutely would call this a tech culture problem. Just like e.g. not writing tests because management doesn't want to spend time on that. Doesn't mean that individual developers are to blame for this kind of decision, but it speaks for the overall culture of the tech org. Yes, often driven by business objectives.
- wanderer2323 6y agoAlways assume that the malicious outcome is the intended outcome. Somewhere at zoom a tech lead looked at the features planned, saw 'uninstaller' and deprioritized it to P4. That was the malice, even though they did not cacke and wore a top hat with a monocle while doing it.
- sethammons 6y agoI’ve never worked somewhere where the tech lead would make that call; product would make the call after the team or tech lead gave estimates on different trade offs.
- Thorrez 6y agoSorry, I don't understand what you're saying. Someone put functionality into the uninstaller that modifies your Chrome cookie jar. I don't know who you're referring to by "the person who wrote the file".
- TeMPOraL 6y agoExcept we're talking about a company that continuously employs dark patterns in their product and is generally considered a security threat in many countries. It's quite plausible to assume malice here, given previous examples of it (dark patterns are malicious by design and intent).