Timeline for What does constructive criticism of a design change look like?
Current License: CC BY-SA 4.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 29, 2018 at 1:12 | comment | added | forest distrusts StackExchange | @NicolBolas That's true. I was talking more about SO users, not SE users in general. My point is that the overlap between those who have enough understanding to judge a regression and those who believe regressions imply stupidity is effectively zero. | |
Aug 19, 2018 at 13:28 | comment | added | Nicol Bolas | @forest: "Regressions are a part of a programmer's life." 1: Not every SE user is a programmer. 2: Not every SE user is a professional programmer. 3: Even among those who are, there would still be many who say that they should. | |
Aug 19, 2018 at 9:50 | comment | added | forest distrusts StackExchange | @NicolBolas No, they would not. Regressions are a part of a programmer's life. Any programmer who thinks that causing a regression makes someone stupid has never actually worked on a big project. But simply saying "we're removing this, deal with it"? That's just in poor taste. | |
Aug 14, 2018 at 17:55 | comment | added | Nicol Bolas | "Folks, we don't have yet a mechanism for custom arrows. So be prepared for some regression." If they had said that, people would be asking "why not" and saying "SO developers are stupid for not implementing it". Nothing would change. | |
Aug 13, 2018 at 21:11 | comment | added | fbueckert | Despite the abrasive tone, I'm having a hard time disagreeing with the reasoning. It very much does not feel like the community is being listened to, in any sense. | |
Aug 13, 2018 at 19:44 | history | edited | user399543 | CC BY-SA 4.0 |
added 515 characters in body
|
Aug 13, 2018 at 18:56 | history | answered | user399543 | CC BY-SA 4.0 |