4 ms·

Ugh, can we just stop talking about that guy?

by ysleepy 5y ago

shaolinspirit 5y ago
may I ask why? I don't know the context
napolux 5y ago
I'm as usual Out Of the Loop. Why we're considering him a renegade now?
- dagw 5y ago
  A lot of people seem to consider him an out of touch architect astronaut peddling snake oil that doesn't have any relevance to actually writing real software in the real world. Personally I think he has more misses than hits and everything he writes should be taken with a large grain of salt, but occasionally he hits upon some interesting ideas.
- 0xFEE1DEAD 5y ago
  I've been closely following him eversince he first got into the spotlight. He got famous in the tech community because he's been preaching about tdd and later on clean code before it got widely accepted to be good practice. Because of this the tech community treated him like a divine preacher and it seems like this got to him and went into his head. His persona "Uncle Bob" is this wise and all knowing guy who has ideas way ahead of everybody else but like most people he had more misses then hits. It seems like he's chasing "controversially big ideas" which he presents like they're truths and this can be pretty tiring to read.
pietromenna 5y ago
Don't get me wrong, but it is because you don't like the ideas presented or because you don't like him? I think there is a problem when we cancel ideas because of whom is telling them.
- ysleepy 5y ago
  He makes a career of telling developers what businesses want him to tell them. In my personal opinion he lacks experience with actual development and skill to even talk about code, let alone good development practices. He is a book author, not a developer sharing his expertise. He spouts hot air for money.
trentnix 5y ago
Because he has and continues to provide interesting and useful advice to software professionals. Leave cancel culture to the idiot class.
- napolux 5y ago
  cancel culture? what happened?
  - krapp 5y ago
    Simply disagreeing with someone is cancel culture, now.
  - dagw 5y ago
    Nothing. No one other than the person you're replying to even mentioned cancel culture. A lot of people just think that he gives bad advice and is out of touch with the realities of modern software development.
dgellow 5y ago
Not sure why you would want this. I know him from the book “Clean Code” and the Clean Code Architecture (not the book, mostly his blog posts on the topic). He oversells his points a bit too often, is IMHO too dogmatic, and I don’t necessarily like his writing style, but his content offers some great hindsight and interesting observations regarding software development.
- cheradenine_uk 5y ago
  And worse, people take it all at face value and don't think for themselves. A lot of the "clean" stuff is completely out of date. It might have been justifiable to insert umpteen independent layers (ooh.. Data Objects -> Domain Objects -> UI objects; mapper mapper mapper!) into your software in the early 90s when everything was a monolith and there were such things as "database teams" and "business rules teams" in order to insulate those parts of the software from each other. In the age of uServices where the boundary is the API and the context is completely self-contained, it's not just a bad idea it's an actively malignant waste of time.

Ugh, can we just stop talking about that guy?

shaolinspirit 5y ago

may I ask why? I don't know the context

napolux 5y ago

I'm as usual Out Of the Loop. Why we're considering him a renegade now?

dagw 5y ago
A lot of people seem to consider him an out of touch architect astronaut peddling snake oil that doesn't have any relevance to actually writing real software in the real world. Personally I think he has more misses than hits and everything he writes should be taken with a large grain of salt, but occasionally he hits upon some interesting ideas.
0xFEE1DEAD 5y ago
I've been closely following him eversince he first got into the spotlight. He got famous in the tech community because he's been preaching about tdd and later on clean code before it got widely accepted to be good practice. Because of this the tech community treated him like a divine preacher and it seems like this got to him and went into his head. His persona "Uncle Bob" is this wise and all knowing guy who has ideas way ahead of everybody else but like most people he had more misses then hits. It seems like he's chasing "controversially big ideas" which he presents like they're truths and this can be pretty tiring to read.

pietromenna 5y ago

Don't get me wrong, but it is because you don't like the ideas presented or because you don't like him? I think there is a problem when we cancel ideas because of whom is telling them.

ysleepy 5y ago
He makes a career of telling developers what businesses want him to tell them. In my personal opinion he lacks experience with actual development and skill to even talk about code, let alone good development practices. He is a book author, not a developer sharing his expertise. He spouts hot air for money.

trentnix 5y ago

Because he has and continues to provide interesting and useful advice to software professionals. Leave cancel culture to the idiot class.

napolux 5y ago
cancel culture? what happened?
- krapp 5y ago
  Simply disagreeing with someone is cancel culture, now.
- dagw 5y ago
  Nothing. No one other than the person you're replying to even mentioned cancel culture. A lot of people just think that he gives bad advice and is out of touch with the realities of modern software development.

dgellow 5y ago

Not sure why you would want this. I know him from the book “Clean Code” and the Clean Code Architecture (not the book, mostly his blog posts on the topic). He oversells his points a bit too often, is IMHO too dogmatic, and I don’t necessarily like his writing style, but his content offers some great hindsight and interesting observations regarding software development.

cheradenine_uk 5y ago
And worse, people take it all at face value and don't think for themselves. A lot of the "clean" stuff is completely out of date. It might have been justifiable to insert umpteen independent layers (ooh.. Data Objects -> Domain Objects -> UI objects; mapper mapper mapper!) into your software in the early 90s when everything was a monolith and there were such things as "database teams" and "business rules teams" in order to insulate those parts of the software from each other. In the age of uServices where the boundary is the API and the context is completely self-contained, it's not just a bad idea it's an actively malignant waste of time.