2 ms·
> A large part of the problem stems from a tendency on the part of technology designers to assume that properties of time and place don’t matter, I've seen a f
by neilv 4y ago
> A large part of the problem stems from a tendency on the part of technology designers to assume that properties of time and place don’t matter,
I've seen a few family farmers, for example, and they seem very well aware of the importance of equipment that they can maintain themselves, and they also DIY a large number of pragmatic necessities.
But look around at our own field's technology design right now, and it's often:
* By people who don't understand the application domain, and apparently don't care to understand it.
* By people focused -- not on the interests of the users -- but on the interests of some other party. (For example, any time you see what we currently recognize as UX dark patterns, and then the other engineering effort against users' interests, for which we might not yet have terms.)
* By people who'll make technology choices for individual gain, not even gain of their company. (For example, to add a marketable new stack keyword to resume, even when it's clearly inappropriate for theis project and the company right now. Or to do an unwarranted new project, so that it can be credited to them.)
* By people strutting around and posturing about their skills/impact/status. (Contrast with your stereotypical small family farmer, where boastfulness is frowned upon.)
Maybe it'd help us to think of those stereotypical farmers, to remind ourselves of humility and user-driven design.