Having human problems that create human pain are what motivates human solutions that humans value. An AI with AI problems doesn't seem relevant. Lions and humans both have pain and suffering in their design. Intelligence is only one part of the complete package that must include empathy for the hosts of problems there are to solve using intelligence. "Solve all suffering = destroy all life" is pretty intelligent but not so empathetic.

A senior developer is a developer valued by her peers. Everyone who goes to her consistently receives quality help, advice, and guidance.

I'm not sure how this wont work itself out in the end. If someone is having trouble getting health insurance, doing their taxes, running their business, or paying their bills online, a lack of neutrality won't look so good even if it's not truly to blame. There is a complexity in managing favoritism and lists and lists of who's who. What happens when a critical internet benefit lands on the wrong list? What if you can't get on the list you want? What if a natural disaster occurs and a website pops up to help victims. Will it be nonfunctional, slow as Christmas, or streamlined onto the fast track? If you are visiting the site, how will you know if it's a badly designed site or a non-neutral site? Will it be fixable? Which ISP would you need to contact? All of them? It seems to me that any company offering Net Neutrality as a foundational feature would win out over those that don't in the long run. (Can't use the internet, find what you want, it costs too much, or it's taking to long = ISP's fault)

-Mikhael

I think there is a huge chasm between the Average Joe and a developer. If I had to guess, I would say that the average Joe doesn't want the filtering functionality. If they could get away with it, they would press a big button that says "Do what I Want" and they'd be done. My guess is that what Joe would want instead is a view of the data that was designed specifically for his primary use case scenario(s). In other words, avoid filters the best you can for the average Joe. Understaninding the content and how it is consumed and why is key here. Identify a default functionality that serves the purposes of the user 90+% of the time. Then Devote the whole screen to making that default scenario feel like a kindergartener could do it. Use the language that Joe is already used to hearing around the shop in your design. Then if a power user still needs filters, put that on a different "Advanced" screen. Maybe a power user could build and save other common scenarios for the Average Joe to consume. Getting Joe to learn to program queries via a user interface is not low hanging fruit even if you deliver a killer UX. Hope it's hepful, -Mikhael :)