3 ms·

I always find the position of telling people to never point out problems, only suggestions or solutions odd. From something as basic as a management philosoph

I always find the position of telling people to never point out problems, only suggestions or solutions odd. From something as basic as a management philosophy of "don't come to me with problems, come to me with solutions" to this "Don't suggest terms not to use, suggest terms to use" A person can identify a problem without having a solution, or identify something is wrong without knowing the full solution. So in this context a person can believe people using "DevOps" or "Agile" or "Tech Debt" in various ways to be a problem without having to suggest a solution to the problem If we just ignore problems we have no personal knowledge of the solution then I think that would end in every bad results over all, take for example a basic concept I think everyone would understand, my car is making an odd noise, I know that is a problem, but I have no idea what the solution is. I don't think anyone would say you should just ignore it, or have to present the auto mechanic with a fully fleshed out solution to the problem before taking it in for service.

jayd16 4y ago
It's not that you can't do it, its just low effort noise without a solution. Often times the downsides are apparent and the complaints don't add much without some discussion of alternatives.
- hombre_fatal 4y ago
  we regularly confuse the ability to enumerate the downsides of something as some sort of notable epiphany.
rendall 4y ago
> I always find the position of telling people to never point out problems, only suggestions or solutions odd. The article went lower than pointing out problems. It veered into toxicity, its claim to "irreverence" notwithstanding. From the first: > Object-Oriented Programming: Luckily the industry doesn’t really use this term any more so we can ignore the changed meaning. The small club of people who still care can use it correctly, everybody else can carry on not using it. Just be aware when diving through the history books that it might mean “extreme late binding of all things” or it might mean “modules, but using the word class” depending on the age of the text. The reference to the "small club of people who still care can use it correctly" is elitist, and he does not bother to define the term (other than in a meaningless call-out to his fellow club members). The casual readers who are not members of his self-described club are not left with helpful information to decide for themselves when and and what use of the term may or may not be wrong. It's just "If you know, then you know" phrasing. The tone does not improve through the rest of the article. I'm not sure this fellow should be teaching beginners how to program.

jayd16 4y ago

It's not that you can't do it, its just low effort noise without a solution. Often times the downsides are apparent and the complaints don't add much without some discussion of alternatives.

hombre_fatal 4y ago
we regularly confuse the ability to enumerate the downsides of something as some sort of notable epiphany.

rendall 4y ago

> I always find the position of telling people to never point out problems, only suggestions or solutions odd. The article went lower than pointing out problems. It veered into toxicity, its claim to "irreverence" notwithstanding. From the first: > Object-Oriented Programming: Luckily the industry doesn’t really use this term any more so we can ignore the changed meaning. The small club of people who still care can use it correctly, everybody else can carry on not using it. Just be aware when diving through the history books that it might mean “extreme late binding of all things” or it might mean “modules, but using the word class” depending on the age of the text. The reference to the "small club of people who still care can use it correctly" is elitist, and he does not bother to define the term (other than in a meaningless call-out to his fellow club members). The casual readers who are not members of his self-described club are not left with helpful information to decide for themselves when and and what use of the term may or may not be wrong. It's just "If you know, then you know" phrasing. The tone does not improve through the rest of the article. I'm not sure this fellow should be teaching beginners how to program.