This is a very short post but I think every developer should read this at the start of their day. I wasn't a code perfectionist but somewhere down the line hearing about clean code, patterns etc made me a perfectionist. The ability to write clean code comes with time. Yes, you can read books like Clean Code, Design Patterns, Refactoring but that will not make a significant difference if you are a newbie.
Such a perfectionist mentally can leave you very exhausted. Be kind to yourself and talk other people's advice and views with the grain of salt. Keep doing what you are doing, keep getting better. Write shit code and improve it later when you have the project completed. Thanks for sharing this.
I don't think it is an architecture but rather a way of doing things. Uncle Bob has been doing it for more than 30 years so I think he knows what he's talking about. It is only the current generation of "senior" developers that gives it a bad name by talking excessively about it in hopes of appearing smarter or better.
I agree completely. Partly the reason why I had to enclose it in quotes. Lots of folks are over-using the concept in places where they shouldn't, thus just making simple things complicated. I would use the exact same words you did, "in hopes of appearing smarter or better". You nailed it!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a very short post but I think every developer should read this at the start of their day. I wasn't a code perfectionist but somewhere down the line hearing about clean code, patterns etc made me a perfectionist. The ability to write clean code comes with time. Yes, you can read books like Clean Code, Design Patterns, Refactoring but that will not make a significant difference if you are a newbie.
Such a perfectionist mentally can leave you very exhausted. Be kind to yourself and talk other people's advice and views with the grain of salt. Keep doing what you are doing, keep getting better. Write shit code and improve it later when you have the project completed. Thanks for sharing this.
The "Clean Code Architecture" is poison for me, even if I'm not a newbie. Sorry Uncle Bob.
I don't think it is an architecture but rather a way of doing things. Uncle Bob has been doing it for more than 30 years so I think he knows what he's talking about. It is only the current generation of "senior" developers that gives it a bad name by talking excessively about it in hopes of appearing smarter or better.
I agree completely. Partly the reason why I had to enclose it in quotes. Lots of folks are over-using the concept in places where they shouldn't, thus just making simple things complicated. I would use the exact same words you did, "in hopes of appearing smarter or better". You nailed it!