127 karma · joined February 6, 2019
7. Problem solving: figuring out how to fulfill goals and objectives
Design is fundamentally about solving problems. It's something that gets overlooked and/or misunderstood by so many web designers today.
Design is not about what one likes. It is about what helps one solve a problem.
Web designers and their bosses/clients reduce "design" to the creation of the look-and-feel of websites. For them, design is all about how something looks. This is something which is highly subjective.
The flaw in this is that it's not how users think. Users have a job-to-be-done. A good design is one that helps them accomplish that job. A better design is one that helps them accomplish that job better, faster, or easier. A bad design is one which doesn't help them or makes it worse.
Consider a monolingual English speaker using an ATM in China. You will never hear them say, "Well, I can't get my money because I don't understand Chinese. However, this ATM looks so nice I'm going to try to use it again."
It doesn't matter how great that ATM looks if the user cannot accomplish their task.
Yes, aesthetics have a place, but it's a very diminished place of importance. Aesthetics is much less important than most web designers and bosses/clients think.
It's time they get over themselves and start thinking about users.
The problem is designers and their bosses/clients. They equate design with looks. As a result, they see design as solving the problem of aesthetic. They fail to realize this is a problem which very few people care about on the web. So long as it passes the smell test of credibility, no one cares. (Excluding a handful of cases.)
As a result, we, the users, must suffer.
Nice? That's not the word I would choose. Random stains on the furniture and carpet. Hairs on the sheets. A vending machine at the end of the hall selling an assortment of toys.
They did have free pirated DVDs on a shelf at the end of the hall. It was all porn.
It did have fantastic sound effects at 2 AM in the morning, though.
Nice is definitely not the word I would choose based on my experience.
What we have is a group of people (e.g., Lerna, etc.) trying to ride on the coattails of success of "open source" without being forthcoming about what they're doing.
We could be charitable and assume they're doing so out of ignorance, but I've seen way too many discussions on this issue where it's pointed out. I simply don't think they're ignorant. I've think they're being actively dishonest.
I wish that people would understand this not only in the context of definitions but also in the context of culture. Neither definitions nor culture belong to anyone. At the same time, they "belong" to everyone.
The existing community in which open source is used largely understands "open" to refer to freedom in the broadest means possible. That's the word's denotative sense. It also carries a strong connotative sense in which it is viewed as a positive for business and society.
What's happening is that you have a small group of people who desire to benefit from the connotative sense of the word while changing denotative sense. That creates problems when they're not clear that they don't mean open source in the same way that it's understand commonly amongst the technical community.
It's underhanded and dishonest.
If they want to create a quasi-open source license, that's fine. They simply should be very clear that it's not open source in the traditional/common sense.