I agree with you that - even if it might look like that in the beginning - the book is not an easy read.
When having finished reading the book I was really motivated to see the benefits of Uncle Bob's thoughts in practice but I also felt left with many open questions on the details. So I decided to take one of my projects and convert it a "Clean Architecture" according to the presented principles.
I'm a small business programmer. I love solving tough problems with Python and PHP. If you like what you're seeing, you should probably follow me here on dev.to and then checkout my blog.
Very interesting. I took a quick look and you've written a small book there. I've bookmarked it and I'll take a look when I have some time to read it but I'm wondering if you would give us a little summary here.
Questions:
Did you find changing your architecture to be useful?
How hard was it? Was it worth the effort?
Did creating boundaries in your system help more than it hurt?
How useful was the book in helping you make your architecture decisions on a real-world system?
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.
I agree with you that - even if it might look like that in the beginning - the book is not an easy read.
When having finished reading the book I was really motivated to see the benefits of Uncle Bob's thoughts in practice but I also felt left with many open questions on the details. So I decided to take one of my projects and convert it a "Clean Architecture" according to the presented principles.
I share my experience when "Implementing Clean Architecture" on my blog: plainionist.net/Implementing-Clean...
If you have some time reading through the series, your feedback would be highly welcome!
Very interesting. I took a quick look and you've written a small book there. I've bookmarked it and I'll take a look when I have some time to read it but I'm wondering if you would give us a little summary here.
Questions: