Timeline for What is the meaning of "A is the good, B is the bad and C is the ugly"?
Current License: CC BY-SA 4.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 8, 2019 at 5:19 | review | Suggested edits | |||
Nov 8, 2019 at 23:03 | |||||
Oct 10, 2019 at 11:46 | history | edited | J.R.♦ | CC BY-SA 4.0 |
The comments are gone, so...
|
Oct 10, 2019 at 10:48 | comment | added | Edwin Buck | One of my favorite westerns. Yes, it's fully relevant. And I'm guilty of producing good, bad, and ugly code, as the need requires. | |
S Jul 9, 2018 at 9:48 | history | suggested | thorn | CC BY-SA 4.0 |
Clinton Eastwood
|
Jul 8, 2018 at 18:10 | review | Suggested edits | |||
S Jul 9, 2018 at 9:48 | |||||
Apr 12, 2018 at 23:29 | comment | added | PerryW | I wouldn't necessarily say arbitrary - that suggests randomness or personal whim, but I would say that the sorting is subjective. The whole piece is subjective; the writer is giving his take on the experience of using the Go programming language: what's good, what's bad and what's ugly. Another writer would probably allocate the issues differently. As an example, the writer classed the Go variable definition method as bad. I'd have put it in ugly, but there are others that really like it and would have added it to good... | |
Apr 11, 2018 at 22:13 | comment | added | Vi. | How would you interpret usage of this pattern in this article? Is division into the two latter groups just arbitrary? | |
Aug 18, 2014 at 4:31 | history | edited | PerryW | CC BY-SA 3.0 |
Missing words corrected
|
Aug 18, 2014 at 4:02 | history | answered | PerryW | CC BY-SA 3.0 |