...is that the system can't hear you. Only people can.
And the problem is that people in the system are too often swayed to believe that they have no power over the system, that they are merely victims of it, pawns, cogs in a machine bigger than themselves.
So, when the system can't hear you, and those who can believe they have no power, nothing improves.
Systems don't mistreat us, misrepresent us, waste our resources, manage poorly, support an unfair status quo and generally screw things up -people do.
If we care enough, we can make it change.
Everyone says we should teach kids to code, what if instead we made it so that the machines they're using didn't need so much coding? Amazon really has something good with AWS, the way we should all be doing computing in the future, but now it requires people to know too much to get the simple result most people will want.
I'm a longtime user/customer of Amazon Web Services, going all the way back to the 2006 when they rolled out S3, their basic storage system.
My websites are S3 buckets. I have an 3 EC2 instances that run my apps and Insight. I use Route 53 to manage domains.
I probably would use more of their services, but they're so damned hard to get started with. Which is a shame because once you've climbed the hill, they're not that hard to use.
Typically I have to approach a product several times, often over a period of months, before the clutter gets out of the way, and the steps-to-start reveal themselves. When I look at the docs, I can tell right off that I now have to learn a lot of extra concepts before I get to Hello World. Usually it takes a few approaches over months before I break through and discover how to use one of these toolkits. There are so many concepts they use that I don't understand, that's why I have to approach and re-approach. Most of their competitors are no better, by thhe way.
They really ought to fix this.
