4 ms·
It appears good on the surface but it's way out of touch with reality. It's actually insulting, too, as it shifts blame from those controlling the situation to
by nickpsecurity 12y ago
It appears good on the surface but it's way out of touch with reality. It's actually insulting, too, as it shifts blame from those controlling the situation to those executing their will within their constraints. Reality: There were attempts repeatedly to do what's truly good for customers from business models to language designs to superior hardware to privacy-preserving technologies. Those companies almost all went bankrupt, got acquired as profit declined, or cancelled those product lines with huge loss ($1+ billion for Intel's BiiN and i432 APX). The reason: the market almost always chooses against sacrificing features, time to market, or profit for quality and security. Making it more expensive, slower, less flexible, or less backward compatible for the users own good will get you shunned by consumers or fired by management. Lack of demand is so strong and pervasive, I left the high assurance industry except for private R&D and contracts. I just publish stuff online for free now to help the few that care.
On the other end, the users indeed don't understand the tech or trust boundaries. What the author missed is THEY... DO... NOT... TRY. Very important. We as a society treat certain things as responsible behavior, mandatory education, or mandatory evaluation. Understanding the tech's properties and risks? Not so much. Further, users as a whole are in favor of buggy systems/services that are cheap, free, or used by many friends. They're also happy to give away personal information and control for almost nothing in return (eg Farmville). And they outcast, demean, and underpay the people that build all this for them. Software engineer's habits and existing products/services are a result of their environment.
So, I've always seen the exact opposite: people as a whole and the marketplace need to act responsibly about technology. That will take a learning experience that combines (a) their efforts to learn along with weighing tradeoffs and (b) our best efforts to convert the technical things into layperson level. Metaphors will help as I illustrated [1] for Facebook's risk. Further, people need to understand that they get what they pay for, that their decisions create long-term effects on them, and that they might need to invest in ethical/private/quality alternatives to existing services. Fortunately, there's always a niche of those customers to serve for developers that care. Hard to get a job, though, since there's so few customers and so little money in it.
Doing the right thing professionally and in mainstream IT is an approach for those seeking to draw unemployment. Certainly little things you can do within constraints you are given. It's just that you're effectively working in a straight-jacket trying to help people ordering you to harm them. Most of the time, anyway.
[1] https://www.schneier.com/blog/archives/2014/04/ephemeral_apps.html#c5259463 https://www.schneier.com/blog/archives/2014/04/ephemeral_app...