this post was submitted on 01 Nov 2024
175 points (96.8% liked)
Open Source
31217 readers
238 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Constructive criticism is different than talking shit. Still a useless debate
Nice strawman btw
talking shit is a completely different thing. and where's the strawman? it feels like you don't know what words mean.
"And no you're not a shit person for critizing any work" is the strawman
it's not though
It is since I criticized only non-constructive criticizing and not critizing in general
I disagree. "It's ugly" is valid criticism. It has the same value as "needs better/more appealing graphics". You're just annoyed it wasn't sugar coded. In fact I'd argue the former is more valuable than the latter because it doesn't beat around the bush and more importantly it points to a problem rather than the solution.
As a designer I find that most often customers don't hit the mark by trying to design the thing themselves, telling me exactly what they want, essentially trying to do my job for me. Hearing the customer's problems with it to figure out a solution on my own as a designer is better a vast majority of the time.
"I don't like it" is bad. "I think it looks awful" is better. "I hate the colors" is best. I don't really care about wording, I care about the information I get.