Because you said that was not the point of the article and I asked you to clarify why you think it wasn’t. But never mind. This is going nowhere.
Because you said that was not the point of the article and I asked you to clarify why you think it wasn’t. But never mind. This is going nowhere.
Why not? If the starting point of the article is that we can’t design interfaces based on our elitist 5 percenter knowledge then the remedy for that would be…?
I’m using a lepotato for Home Assistant. Works very well for months now, but I’m a bit worried about long term distro support
I wonder why user tests aren’t even mentioned once in the article. If you design an interface you have to test it with your audience
That looks like advice on how NOT to ask for technical support on a public forum.
I was wondering if that might be a thing. Saw people talk about “the codes” instead of “code” more than once.
I don’t like this story. The outcome is only accidentally good and what the author seems to miss entirely is the elephant in the room: A crass failure to communicate with the developers. If you try to establish something like KPIs (not commenting on if that is good or bad here) you need to talk to the team and get them on board. If you treat them like lab rats and try to measure individual performance from the outside that is an obvious fail. In the end, where they state that they “quietly” dropped it, indicates that the real lesson was not learned.
Uh, and a dilbert comic.
Just call it Ecmascript and be done with it. The name JavaScript was misleading from the beginning. Well, Ecma sounds like a skin disease but who cares.